Jarry wrote:
Might be bug in clamd/spamassassin. But it could also be you are
being mail-bombed (e.g. infinite depth of compressed-in-compressed
attachements).
I thought about that - but I can't find an offending email with a bogus
attachment if I am.
I recommend to include some limit for number of clamd/spamassassin
instances. Don't know if procmail has such a capability, but it is
easy to control it with wrappers like amavisd-new or MailScanner...
I'd assumed that clamassassin would take care of this with some sensible
defaults for me...
My default clamd.conf says:
--
# Maximum depth directories are scanned at.
# Default: 15
#MaxDirectoryRecursion 20
--
So, I'd imagine that would take care of this... conversely - it did seem
a bit strange that clamassassin was configured to use clamscan not
clamdscan (which would have made more sense to me) but it had been
configured that way for a very long time according to the file-dates and
it's only recently that things went awry for me...
My procmailrc is simply how I wire in my mail delivery filters. I'd
expect the filters themselves to behave sensibly... Though it came as a
bit of a shock to see that my postfix user had as many processes spawned
as it did... I'd always thought that the purpose of postfix was to queue
mail in order that it could be processed sequentially in order to avoid
this sort of problem...
