I think 5.5 sends the FQDN of the server that it picks from the Computer name property[1]. So if you computer name's FQDN does not match the actual domain name that you registered, some receiving SMTP servers might have a problem with that.
[1] I just checked my Borderware logs, and when my Exchange 5.5 server sends mail out via the Bordeware box, it says "HELO <FQDN>" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Scharff Sent: Thursday, July 21, 2005 3:20 PM To: Exchange Discussions Subject: RE: Can't send email to particular domain. Your MTA is not RFC compliant. Neither is the receiving MTA. One of the MTAs is willfully so, and it's probably not you. IIRC in 5.5 this is based on the DNS name specified in the machine or TPC/IP properties (I /think/ it's the former, but it's been a little while since I touched a 5.5 box. Verify the name being sent in the ehlo command and if necessary change it or add a DNS record for it. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of McCready, Robert Posted At: Thursday, July 21, 2005 1:14 PM Posted To: swynk Conversation: Can't send email to particular domain. Subject: Can't send email to particular domain. I'm pulling my hair out here. Last week, our company was able to send email to the Hillenbrand-cp.com domain. This week we can not, we get the following error message. Your message did not reach some or all of the intended recipients. Subject: DPL Test. Sent: 7/21/2005 1:34 PM The following recipient(s) could not be reached: '[EMAIL PROTECTED]' on 7/21/2005 1:34 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. <exchange.dplinc.com #5.7.1 smtp;554 5.7.1 This message has been blocked because the HELO/EHLO domain is invalid.> Last Friday this Domain added a second Exchange Server (5.5) and moved some mailboxes to that server (possibly another domain? Not sure). Ever since then, we can not send them email. However, anybody else on the planet can. I did a test from two Internet accounts and they worked fine. Anybody know why we can no longer send to this domain? I've already flushed DNS on all our servers. Thanks. Robert _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
