RE: AOL, Yahoo and other servers do not respond to connection attempt

  • From: "Chris Wall" <Chris.Wall@xxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 11 Jan 2006 12:44:39 -0500

From your server, can you perform an NSLookup in dos and identify the
organizations (yahoo, aol, etc) MX records?  

Once you do this, try to initiate an SMTP session in Dos (still on your
mail server) and manually send an e-mail through dos.  If you can do
that fine, then your firewall definitely is not the issue.

Are you on any Black Lists?

DNSStuff.Com is a great utility for testing your domain, finding
blacklist info and so forth.

Let us know the results of the SMTP mail delivery through dos on the
mail server.

Chris

-----Original Message-----
From: Jan Mt Pleasant [mailto:mtpleasantj@xxxxxxxxxxxxxx] 
Sent: Wednesday, January 11, 2006 11:59 AM
To: [ExchangeList]
Subject: [exchangelist] AOL, Yahoo and other servers do not respond to
connection attempt

http://www.MSExchange.org/

Since upgrading our mail server to Win2k3 and Exchange 2k3 (enterprise)
over the holidays, we have been unable to send mail to certain domains,
including AOL, Yahoo and others.  The messages just sit in the queues
and
then time out.  We're behind a pix firewall.  I've checked the message
boards and made sure that our IP has entered PTR and A records for us,
but
that doesn't seem to have helped.  Any thoughts?

Thanks.

Jan Mt. Pleasant

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
Chris.Wall@xxxxxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx




Other related posts: