Yep, it's so much fun dealing with AOL. How 'bout I buy you a $0.25 beer at MEC. Oh wait, that doesn't exist anymore. ;-)
--- "Michael B. Smith" <[EMAIL PROTECTED]> wrote: > Where do I bill you Steve? :-) > > A key indicator is whether the connection attempt > fails or not. Edns0 is > typically indicated when the remote server doesn't > respond (according to > Exchange). Reverse DNS is typically indicated with a > successful > connection and a 4xx error. The internal scanning > mechanisms are > typically indicated when the e-mail immediately > bounces with a 5xx > error. > > In regards to AOL, as soon as you get a block of IP > addresses, signing > up to be notified by AOL as to "bad" behavior in > that block is a really > good idea (they call this their "Feedback Loop" and > they are much more > responsive to organizations who are whitelisted and > in the feedback > loop). See http://postmaster.aol.com. > > One of my techs or myself has to deal with them > almost daily on some > level with the 1,000+ e-mail domains we host on a > variety of platforms. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Johnston > Sent: Saturday, April 29, 2006 5:17 PM > To: [email protected] > Subject: RE: [ActiveDir] FW: Sending mail to AOL and > Yahoo > > Justin, > > Well, maybe. I've had the edns0 problem in the past > with a couple of clients. But, more likely, it's > one > of the recent problems I've had with clients of mine > sending to AOL: > > 1) As of a couple of months ago, AOL no longer > accepts > mail from servers that do not have PTR records > defined. > > 2) AOL has its own internal scanning mechanisms to > try > to identify and block domains and/or subnets > attempting to spew spam to AOL subscribers. Even > though a particular domain/subnet may not appear on > any RBL lists, AOL could still be blocking it. > > To determine which it is, telnet to port 25 on one > of > the AOL SMTP servers and try to manually send a > message to a valid AOL address. Make sure you do > this > from the actual Exchange server on which the AOL > queues are filling up. The error message you will > receive from the AOL server will include a link to a > website that will explain the reason why AOL will > not > accept a connection from you. > > In my most recent case, my client switched ISP's > and, > by chance, received a set of IP addresses that had > been blocked by AOL for a long time. AOL tech > support > was TOTALLY unresponsive and it took me about 6 > weeks > and many, many phone calls to AOL to finally get the > subnet removed from their blocking lists. Be > prepared > for a lot of pain dealing with AOL on this. > > As soon as you determine the problem, please let us > know so I can bill Michael for $0.25. :-) > > Steve > > --- "Michael B. Smith" <[EMAIL PROTECTED]> wrote: > > > Ah yes, now that I see the original message - I > bet > > a quarter it is the > > edns0 issue with a PIX firewall running a > relatively > > old version of > > PIX/os. > > > > ________________________________ > > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Salandra, > > Justin A. > > Sent: Friday, April 28, 2006 4:37 PM > > To: [email protected] > > Subject: [ActiveDir] FW: Sending mail to AOL and > > Yahoo > > > > > > > > > > > > > > > > Justin A. Salandra > > > > MCSE Windows 2000 & 2003 > > > > Network and Technology Services Manager > > > > Catholic Healthcare System > > > > 646.505.3681 - office > > > > 917.455.0110 - cell > > > > [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > > > ________________________________ > > > > From: Salandra, Justin A. > > Sent: Friday, April 28, 2006 4:16 PM > > To: [EMAIL PROTECTED] > > Subject: Sending mail to AOL and Yahoo > > > > > > > > Is any one else having difficulty in sending mail > to > > AOL and YAHOO. > > > > > > > > DNS is resolving the MX records for these domains, > > we can receive mail > > from these domains, but when we send mail it is > just > > sitting in the > > queue in the server saying that the remote server > > did not respond to the > > connection attempt. > > > > > > > > All other mail flow is working correctly. > > > > > > > > I have restarted the SMTP service twice and have > > turned on logging and > > nothing is showing. Just the same message in the > > event logs once > > logging was turned on, remote server did not > respond > > to the connection > > attempt. > > > > > > > > Any ideas > > > > > > > > Exchange 2003, Windows 2003 no service packs. > > > > > > > > Justin A. Salandra > > > > MCSE Windows 2000 & 2003 > > > > Network and Technology Services Manager > > > > Catholic Healthcare System > > > > 646.505.3681 - office > > > > 917.455.0110 - cell > > > > [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: > http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info : http://www.activedir.org/List.aspx > List FAQ : http://www.activedir.org/ListFAQ.aspx > List archive: > http://www.mail-archive.com/activedir%40mail.activedir.org/ > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
