External Mails stuck in the smtp connector: An smtp protocol error occurred
HI,We have a problem with our external mails.Frequently our external mails we stuck in queue and it will not connected to the remote servers.It gives "SMTP protocol error occured"in the additional information for the queue.Once we restart our exchange server then the mails in the queue will be delivered and the external mails will work fine for few days. This is happening very often to us and i cant find the exact reason for this problem.Someone please help me to find and resove this issue.Thanks
February 4th, 2009 1:13am

Hi,Before going on, please let me know the version of the Exchange server.When the issue comes up again, please telnet remote server 25, check whether you can send the email by using the command.If any error message is received, please let me know.Additionally, please enable SMTP logging and reproduce this issue in order to help us diagnose the log to find the possible cause.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2009 2:54am

Hi Allen, Thanks for the reply,I have enabled the diagnosting logging and i found the event occured when the mails got stuck,Its Event ID 7002 and it says,This is an SMTP protocol warning log for virtual server ID 1, connection #60. The remote host "100.100.100.10", responded to the SMTP command "mail" with "452 4.3.1 Out of memory ". The full command sent was "MAIL FROM:<rahmed@tdme.ae> SIZE=103983 ". This may cause the connection to fail. I had a search in Microsoft site about this event and they say to do the following, To resolve this error, try one or more of the following: Make sure that the latest network card drivers and firmware are installed. Run any network diagnostics software that was supplied with the network cards to verify that the network cards are functioning correctly. If the network cards are configured to automatically detect the speed of the connected network, change the configuration to use a specific speed setting. For additional information that may help you resolve this problem, see Microsoft Knowledge Base article 153119, XFOR: Telnet to Port 25 to Test SMTP Communication. But i cannot understand where the actual problemis coz , the Remote Host in the Event "100.100.100.10" is our exchange Front End.Could you please help to resolve tis issueThanksAsif
February 9th, 2009 1:46am

Hi,It seems that the issue that you encountered was similar to the below article:http://support.microsoft.com/default.aspx/kb/329167/en-usPlease refer to it and implement the solution based on the description.Hope that can help you.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2009 2:55am

Hi Allen, I searched the link and tyr to find out the exact issue in our office by folowing the link,Cause1:The Antigen software is not instlled installed in our Exchange , so that one is out.Cause2: I have checked the VSI 1 folder rights and Exchange Admin has Full Access on all the folders.Cause3: The Badmail folder is Empty in both exchange Backend and Front end servers..So, still i can't find out the reason why we are getting this problem.Please let me know is there anything else i need to check.ThanksAsif
February 11th, 2009 1:53am

Hi,Whether the FE and BE are placed in different Routing Groups?Where is the SMTP connector? created in FE or BE?How did the email send out? BE--->FE or just BE?Please describe the whole topology and configuration in detail for your environment.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2009 4:44am

Hi Allen, The SMTP connector is created in Exch BE and the mail travles from ,BE--->FE .We have a FE and BE topology, our Backend is a clustered exchange Virtual server and the SMTP connector is created in the back end .I have already check the Routuing Group, Both are in the same group and Virtual Server is the Master.The mail goint out will travel from BE--->FE and the incoming mails are vice versa.We are using Symantec Mail security in the Front end server.Will there beany problem in the front end?Thanks Asif
February 11th, 2009 5:48am

Hi,Now please set the SMTP connector to make the email to go out directly from BE, then check the result.Throught this, we can confirm whether the issue is caused by the FE or BE.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2009 9:41am

Hi Allen, Sorry for delayed responce, all our Incoming and Outgoing mails are coming through FE. Could you please help mehow toconfiguring the SMTP connector so that outgoing mailspasses directly from BEand incoming mails normally pass through FE --->BE.I found the Event ID 7010 and 7002 in Front End.Please help me.Thanks & Regards
February 14th, 2009 10:06am

Hi,For the Outgoing mails, please locate in the SMTP connector, right lick it and select Properties, in the General tab, remove the FE from the Local bridgeheads, then add BE as the Local bridgeheads.For the Incoming mails, we don't need to change anything.After that, please this issue.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2009 9:06pm

Hi Allen, Thanks , i will folow it and check whether it works.I will check fro few days and lets hope it sove the issue.Asif
February 16th, 2009 4:19am

Hi Allen, sorry, i took a longtime toreply on it. I did changethe Bridgehead form my front end to back end and examined but still i got the same problem after few days.This is an SMTP protocol warning log for virtual server ID 1, connection #60. The remote host "100.100.xx.xx", responded to the SMTP command "mail" with "452 4.3.1 Out of memory ". The full command sent was "MAIL FROM:rahmed@xx.xx SIZE=103983 ". This may cause the connection to fail. As is said here the remote host is my front end server.This problem in making me go nuts, please help me in this.Thanks Asif
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2009 4:18am

Hi,Did you try to delete the send connector and recreate it?If yes, please check whether this issue was caused by the message size limit which configured on the Exchange server.http://support.microsoft.com/kb/322679ThanksAllen
March 18th, 2009 2:56am

Hi Asif, This is due to spam mails that clogged your exchange FE with n number of mails. Due to which the storage limit for queue folders reached such limit and event was triggered. Regard GaneshGanesh P
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2012 2:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics