We're using exim to deliver to (among other things) a mailing list manager
called Mailman, and are occasionally getting duplicate messages to the
mailing lists.
Investigations with the Mailman guys seemed to indicate that the problem
lies with exim...
Example headers:
[first message]
Received: from ibm1.ftech.net ([212.32.16.71] helo=relay2.ftech.net)
by library.lspace.org with esmtp (Exim 3.03 #1)
id 11X2Q7-0004E5-00; Fri, 01 Oct 1999 14:08:19 +0100
Received: from localhost ([127.0.0.1] helo=ibm1.ftech.net)
by relay2.ftech.net with esmtp (Exim 3.03-ftechp3 #14)
id 11X2FP-0004p3-00; Fri, 01 Oct 1999 13:57:15 +0100
Received: from library.lspace.org ([195.200.1.58] ident=mail)
by relay2.ftech.net with esmtp (Exim 3.03-ftechp3 #14)
id 11WzYB-0005yY-00
for sluts@???; Fri, 01 Oct 1999 11:04:27 +0100
Received: from www.darkwave.org.uk ([207.24.30.216] helo=darkwave.org.uk)
by library.lspace.org with esmtp (Exim 3.03 #1)
id 11Wzi4-0002ni-00
for sluts@???; Fri, 01 Oct 1999 11:14:40 +0100
Received: from LON_ENG4.metronetworks.co.uk ([195.40.139.18])
by darkwave.org.uk (8.9.3/8.9.3) with SMTP id LAA27271
for <sluts@???>; Fri, 1 Oct 1999 11:04:46 +0100
Message-Id: <199910011004.LAA27271@???>
[duplicate]
Received: from ibm1.ftech.net ([212.32.16.71] helo=relay2.ftech.net)
by library.lspace.org with esmtp (Exim 3.03 #1)
id 11WziV-0002oL-00; Fri, 01 Oct 1999 11:15:07 +0100
Received: from localhost ([127.0.0.1] helo=ibm1.ftech.net)
by relay2.ftech.net with esmtp (Exim 3.03-ftechp3 #14)
id 11WzYD-0005yt-00; Fri, 01 Oct 1999 11:04:29 +0100
Received: from library.lspace.org ([195.200.1.58] ident=mail)
by relay2.ftech.net with esmtp (Exim 3.03-ftechp3 #14)
id 11WzYB-0005yY-00
for sluts@???; Fri, 01 Oct 1999 11:04:27 +0100
Received: from www.darkwave.org.uk ([207.24.30.216] helo=darkwave.org.uk)
by library.lspace.org with esmtp (Exim 3.03 #1)
id 11Wzi4-0002ni-00
for sluts@???; Fri, 01 Oct 1999 11:14:40 +0100
Received: from LON_ENG4.metronetworks.co.uk ([195.40.139.18])
by darkwave.org.uk (8.9.3/8.9.3) with SMTP id LAA27271
for <sluts@???>; Fri, 1 Oct 1999 11:04:46 +0100
Message-Id: <199910011004.LAA27271@???>
(Note - relay2.ftech.net = ibm1.ftech.net, same machine)
And from the exim logs:
[root@ibm1 exim]# grep 11WzYB-0005yY-00 main.log
1999-10-01 11:04:28 11WzYB-0005yY-00 <= lee@???
H=library.lspace.org [195.200.1.58] U=mail P=esmtp S=1949
id=199910011004.LAA27271@??? T="RE:t
1999-10-01 13:57:50 11WzYB-0005yY-00 => |/home/mailman/mail/wrapper post
sluts <sluts@???> D=mailman_alias T=address_pipe
1999-10-01 13:57:50 11WzYB-0005yY-00 Completed
[root@ibm1 exim]# grep 11X2FP-0004p3-00 main.log
1999-10-01 13:57:36 11X2FP-0004p3-00 <= sluts-admin@???
H=localhost (ibm1.ftech.net) [127.0.0.1] P=esmtp S=2314
id=199910011004.LAA27271@??? Tk
1999-10-01 13:57:37 11X2FP-0004p3-00 => C.Whitehouse@???
R=lookuphost T=remote_smtp H=smtp0.rhbnc.ac.uk [134.219.101.212] C="250
Submitted & queued (msg.0379"
[...snip further deliveries...]
[root@ibm1 exim]# grep 11WzYD-0005yt-00 main.log
1999-10-01 11:04:48 11WzYD-0005yt-00 <= sluts-admin@???
H=localhost (ibm1.ftech.net) [127.0.0.1] P=esmtp S=2314
id=199910011004.LAA27271@??? Tk
1999-10-01 11:04:50 11WzYD-0005yt-00 => C.Whitehouse@???
R=lookuphost T=remote_smtp H=smtp1.rhbnc.ac.uk [134.219.101.211] C="250
Submitted & queued (msg.0197"
[...snip further deliveries...]
The relevant lines from the mailman log (NB: mailman was patched earlier
to show process IDs in these logs)...
[post]
Oct 01 11:04:28 1999 post to sluts from lee@??? size=923
pid=22979
Oct 01 13:57:14 1999 post to sluts from lee@??? size=923
pid=18524
[debug]
Oct 01 11:04:28 1999 List 'sluts': Running 'post' under pid 22979
Oct 01 13:57:14 1999 List 'sluts': Running 'post' under pid 18524
... indicate that exim is calling Mailman twice.
Can anybody shed any light on this? We're running Exim 3.03, Mailman
1.0rc2 (which is using python 1.5.1).
Please give me a shout if I can provide any further information.
--
Kieran Hartnett - Frontier Internet Network Operations
Tel: +44 20 7510 4700 Fax: +44 20 7531 9930
All statements made and agreements come to by means of email are
at all times subject to Frontier's Terms and Conditions of service
and product descriptions/sales literature. Representations made
above and beyond those contained therein are not to be relied
upon and are at no time contractually binding.
