SLUG Mailing List Archives
Re: [SLUG] AOL SUCKS
- To: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
- Subject: Re: [SLUG] AOL SUCKS
- From: DaZZa <dazza@xxxxxxxxxx>
- Date: Thu, 26 Feb 2004 08:27:40 +1100 (EST)
- Cc: slug@xxxxxxxxxxx
On Wed, 25 Feb 2004, Jeff Allison wrote:
> Anyone been getting these
> And maybe know a work around
> From: "Mail Delivery System" <MAILER-DAEMON@xxxxxxxxxxxxxxx>
> To: <terrigal28@xxxxxxxxxxxxxxx>
> Sent: Wednesday, February 25, 2004 10:45 PM
> Subject: Undelivered Mail Returned to Sender
> > This is the Postfix program at host dalston.blackshaw.dyn.dhs.org.
> > I'm sorry to have to inform you that the message returned
> > below could not be delivered to one or more destinations.
> > For further assistance, please send mail to <postmaster>
> > If you do so, please include this problem report. You can
> > delete your own text from the message returned below.
> > The Postfix program
> > <Beanienut3@xxxxxxx>: host mailin-03.mx.aol.com[220.127.116.11] said:
> > (DNS:B1) AOL has determined that you are connecting directly to our
> > servers from a residential or dynamic IP. AOL
> > 554 TRANSACTION FAILED
It's commonplace these days for mail administrators to use RBL checks on
One of the RBL lists has a heading for "dial-up blocks", or IP's which are
dynamically assigned to dial up clients, or dynamic allocation IP
addresses - which means that if the email *is* spam, it can't necessarily
be tracked effectively. My mail server does exactly what AOL's does -
denies the connection.
A work around is to relay your outbound mail through your ISP's
"legitimate" mail server - that way, AOL will see it coming from a
non-dynamic IP, and accept the message.
This, of course, depends on your ISP allowing you to relay through it.