Kenneth Porter <sh...@sewingwitch.com> wrote: > --On Thursday, March 05, 2009 7:43 AM +0100 Andrzej Adam Filip > <a...@onet.eu> wrote: > >> What I would like to see is a option to make spam assassin to produce >> "weighted scores" based on subset of all tests capable to work on subset >> of the "final data" available *before* message headers&body are >> transfered in SMTP session. > > Before you get the DATA part, you only have the EHLO and envelope.
At "RCPT TO:" stage there are available: * connecting client IP address (last mail hop) so big part of DNSBL and DNSWL tests *CAN* be used * envelope sender for SPF based tests * envelope sender and envelope recipient for auto white/black listing (producing some kind of grey-listing based for first attempt from unknown reputation source) > Not a real need for a full-blown SA scan at that point. I try hard to preach that SA methodology of creating "spam score" based on weighted tests *CAN* be applied at this point too. I would like too apply such test in milter (MIMEDefang) that uses SA anyway in my installation. > What rules would you apply that couldn't be done with a simple Perl > function? SA is not "a simple set of perl functions"? ;-) Delivering such functionality via SA would assure keeping sync of weights with changing spamming patterns. Some spammers are smart, many spammers are smart enough to follow so quality of maintenance team and maintenance methodology does make difference. > (For lurkers, MIMEDefang allows one to write a Sendmail milter in > Perl, by providing a C-to-Perl translation layer.) -- [pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu You can't have everything. Where would you put it? -- Steven Wright
