Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-20 Thread Mark Martinec
Nicklas, Do you know when you will have a chance to release 2.4.5 or at least a patch for this specific problem? Will post a patch in a day or two (it is one of the two things holding back 2.4.5). The 2.4.5 pre-release is expected in a week. In your case where you know that clamd is actually

Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-20 Thread Nicklas Bondesson
do_unzip: p003, zero length members, archive retained Dec 19 15:56:31 example.com /usr/local/sbin/amavisd[8972]: (08972-13) ClamAV-clamd: timed out, retrying (1) There is a bug in amavisd client code to sophie and clamd where after one attempt to connect to these virus checkers

Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-20 Thread Mark Martinec
Nicklas, It seems like this problem is not only locally affected. The buggy client code in amavisd seems to make some mail servers goes a bit crazy when they try to deliver a mail and the loop starts in amavisd/clamd. This does not sound as being related to the clamd/sophie/trophie client

Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-19 Thread Nicklas Bondesson
Nice knowing you are aware of the problem, and know what needs to be done. Do you know when you will have a chance to release 2.4.5 or at least a patch for this specific problem? Thanks, Nicklas Nicklas, P.S. do_unzip: p003, zero length members, archive retained Dec 19 15:56:31

Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-19 Thread Nicklas Bondesson
Nice knowing you are aware of the problem, and know what needs to be done. Do you know when you will have a chance to release 2.4.5 or at least a patch for this specific problem? Thanks, Nicklas Nicklas, P.S. do_unzip: p003, zero length members, archive retained Dec 19 15:56:31

Re: [AMaViS-user] Duplicate mails: archive retained and clamav timeout

2006-12-19 Thread Nicklas Bondesson
This can happen when MTA's timeout setting on waiting for response to DATA is longer that a timeout of a content filter. MTA times out and requeues a message, while content filter continues with processing and at the end delivers the message, on every MTA attempt. Check your option '-o