The second cause might be excessive clamav scanning times. If clamav
takes too long to scan, the sending client (be it an external server
or a submission client) can time out the connection thinking the
message hasn't been sent, and retry. Upon eventual successful
completion of scanning, QMT will deliver the message, but fail to
notify the sender of such because the sender timed out. After a period
of time, the sender will re-try sending, resulting in a duplicate. The
most common cause of this I've seen is with Outlook. Outlook clients
should be configured for maximum time to time out, which generally
fixes the problem (without really impacting Outlook performance).
Question : when you say " excessive clamav scanning times " would this
always be the scanning of that email
or is it possible for clamav to be bogged down with someone elses email.
meaning
email 'a' is sent , email 'a' has excessive clamav scanning time so
email 'a' is sent again .
or
email 'a' is sent but clamav is bogged down scanning a big
email/attchment of email 'z' currently making email 'a' ---wait.
timeout is exceeded and email a is sent again.
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
