Max SpamAssassin Size problems

[Peter Peters]

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

shuttlebox wrote on 24-8-2006 11:09:
> On 8/24/06, Julian Field <MailScanner at ecs.soton.ac.uk> wrote:
>> do I chop half way through an image?
>> do I chop at the end of an image?
>> do I carry on for a max of 100 lines of Base64 data or until the end of
>> an image, which is earlier?
> 
> I vote for the third alternative.

I think this is the best. And change the comment in MailScanner.conf in
something like this:

# SpamAssassin is not very fast when scanning huge messages, so messages
# bigger than this number of lines will be truncated to this length for
# SpamAssassin testing. The original message will not be affected by
# this. This value is a good compromise as very few spam messages are
# bigger than this.
# This is an estimation. Because of proper MIME handling the actual size
# of the message handed over to SpamAssassin can be up to 100 lines
# bigger.
Max SpamAssassin Size = 30000

- --
Peter Peters, senior beheerder (Security)
Dienst Informatietechnologie, Bibliotheek en Educatie (ITBE)
Universiteit Twente,  Postbus 217,  7500 AE  Enschede
telefoon: 053 - 489 2301, fax: 053 - 489 2383, http://www.utwente.nl/itbe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7XC8elLo80lrIdIRAjFoAJ4/Cbsybd9dXRaRtXPjgVR1/nX3EwCdHmjB
l793ZxzCW5WVM1rmIoIzWMo=
=ufCD
-----END PGP SIGNATURE-----