Exchange 2003 - Error #4.3.2

Yes, the third domain is listed in the recipient policy, and all users has this domain setup as a valid SMTP email address.  I know this part is configured properly since the customer can receive email for this domain, just not from the above referenced company.

I just turned on logging for the SMTP virtual server.  I'll check tomorrow, and see what this shows.

Thanks,
Harry

Hello Guys,

I have the exact same problem listed here. One exception though, when I restart my server the mail to the domains that was stuck in the queue get delivered. Not sure, why !!

I see that the accepted anwer was from hclotrain. Not clear on the actual solution here. What should I be looking out for once ive enable SMTP logging ???

Thanks for the help guys

Suren

Suren,

Just so you are aware this problem was only happening for us between two Exchange 2003 Servers.  I'm pretty sure what ultimatly fixed the problem was configuring both Exchange servers to (Perform reverse DNS lookup on incoming messages).  This setting automatically resolves the originating IP address of incoming e-mail messages to a host name (and the host name will be attached to the headers of e-mail messages).  Go into the properties for the "Default SMTP Virtual Server" (or what ever your virtual server name is), click on the Delivery tab, click on Advanced, and at the bottom of this screen you can configure the "Perform reverse DNS..." settings.

If it helps you, below is the SMTP error message we were receiving (once extended logged was turned on):

This is an SMTP protocol error log for virtual server ID 1, connection #874. The remote host "You", responded to the SMTP command "helo" with "550-You are not permitted to send mail from 550-vriusa.com(208-41-36-226.client.dsl.net[208.41.36.226]). 550-All SMTP connections have been blocked from that address. A 127.0.0.2 550- 550-There is a serious error of some kind at your end which we cannot correct 550-or compensate for at this end. Please forward this message in its 550-entirety to your own LOCAL <postmaster> and ask them to correct the 550-problem for you. 550- 550-Postmaster@[208.41.36.226]: Please contact <postmaster@most.weird.com> 550-(via an unblocked server of course!) if you need assistance in resolving 550-this issue. You must include your IP number, given above, in order to 550 receive any help at all. Including this entire status reply is ideal. ". The full command sent was "HELO vriusa.com ". This will probably cause the connection to fail.

Source:                   MSExchangeTransport
Category:                SMTP Protocol
EventID:                   7004
Computer:                ARLMAIL1

Good luck,
Harry
 

Thanks for the feedback. The domain that im having trouble sending to is microsoft.com Im pretty sure that that they are also running Exchange 2003. I will give your suggestion a try.

Thanks again for the help, I will let you know what happens

Regards

Suren

Hi Harry,

Thanks for the info, I eventually found my problem to be my exchange server, trasmitting the XEXCH50 command prior to sending mail outside the organisation. Once I disabled this feature in the registry, mail started to flow just fine.

The articles be below give the details of the XEXH50 command and when exchange uses it.

http://support.microsoft.com/default.aspx?scid=kb;en-us;818222
http://support.microsoft.com/?id=843106  

Thanks
Suren