https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6745
--- Comment #6 from Tim Gustafson <[email protected]> 2012-02-17 16:50:12 UTC --- > Do you happen to have a copy of the message that caused the issue? I'm sorry, but I don't. It's hard for me to capture the messages that cause the crash because this is a very busy e-mail server and most messages are delivered off-server to end users where I can't peek into their mail file to examine the message that caused the problem (and there would be legal implications in doing so, of course). Upgrading Perl and all the Perl modules did not help either; I'm still getting an occasional "Out of memory during ridiculously large request" messages. (By the way, the spamass-milter is configured to only scan e-mails of 512kb or less, so I'm guessing that it's not complaining about the size of the message. Or if it is, it must be getting confused about the message size somehow.) So, for now I've got the spamass-milter configured to refuse e-mails when spamd is down, and I've got Nagios configured to re-start spamd when it crashes. Obviously this is not a good long-term solution, but it's all I've got for the moment. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
