Hello... I recently updated milter-greylist from 2.1.12 (on a rhel3 server that had been working great for years) to 4.1.1 from EPEL on a new rhel5 server both running sendmail. It seems that the older 2.1.12 version only looked at the envelope of an email message and the newer 4.1.1 version will also look at the data of the email (dacl ?). I ran into a problem with a 18 Gig email (yes!). milter-greylist seemed to suck the entire message into ram. Since the new mail server only has 6Gigs of ram, "bad things" happened. Specifically ram usage and swap usage maxed out, the milter-greylist daemon stopped working, the message was rejected with a 4xx error. After restarting the milter daemon, all was good until the message was tried again. lather, rinse, repeat. I eventually found the root cause and deleted the large emails ( all six of them). questions: 1: Has anyone else run into this? 1a: If so has this been fixed in a newer version? 2: Is there a way to stop milter-greylist from processing the data stage completely? I realize limiting message sizes either within sendmail or the milter msg size max will work around this, but sometimes large messages need to be sent and received. I am also running clamav milter and spamass milter and IIRC, they both handle large messages gracefully by using disk space in /tmp. -- Christopher McCrory "The guy that keeps the servers running" chrismcc@... http://www.pricegrabber.com Let's face it, there's no Hollow Earth, no robots, and no 'mute rays.' And even if there were, waxed paper is no defense. I tried it. Only tinfoil works.
Message
memory usage bug with mushroom cloud
2009-08-14 by Christopher
Attachments
- No local attachments were found for this message.