On Monday, Jun 19th 2006 at 11:40 -0400, quoth Chris Santerre:

=>
=>
=>> -----Original Message-----
=>> From: Steven W. Orr [mailto:[EMAIL PROTECTED]
=>> Sent: Monday, June 19, 2006 9:08 AM
=>> To: spamassassin-users
=>> Subject: Can SA be used to implement greylisting?
=>> 
=>> 
=>> I'm running sendmail here on a home server. I've been looking 
=>> for a good 
=>> greylist package and I frankly have not found one. There are 
=>> a couple out 
=>> there but they work in memory and don't maintain their tables in a 
=>> database.
=>
=>grey.uribl.com  ???
=> 
=>> I'm also running spamass-milter which is set to reject mail 
=>> ifd SA says 
=>> it's spam. Is it worthwhile to try to convince the SA dev 
=>> crowd to add 
=>> greylist functionality? I know it would be easy to modify 
=>> spamass-milter 
=>> to return the needed info to sendmail. It would require a new table.
=>> 
=>> Does this make sense?
=>
=>Not really. Are you talking about greylisting as in a greet pause, or a
=>"This is a spamish domain."? 
=>
=>Greet pause would be used in Sendmail. grey.uribl.com would be used for the
=>later. 
=>
=>http://www.uribl.com/usage.shtml

Neither. What I'm looking for is a rubust way to say: "I haven't seen mail 
from this guy before so I'm going to reject his email with a 450 error 
code. If email from him tries for delivery after (let's say) four 
hours, then I will accept it and nevermore will this guy have a delay in 
sending me mail." 

It's not a spam identifying technique but it does eliminate about 90% of 
the spam. The question is, is this worthwhile exploring as adjunct 
functionality to SA?

Yes, I understand that SA does not have any ability to reject mail, much 
less specify an SMTP error code. Is this clearly out of bounds for what SA 
should be doing?

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors?

Reply via email to