|Main Archive Page > Month Archives > spamassassin-users archives|
On Fri, 16 Dec 2011 12:06:15 -0500
Kevin A. McGrail wrote:
> >>> There are a couple of hits on it on google with various people
> >>> having the same problem, I didn't find much answers but it
> >>> appears that the hardcoded limit is somewhere between
> >>> 256-512kilobyte?
> >> man spamc
> >> -s max_size, --max-size=max_size
> >> Set the maximum message size which will be sent to
> >> spamd -- any bigger than this threshold and the message will be
> >> returned unprocessed (default: 500 KB). If spamc gets handed a
> >> message bigger than this, it won't be passed to spamd. The
> >> maximum message size is 256 MB.
> > I do not use spamd/spamc. But the perl module of spamassassin.
> > So is there no way to get around this?
> Hmm. I didn't think SA had a limit internally. Normally, you
> utilize a limit on spamc (-s/--max-size) or in procmail such as * <
> But if you call SA directly as an API, I don't think there is a
> limit. You might want to post this on the dev list.
It's an optional limit in ArchiveIterator.pm. It's turned-on in