On 06/22/2014 09:36 PM, Peter Fraser wrote: > > Ok I went scouring through the logs trying to trace a particular message like > you suggested and I did find some like this: > > Here's one message I tracked.214CA3AC88D: from=<listname-boun...@domain.com>, > size=585098, nrcpt=500 (queue active) > then214CA3AC88D: to=<n...@otherdomain.com>, relay=none, delay=32256, > delays=32255/0.05/0.15/0, dsn=4.4.1, status=deferred (connect to > mail1.otherdomain.com[x.x.x.x]:25: Connection refused > then214CA3AC88D: from=<listname-boun...@domain.com>, size=585098, nrcpt=500 > (queue active) > then214CA3AC88D: sender non-delivery notification: 35F9D3AC8A5 > then35F9D3AC8A5: from=<>, size=3771, nrcpt=1 (queue active) > then35F9D3AC8A5: to=<listname-boun...@domain.com>, > relay=hubtransport.domain.net[192.168.0.165]:25, delay=0.22, > delays=0.08/0.04/0.01/0.1, dsn=2.6.0, status=sent (250 2.6.0 > <20140620091131.35f9d3ac...@mail1.domain.com> Queued mail for delivery) > then35F9D3AC8A5: removed
OK. The failure DSN was sent to <listname-boun...@domain.com> via hubtransport.domain.net (local network IP 192.168.0.165) and accepted by the MTA there with the response (250 2.6.0 <20140620091131.35f9d3ac...@mail1.domain.com> Queued mail for delivery) So look at the logs on that machine and see what it did with the message. And then continue to follow the message until you see it delivered to Mailman or not delivered and why. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
