Max SpamAssassin Size problems

[Julian Field]

Logan Shaw wrote:
> On Tue, 22 Aug 2006, Kash, Howard (Civ, ARL/CISD) wrote:
>> With the new OCR/Image verification plugins now available for
>> SpamAssassin, MailScanner truncating messages due to "Max SpamAssassin
>> Size" in the middle of an attached image is causing higher than normal
>> scores due to these images appearing to be corrupt.  How hard would it
>> be to truncate to the closest MIME boundary (either before or after this
>> value) instead of in the middle of it?  You could increase the value of
>> "Max SpamAssassin Size", but unless it's the same as the max allowed
>> message size you're still going to potentially truncate MIME
>> attachments.
>
> That's a very good point, and in fact it could explain some
> false rule firings (of FUZZY_OCR_CORRUPT_IMG) that I've seen,
> although it's hard to know for sure.
>
> If the closest MIME boundary thing turns out to be prohibitively
> difficult,
Instead of the closest following MIME boundary, how about the closest 
following blank line (or line that only contains whitespace). Would that 
be okay?

-- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk