While this works great for web-based mail clients, this
is rejecting valid emails sent by AOL cable modem users
that are using outlook or other email clients. Has anyone
come up with a better way to handle AOL abused addresses?
Thanks
Jeff
> -----Original Message-----
> From: Suresh Ramasubramanian [mailto:mallet@efn.org]
> Sent: Wednesday, December 04, 2002 9:39 PM
> To: Nico Erfurth
> Cc: Kevin P. Fleming; Exim users list
> Subject: Re: [Exim] New AOL Mailer for forgery filter (for Exim 4.x)
>
>
> On Thu, 2002-12-05 at 01:01, Nico Erfurth wrote:
> > nicer versions of this condition would be
> >
> > condition = ${if match {${lc:$h_X-Mailer:}} {(?:aol|atlas)}
> {no}{yes}}
> > or condition = ${if match {${lc:$h_X-Mailer:}} {a(?:ol|tlas)}
> > {no}{yes}}
> >
> > you don't need the .* in your case, and a single match should be
> > better than two separated ones.
>
> sender_domains would only match the mail from: I take it?
>
> The X-Mailer: Atlas Mailer is used by netscape.net webmail
> afaik, not by AOL. However, netscape.net outbound mail is
> routed through AOL boxen.
>
> srs
>
>
>
> --
>
> ## List details at
> http://www.exim.org/mailman/listinfo/exim-> users Exim details
> at http://www.exim.org/ ##
>
>
> ---
> Incoming
> mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.423 / Virus Database: 238 - Release Date: 11/25/2002
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
http://www.grisoft.com).
Version: 6.0.431 / Virus Database: 242 - Release Date: 12/17/2002
