-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chr. v. Stuckrad writes:
> On Mon, Aug 15, 2005 at 07:27:33AM -0700, Loren Wilton wrote:
> > You can stop the first two from being problems by running a manual expire
> > from a cron job every so often and disabling the auto-expire runs. You
> > should have a limit of 250K or so on the mail size to try to keep the third
> > from being a problem.
>
> Did that, it works (mostly, see below)...
>
> > Usually (at least in my experience) the way a rule is written doesn't affect
> > the spamd memory size.
>
> Sorry, this is definitely WRONG!
>
> If you write (like I once did) some rule containing spurious
> 'arbitrary long ..*-Constructs', the regex-automaton goes crazy
> and a mail of 250k may need more than 250MByte memory per child,
> instead of the currently seen near 80M.
>
> Simply 'shortening' the possible evaluation of the expression by
> replacing '..*' by .{1,N} (with 'N' a 'reasonably short' number)
> shrunk the problem to manageable sizes!
>
> Since then I never again used .+ or .* but ALWAYS limit the length.
Yep, that's correct. It's important to *never* use ".*" or ".+"
in rules.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFDANKHMJF5cimLx9ARAk9oAKCyVSB0u2mMVnnvJlyogesHtzZ7nACfWgIz
/bqCgRYmrlCX2J9cdUazBxg=
=qkt+
-----END PGP SIGNATURE-----
