That's definitely a PIX in the mail path. -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc.
> -----Original Message----- > From: Phillip Stafford [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 06, 2004 10:50 AM > To: Exchange Discussions > Subject: RE: Problem sending to one domain > > I get > > 220 > ************************************************************** > 0*2******* > ******************200******2**0 *0*00 > > And then immediately become disconnected. No chance to type > or enter in > anything. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Fyodorov, Andrey FTL > Sent: Tuesday, April 06, 2004 9:34 AM > To: Exchange Discussions > Subject: RE: Problem sending to one domain > > > Can you manually establish an SMTP connection to their server > from your > server's console, using Telnet on port 25? > > What do you get back? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Phillip Stafford > Sent: Monday, April 05, 2004 7:44 PM > To: Exchange Discussions > Subject: Problem sending to one domain > > > One of our clients running Exchange 2003 on a Win 2003 SBS is having > issues in sending to one domain. > > The Outlook error message is: > > Your message did not reach some or all of the intended recipients. > > Subject: > Sent: 4/5/2004 7:18 PM > > The following recipient(s) could not be reached: > > [EMAIL PROTECTED] on 4/5/2004 7:25 PM > There was a SMTP communication problem with the recipient's email > server. Please contact your system administrator. > <mail.sendingdomain.com #5.5.0 smtp;500 Non RFC-compliant response > received> > > > I enabled maximum logging on several of the subcategories on the > MSExchange Transport in System Manager. In the App Event Log, the > following error is > logged: > > > Event Type: Warning > Event Source: MSExchangeTransport > Event Category: Connection Manager > Event ID: 4006 > Date: 4/5/2004 > Time: 1:48:21 PM > User: N/A > Computer: Server > Description: > Message delivery to the host 'xxx.x.xxx.xx' failed while delivering to > the remote domain 'receivingdomain.com' for the following reason: The > connection was dropped by the remote host. > > To further assist, I went and started logging SMTP > connections through a > 3rd party app (MailMonitor) and listed below is the log for the > connection: > > 220 > ************************************************************** > 0*2******* > ******************200******2**0 *0*00 > EHLO mail.domainname.com > 500 Syntax error, command "XXXX mail.sendingdomain.com" unrecognized > QUIT > > Since it appeared the recipient's server was having trouble with the > EHLO command and no HELO command was ever issued as a result, > I created > an SMTP connector for their domain, using their IP address as the > smarthost and giving their domain name of type SMTP in address space a > cost of 1. > > When trying afterwards, the email again fails. In > MailMonitor, the log > is > below: > > 220 > ************************************************************** > 0*2******* > ******************200*****02**0 *0*00 > HELO mail.sendingdomain.com > QUIT > > So, it looks like the problem is something more than just the > EHLO/HELO > specification. I don't understand WHY, when sending HELO it > then quits. > I even tried sending emails from my own server (running Exchange 2003 > Standard) and my email goes through fine. > > I have emailed their IT support on this issue and they claim that the > problem is at our end. According to them, they are not performing any > reverse-DNS lookups (our reverse-DNS has already been configured > properly, by the way) and they are not blocking emails from > our domain. > > This problem has been happening sporadically over the past few weeks > (ever since we moved our mail in-house). > > Any help is greatly appreciated. > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=& > lang > =english > To unsubscribe: mailto:[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/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=& > lang=english > To unsubscribe: mailto:[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/cgi-bin/lyris.pl?enter=exchange&t ext_mode=&lang=english > To unsubscribe: mailto:[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/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[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.
