From: Gerardo Gregory [mailto:[EMAIL PROTECTED] > > Bowie Bailey wrote: > > > I asked this question on the Amavis list and didn't get any answers, > > so I'll try again here. > > > > I am currently testing Amavis-ng/Clamd on my Courier mail server. > > It works fine most of the time, but if Clamd dies, Amavis starts > > dropping all the mail into it's 'problems' directory. This would > > only be a minor annoyance, except that Amavis does not store the > > correct recipient information with the message. So the > > amavis-inject script will not resend the message properly. > > > > As an example, this header came from a message from this list that > > was quarantined due to Clamd problems. > > > > X-Quarantined-To: [EMAIL PROTECTED] > > > > If I run amavis-inject on this message, it will attempt to send it > > back to the list rather than delivering the message to me. As long > > as I am the only user running Amavis, I can just send all the > > messages to myself, but as soon as I put this system-wide, I will > > have no idea where these messages are supposed to go. > > > > I am using Amavis as an xfilter as such: > > xfilter '/usr/local/bin/amavis' > > > > How can I get Amavis to put the correct recipient information in > > it's quarantine headers? > > My first suggestion would be to find out why CLAM (or CLAMD) is dying > on you. I have run Clam and Amavis-ng (Amavisd, and Amavis-new) on > FreeBSD (numerous releases) and never had Clam die on me (knock on > wood).
I am working on the problem with Clamd. The only message I have been able to find is related to a timeout, so I upped the timeout and I'm now waiting to see if the problem happens again. This is really a secondary problem at the moment. The real killer here is the lack of valid recipient information in the Amavis-ng quarantine files. > Also I would suggest to run Amavis-ng using the perlfilter > (Courierfilter), if you have any considerable number of users on your > system. The overhead is way better than running it from maildrop. I might consider this if I find the overhead is too high once I put the xfilter systemwide. My server is relatively low traffic, so I don't think I'll have a problem. > I had numerous issues with Amavis-ng from maildrop (Zip decompressor > did not worked right, no notifications ever arrived [just a blank > message]), and a plethora of other fun and interesting issues. I'll have to test the zip decompressor, but the notifications seem to work fine. > All in all ever since I applied it to the global filter everything > works perfectly. One thing though, there will be no header rewriting > done if you run it globaly. Right. Thanks, Bowie ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
