Serge,
Well, as it happens, I received some e-mail fitting the criteria just
earlier today. A legit host carried it from an open relay.
As for the DNS checks, I'm going to remove the mail-abuse checks, and pare
down to just relays.osirusoft.com and relays.ordb.org.
I'm thinking that it might be a good policy to tag possible SPAM with
X-Spam-Warning or X-RBL-Warning headers. That would allow someone to pass
the e-mail along, but make it easy to filter on the client. [More on this
in a James-Dev thread]
--- Noel
-----Original Message-----
From: Serge Knystautas [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 02, 2002 23:20
To: James Users List
Cc: Russell Coker
Subject: Re: SPAM origin
It might be worth doing... the thing is, if there is an open relay, it's
probably getting to you from that open relay (as opposed to going from
one to another). Downside though is it makes mail processing a lot
slower. If you comment out the DNS related checks in your spool
processor, generally you'll see a huge increase in performance. So
doubling or more the number of checks probably is overkill. But it
certainly might be worth having as an option.
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Noel J. Bergman wrote:
> Right now InSpammerBlacklist checks the remote address of the proximate
> relay to see if it is open. Is that sufficient? We are trusting that
relay
> to filter out e-mail from open relay sources.
>
> Should we be (at least optionally) checking the entire series, and
rejecting
> if we find any open server in the chain?
>
> --- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
