Max SpamAssassin Size problems

[Julian Field]

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



Kash, Howard (Civ, ARL/CISD) wrote:
>> What objections to people have to simply letting you set this yourself?
> 
> With no changes to the code we have to disable Max Spamassassin Size in order to guarantee that no attachments are truncated in the middle and thus cause false positives.  At the same time we loose all protection against DoS and resource over utilization.  With code added that will only continue until the end of the current attachement, at least there is some protection.  Granted, there may be one huge attachement, but at least it's something.

Why not just set the Max SpamAssassin Size to 50k or the 
partial-image-detection rules to 0?
- -- 
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: UTF-8

wj8DBQFE8GoLEfZZRxQVtlQRAgaSAKCg9lzXAwCbR/d3j2A6b8Py53bJyQCfVw0b
PYr8Mk3F9qutMZIBsqkqLxc=
=DjBq
-----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