Hanne wrote: > I'm working on upgrading to spamassassin 3.1.7 and amavisd-new 2.4.2 > (what's in backports, basically) and one mail (spam) fail with the > following log:
> There are 19 image attachments, several with the same filename, here's > an example from the log: > Jan 19 14:36:43 liksom3 amavis[19850]: (19850-07) (!!) TROUBLE in > check_mail: parts_decode_ext FAILED: run_command (open pipe): Can't > fork at /usr/lib/perl/5.8/IO/File.pm line 70, <GEN53> line 8941. > (Cannot allocate memory) at /usr/sbin/amavisd-new line 2216, <GEN53> > line 8941. > Now, this upgraded amavis is running in a sandbox with a lot less > memory than the box that actually will be receiving mail, so an out of > memory-message is not unexpected. However, the mail isn't actually > delivered in any way. Shouldn't there be a better way of handling such > situations? How about defanging the mail in questions and sending it > on with "amavis at so and so couldn't check this mail because > <reason>, so take care"? There are certain decode errors that are predictable (mail bomb, encrypted archives) where the mail may be allowed to pass unchecked. This type of error however potentially affects all mail and simply needs to be fixed, not worked around. My $0.02 Gary V ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
