On Fri, 18 Apr 2014, Kevin A. McGrail wrote:
On 4/18/2014 6:18 AM, Erik Logtenberg wrote:
The tool that hands the message to spamasassin (spampd in your case)
imposes the size limit. The message is never seen by spamassassin.
You're barking up the wrong tree ;)
Tom
Ah, I agree. This is where that happens:
$self->log(2, "skipped large message (". $size / 1024 ."KB)");
I'll send my question to Maxim Paperno, author of spampd, instead.
Spamassassin is a program AND an API.
Right now you are using the API so your wrapper (spampd) can do anything it
wants but we could also consider this feature for spamc/spamd and for
spamassassin as a parameter to enable. Please open a bugzilla bug if you
would like it considered.
Another way to deal with this problem is, via the glue agent, to truncate
large messages and send just the first X-kbytes of the message (for some
appropriate value of X, I'm using 256K). The idea is that a large spam message
is probably large because of some attachment and the payload is in the first
part.
I'm using a milter to connect to spamd so I can do SMTP rejections of high
scoring spam. I coded the truncation feature in the milter so no need to
modify the MTA nor spamd.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
