Im getting complaints on several of our lists that LISTSERV is issuing duplicate copies of list mail (or digests) to the users. What could be causing this?
LISTSERV probably isn’t doing this (in fact, it’s almost impossible for LISTSERV to be doing this), but to be sure you should check the daily log for any discrepancy. The most likely causes of this problem are: A broken unix gateway somewhere between LISTSERV and the recipient that is sending the duplicate mail (this has to do with how unix Sendmail recovers from crashes). Generally this problem will appear and disappear, although it’s entirely possible for it to go on for days or weeks, depending on how broken the gateway is. The SMTP protocol makes it possible for messages to be duplicated if the remote MTA abruptly drops the connection before it sends your local MTA an acknowledgement that it successfully received the message for delivery (via a 250 reply message). When this happens the protocol dictates that the local MTA try to deliver the message again. There is no way to stop this on the sending end short of removing the message manually from the MTA’s queue (by the time this ha
Related Questions
- LISTSERV uses a null return path (RFC821 MAIL FROM:<>) on its administrative mail, and some of our list owners and/or subscribers mail hosts reject this. Can the null return path be changed?
- Im getting complaints on several of our lists that LISTSERV is issuing duplicate copies of list mail (or digests) to the users. What could be causing this?
- Director FAQ [12] Lists [12.4] How can I make a duplicate copy of a list?
