Re: A good spam tool

[Dick Dowdell]

Graylisting (see http://projects.puremagic.com/greylisting/ for a full 
description) involves logging each incoming piece of mail and rejecting 
it with a 451 (Try again later) message.  After a specified period of 
time has elapsed for a specific piece of mail, the server will accept it 
normally.  Unlike legitimate SMTP servers, spammers rarely try to resend 
rejected mail and are effectively blocked.  For a spammer to circumvent 
the graylist, he has to incurr the cost of resending rejected mail---a 
very expensive process for millions of emails.

It is my understanding that, by the time a mailet is executed, the email 
has already been accepted.  Hence, my problem.

Thanks,
Dick Dowdell


Steve Brewin wrote:

Dick Dowdell wrote:

<snipped>

 

One of the most promising techniques, to me, is graylisting
(http://projects.puremagic.com/greylisting/).  It won't block
any mail
from properly configured legitimate mail servers while increasing the
processing costs of any spammer who wants to circumvent it.  However,
given the way James works, I can't see any way to implement a
graylisting mailet. If I'm wrong, I'd appreciate someone setting me
straight before I waste time building a filter in front of James.
   

What are the issues you are seeing that prevent this using matchers and
mailets in James? If you enumerate the problems maybe someone can suggest
solutions.
-- Steve





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]