Max SpamAssassin Size problems

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Kash, Howard (Civ, ARL/CISD) wrote:
>> Instead of the closest following MIME boundary, how about the closest 
>> following blank line (or line that only contains whitespace). Would
> that 
>> be okay?
> 
> 
> That sounds like an OK fix for the images.  The plugins don't care about
> the closing MIME boundary, they just need the full base64 encoding
> present, which, as far as I know, shouldn't contain any blank lines.
> The only issue I can think of is if you hit the "Max SpamAssassin Size"
> limit in the middle of the MIME header.  Then your next blank line would
> be between the header and the contents and you're left with a header but
> no contents.  That would probably still trigger a corrupt image rule,
> but should be pretty rare.
> 
> SA does have a MIME_MISSING_BOUNDRY rule, but it has a default score of
> zero in at least the 3.1 releases.

Sounds survivable. After the limit I will keep going until I hit the 
first line that only contains white space.

All done. Will be in the next beta.
*Please* test this functionality after I release this beta.






> 
> 
> Howard

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

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at MailScanner.biz

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.5.0 (Build 1112)
Charset: ISO-8859-1

wj8DBQFE7LmMEfZZRxQVtlQRAo6WAKDSJlPXxbqj3KfOEGRlA+IBeWVhtQCgjv8W
5N7UCvYtl9+ZRWw/G12ywk8=
=4DzA
-----END PGP SIGNATURE-----

-- 
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