On Sun, 28 Jan 2001, Don Hayward wrote:
> I found reference to a problem like this in the list archive, but no
> resolution. This list has about 850 members and is managed by
> majordomo. I'm running exim 3.21 on Solaris 2.6. The problem is that
> apparently arbitrary members of the list are receiving multiple copies
> of the messages. Not all messages, not all members. Below are log
> excerpts demonstrating the occurence.
This is worrying. Exim goes to great lengths to try to avoid doing
duplicate deliveries.
> 2001-01-26 20:10:06 14MIan-0003E2-00 => don@???
> <marbio-outgoing@???> R=lookuphost T=remote_smtp
> H=thalia.pomobuli.net [4.35.171.234] X=TLSv1:DES-CBC3-SHA:168
> 2001-01-26 20:10:10 14MIan-0003E2-00 => don@???
> <marbio-outgoing@???> R=lookuphost T=remote_smtp
> H=thalia.pomobuli.net [4.35.171.234] X=TLSv1:DES-CBC3-SHA:168
The fact that those deliveries are only 4 seconds apart *suggests* that
they are all part of the same delivery attempt, which is particularly
weird. Were there normal deliveries of this same message to other
addresses at around the same time?
I'm not sure how best to try to track this down. If you can do a
delivery to the list with -d9 set, and stderr directed to a file so that
it is captured, we might get some evidence. Obviously you don't want to
send test messages to a large list, but what you could to is to set up
majordomo to submit messages to Exim with -odq so that they sit on the
queue till the next queue runner. Then when you spot such a message on
the queue, you can run
exim -d9 -M <message-id> 2>/some/file
to deliver the message and catch the stderr output. Of course, in the
way of these things, it will probably deliver perfectly, but it's worth
a try.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
