Hello,

I manage a few public Mailman 2 mailing lists. A contributor to one of the 
lists was recently removed because of bounces, and they reached out to us to 
understand why.


  *   This poster’s email domain is gmail.com. For this thread, we’ll say it’s 
xx...@gmail.com.
  *   I found the relevant DSNs that the Mailman bounce processor received.
  *   In all cases, the DSNs were from mailer-dae...@googlemail.com
  *   All DSNs had this as the reason:

Delivery to the following recipient failed permanently:

     xx...@gmail.com

Technical details of permanent failure:
554.5.7.1 The user or domain that you are sending to (or from) has a policy
that
554.5.7.1 prohibited the mail that you sent. Please contact your domain
554.5.7.1 administrator for further details. For more information, please
visit
554.5.7.1 http://support.google.com/a/answer/172179
My initial read of the DSN was simply that some policy that xx...@gmail.com had 
set up on his Gmail account was rejecting copies of their own emails sent to 
the list, but I looked a little closer at the original headers in the DSNs.


  *   In all cases, the Delivered-To in the original headers section of the DSN 
was to a different email address. For this thread, we’ll say it’s f...@bar.com, 
where bar.com’s MX records are aspmx.l.google.com and the usual alts.

Would this mean that there’s some policy set by the bar.com admins in Google 
Apps rejecting xx...@gmail.com’s email? If that’s the case, shouldn’t the DSN 
say delivery to f...@bar.com failed permanently instead, since that’s the 
recipient? Or is Google ignoring the “delivery to the following recipient” part 
of the message and putting the sender’s email there to blame them for the 
delivery failure? (The first line of the 554.5.7.1 explanation suggests that it 
might be.)

As a list admin, it feels wrong to ding (and eventually auto-unsub) 
xx...@gmail.com because f...@bar.com sets some arbitrary policy. Is there 
anything that can be done in Mailman 2 to detect and ignore these cases or have 
the bounce count against f...@bar.com? Does Mailman 3 handle these cases any 
differently?

Thank you,
Pete
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
    https://mail.python.org/archives/list/mailman-users@python.org/
Member address: arch...@jab.org

Reply via email to