Deliverability Report suggestion

Bug #327696 reported by Chris Alexandre
2
Affects Status Importance Assigned to Milestone
GNU Mailman
New
Undecided
Unassigned

Bug Description

This is a suggestion rather than a bug, (sorry Barry if its in the wrong place!)

It would be very cool to have a report that listed the delivery status of each mailing that is done - something that shows me which email addresses were/weren’t delivered to. (I have users who say “definitely didn’t get to me..” etc and I want to be able to see if it did or didn’t.)

Thanks

Revision history for this message
Mark Sapiro (msapiro) wrote :

Ultimately, there's no way for Mailman to know this. Mailman knows which addresses were "sent to", but I don't think this is the information you want. The best you can do from your end is analyze your MTAs logs and perhaps Mailman's bounce log to find for which addresses mail was accepted by the MTA and which addresses bounced.

This may still miss "unrecognized" bounces from remote MTAs, and most importantly, it misses mail which is silently discarded or filed in some "spam" or "bulk" folder by the remote MTA. Many ISPs will silently discard some mail, and there is no way the sender or the recipient can know this other that the fact that it was sent, accepted and apparently not delivered.

I suspect this is the mail you really want to know about. All you can to do in this case is find the entry in your MTAs log that says the message was accepted by the remote MX, and give that information to the user who can then complain to the ISP that it silently discarded wanted mail.

Revision history for this message
Chris Alexandre (chris-surveyshack) wrote : RE: [Bug 327696] Re: Deliverability Report suggestion

Hello Mark

Thanks - even a listing of Mailmans bounce log would be great to see.

I realise that a lot would get "missed" as you have pointed out, but you are also correct in saying that all I want to know is if it was handed to and accepted by the remote MX.
It's not easy for me to get into the servers logs to search for specific email addresses and its log entry. If there was a list (alphabetical would be fine), it would help a lot.

Thanks again

Chris

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Mark Sapiro
Sent: 10 February 2009 07:33 PM
To: <email address hidden>
Subject: [Bug 327696] Re: Deliverability Report suggestion

Ultimately, there's no way for Mailman to know this. Mailman knows which
addresses were "sent to", but I don't think this is the information you
want. The best you can do from your end is analyze your MTAs logs and
perhaps Mailman's bounce log to find for which addresses mail was
accepted by the MTA and which addresses bounced.

This may still miss "unrecognized" bounces from remote MTAs, and most
importantly, it misses mail which is silently discarded or filed in some
"spam" or "bulk" folder by the remote MTA. Many ISPs will silently
discard some mail, and there is no way the sender or the recipient can
know this other that the fact that it was sent, accepted and apparently
not delivered.

I suspect this is the mail you really want to know about. All you can to
do in this case is find the entry in your MTAs log that says the message
was accepted by the remote MX, and give that information to the user who
can then complain to the ISP that it silently discarded wanted mail.

--
Deliverability Report suggestion
https://bugs.launchpad.net/bugs/327696
You received this bug notification because you are a direct subscriber
of the bug.

Status in GNU Mailman: New

Bug description:
This is a suggestion rather than a bug, (sorry Barry if its in the wrong place!)

It would be very cool to have a report that listed the delivery status of each mailing that is done - something that shows me which email addresses were/weren’t delivered to. (I have users who say “definitely didn’t get to me..” etc and I want to be able to see if it did or didn’t.)

Thanks

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.19/1942 - Release Date: 02/09/09 17:40:00

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.