This is a discussion on Re: [AMaViS-user] amavisd-new filling /var/amavis/tmp because of within the Amavis User forums, part of the Anti-Spam and Anti-Virus Related Forums category; Peter, > We use FreeBSD 6.1-RELEASE-p11, with amavisd-new-2.4.4,1. > Today one of ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Peter,
> We use FreeBSD 6.1-RELEASE-p11, with amavisd-new-2.4.4,1. > Today one of our antispam servers had its /var partition overfilled. > The problem was due to file dumping core on the p001 text part of a > spam email (I have reported this as a bug to FreeBSD), The file(1) that comes with the system is 4.12. You'd be better off with a version from ports: sysutils/file > and that made > amavisd-new constantly reprocess this spam email thousands of times > and fill /var/amavis/tmp with 30 GB of half processed emails. > > The main problem is that file dumped core, but shouldn't amavisd-new > give up on an email when it has failed several thousand times in a > short time span? It is the MTA that is repeating attempts. As far as amavisd is concerned, these are all independent messages. A crashing file(1) causes a temporary failure (4xx) to be reported to MTA, which retries repeatedly for few days until the message lifetime expires and a bounce is generated. I don't think there is much that can be done when essential components fail. The fundamental goal is not to lose mail when unexpected happens. Mark ------------------------------------------------------------------------- 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?p...rge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/...fo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ |