Forum Moderators: phranque

Message Too Old, No Replies

Mail to AOL

AOL rejects all our mails

         

EricGen

12:46 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



Hi,

I am getting really really frustrated with AOL. Our personal mailsnever get delivered to people using them, and our ISP here tiscali which I would have thought is quite a big ISP so we're probably not the only one sending mails to aol users. We sometimes get a notification saying they reject it because it's spam, but more often, nothing. Now and that's more serious, even mails sent by our site, such as orders notifications get there, these are from a totally different isp as well. A friend who's with them gets nowhere with their tech support either.

This is really outrageous, it's like if in France the post office decided the mail coming from the UK was irrelevant and would not deliver it. Is there anything we can do?

Thanks

EricGen

12:49 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



oops, when I say:

"Now and that's more serious, even mails sent by our site, such as orders notifications get there..."

I mean of course:

"Now and that's more serious, even mails sent by our site, such as orders notifications DONT get there..."

Eric

amznVibe

12:53 pm on Oct 6, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Join the crowd:

[internetnews.com...]

[rss.com.com...]

[rss.com.com...]

check this too:

[postmaster.info.aol.com...]

rmccollom

1:05 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



That happened to us too. We had to close our open relay and start authenticating our emails through the server. Once we did that, our messages got through the AOL filter.

EricGen

1:06 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



Thanks. What gets me as well is that as far as I know, our ISP's SMTP servers don't have dynamic IP addresses. Tiscali is quite a big player too, so their antispam stuff doesn't work or they've changed it again

celerityfm

1:14 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



We had all of our email blocked by AOL on Thursday for not having reverse DNS according to their postmaster hotline (you have called that, haven't you?), but then like magic even before our reverse dns was setup the block went away on Friday-- so your not alone.

Fortunately all of the email that was sent, that we didn't get notices about not being deliverable, got through-- albeit a little delayed.

FOR THOSE WITH AOL EMAIL PROBLEMS:

Go to this webpage: [postmaster.info.aol.com...] and follow the instructions-- make sure you've got Reverse DNS setup for your mailserver's IP address (put your IP address into [samspade.org...] and see what it says about reverse DNS)-- follow theinstructions at that page and if you still can't get mail to go through then call the number on that page.

[edited by: celerityfm at 1:18 pm (utc) on Oct. 6, 2003]

pageoneresults

1:14 pm on Oct 6, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



We've also had some issues with our clients and AOL. We came to find out that our backbone provider happens to be listed in a few blacklists and we had Open Relay set up at the host level.

We had to close our open relay and start authenticating our emails through the server.

That is the main problem right there. If you have any type of Open Relay setup, even at the host level, you may end up on a blacklist. There are various tools out there where you can check your mail server to see what the blacklist sees. If you have any type of Open Relay set up, you're going to have problems with mail.

rmccollom

1:43 pm on Oct 6, 2003 (gmt 0)

10+ Year Member



If you have any type of Open Relay set up, you're going to have problems with mail.

We had to get our ISP involved which meant moving us to a new email server.

sarahk

12:18 am on Oct 9, 2003 (gmt 0)

10+ Year Member



oh, how familiar.

I fought this battle for ages and in the end it turned out to be a connection way up the line. You know how the traffic bounces from node to node to node? Well, one of those nodes was rejecting aol emails. We got no fail message and AOL were hopeless (but then it wasn't their problem). I did find the AOL help really difficult to use.

Anyway, one day some engineer somewhere scratched his head and fixed it, not realising the downstream hysteria caused by the problem.

good luck on fixing this!