On 8/16/21 11:10 AM, Carl Zwanzig wrote:

On 8/16/2021 10:30 AM, Jim Dory wrote:

...

I've asked her to run it by the IT department of her corporation, but thought I would ask here in case there is something I need to do instead. I thought that the "on behalf of listname-request@domain.com" was pretty unusual, or something I don't usually see anyway.

Sounds like a microsoft exchange/outlook thing- the "on behalf of" part. Could be they have an internal list that's subscribed to the MM list, or that the MM list member is a secretary/assistant of the final recipient.

If you can, the the full SMTP headers and look at the top/most-recent Received: lines; that'll show the handoff-

(the message I'm replying to) Received: from mail.python.org (mail.python.org [188.166.95.178])     (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))     (No client certificate requested)     by host.hosting.service (Postfix) with ESMTPS id A1FA6487B1     for cpz@tuunq.com; Mon, 16 Aug 2021 15:01:50 -0400 (EDT)

See who it's for in there.

Thanks for the reply. I had her forward the digest message to me, and it appears she did because the subject line says: FWD: listname Digest vol. <etc> . She did add a bit of text to the forward explaining it was from her work email. So headers in the source view prior to her text just show received from her to me. After her little bit of text, it just has the From, Subject, To lines as one sees when receiving any message and then the digest text. So no headers to inspect. Perhaps if I could have her view the digest source and copy/paste it to me, that might be revealing. I'll see if she can do that. I'll have to google how to view source in MS Exchange.

On 8/16/21 11:34 AM, Bruce Johnson via Mailman-Users wrote:

When I’ve gotten these in the past it’s almost always because someone else’s email, or an old email address is getting forwarded to the recipient. I don’t think the 'on behalf of’ stuff is actually from an O365/Exchange system, but whatever that linkprotect link is.

(which link, btw, my campus network won’t let me load because it’s flagged as a malware source…so be careful)

I clicked on the link trusting my linux system would catch malware usually targeting windows, and it redirects to our MM list page. I'll make sure this person contacts her IT dept. to try and figure this out. Thanks for the reply!   /jim

On 8/16/21 8:11 PM, Mark Sapiro wrote:

One thing you can do is enable VERP. Assuming this in Mailman 2.1 since this list is for Mailman 2.1, you enable VERP by putting

VERP_DELIVERY_INTERVAL = 1

in mm_cfg.py. This will change the envelope sender (the bounces address) from

listname-bounces@domain.com>

to

listname-bounces+user=example.com@domain.com>

where replacing the '=' in user=example.com gives the recipient's address.

The other thing you can do is just look at all the digest members of the list. If there aren't too many, you may be able to figure out which it is. use Mailman's

bin/list_members -d -f listname

to get a list of digest members with their 'real name' if available.

Otherwise, as you note, if you can get her to send you the raw message headers, you may be able to get the address from the Received: headers.

Great Mark, will try that VERP trick. She is out of the office for the rest of the week so will have to wait and see.

There's over 1500 subscribers so probably best to search on her corporation's domain - that may return maybe around a couple dozen or so - rather than digest subscribers which are probably a ton.

thanks, Jim

I'd say export the digest subscriber list and then search within it for the domain, or even the username portion of her email address. My office has email addresses on several domains of which all direct to my inbox, but every email domain has the same username. The digest subscribers list is usually only a small percentage of all subscribers.

On Mon, Aug 16, 2021 at 10:59 PM Jim Dory james@dorydesign.com wrote:

On 8/16/21 8:11 PM, Mark Sapiro wrote:

...

One thing you can do is enable VERP. Assuming this in Mailman 2.1 since

this list is for Mailman 2.1, you enable VERP

...

by putting

VERP_DELIVERY_INTERVAL = 1

in mm_cfg.py. This will change the envelope sender (the bounces address)

from

...

listname-bounces@domain.com>

to

listname-bounces+user=example.com@domain.com>

where replacing the '=' in user=example.com gives the recipient's

address.

...

The other thing you can do is just look at all the digest members of the

list. If there aren't too many, you may be

...

able to figure out which it is. use Mailman's

bin/list_members -d -f listname

to get a list of digest members with their 'real name' if available.

Otherwise, as you note, if you can get her to send you the raw message

headers, you may be able to get the address

...

from the Received: headers.

Great Mark, will try that VERP trick. She is out of the office for the rest of the week so will have to wait and see.

There's over 1500 subscribers so probably best to search on her corporation's domain - that may return maybe around a couple dozen or so - rather than digest subscribers which are probably a ton.

thanks, Jim

---

Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@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/