On 08/29/03 at 15:54 -0400, chris opined:
> >You're aware, aren't you, that for the purposes of rejecting spam
> >messages, router entries like the above will only be applied to the
> >Return-Paths of incoming messages? And then, only if you have
> >'Verify Return-Paths' enabled. That doesn't do the same thing as IP
> >blacklisting, and its usefulness is much narrower.
>
> Yes, in this instance, the return-path always carries the distinctive
> marker of "mx##." in the domain part.
Good 'nuff. I just wanted to make sure that you intended to apply this to
observed Return-Paths and weren't expecting it to work on the name of the
relaying host.
> I've actually been using that on a local client level filter for a
> while, but at the client level I can do much more specific filtering
> so I haven't noticed if anything will be caught with just "mx*"
It's not unknown for legitimate SMTP servers to be named like
'mx1.served.domain', etc. ('mx' being an abbreviation for 'mail exchanger'
and the DNS record type for mail exchangers), so it's possible that you
might get some false positives. For the most part, though, I'd guess that
such names wouldn't show up very often in Return-Paths on legit messages.
--
Christopher Bort | [EMAIL PROTECTED]
Webmaster, Global Homes | [EMAIL PROTECTED]
<http://www.globalhomes.com/>
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
