[Mailman-Users] subscribed address that forwards to secondary address can't be identified

[Mark Sapiro]

On 04/04/2014 02:29 PM, Christopher Adams wrote:
> 
> A person is receiving mail through a list. The address that they are
> currently using (@gmail.com) is not subscribed to the list. I assume that
> means a subscribed address is forwarding to the gmail account. The gmail
> account people don't have any idea what they could have been subscribed as.
> I thought maybe the Mailman or MTA logs would show the susbscribed address
> forwarding to the gmail address. However, I can't find anything, so can't
> identify which address is the culprit.
> 
> Does anyone have an idea how to get to the bottom of this?


The first step is to examine the Received: headers of the post as
received by the gmail user. This may tell you exactly what address
Mailman sent to. If not, it will tell you what MX server the message
went to from the Mailman server which will help narrow the possibilities.

There's no way that Mailman or probably even your local MTA can know
that any particular address they send to ultimately forwards to gmail.

If all else fails, and you have the ability, you can enable Mailman's
VERP. Then each message from Mailman will have the envelope from and
Sender: and Errors-To: headers with the address
LISTNAME-bounces-user=example.com at your.domain where user at example.com is
the address sent to.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan