On 01/14/2019 11:13 AM, Mark Sapiro wrote:
To place the burden on john, he can subscribe both addresses and set j...@example.com to nomail.
This is what I have done for many mailing lists. — I subscribe with one private address for email filtering and reply from another public email address.
I suggest that the member also pick one and toggle the option to hide (the non-public subscribed address) from other subscribers.
To place the burden on you, assuming you have access to Mailman's command line tools, you could periodically (via cron) run a script to list the members, find those with '+' in the local part and add the address without the +... in the local part to the list's accept_these_nonmembers. There is a script at <https://www.msapiro.net/scripts/non_members> (mirrored at <https://fog.ccsf.edu/~msapiro/scripts/non_members>) that can do the adding to accept_these_nonmembers.
I don't see any obvious security related down sides to this. It does open the mailing list up to messages (spam) from some additional addresses. But I can't think of any cases where u...@domain.tld would be different than user+det...@domain.tld. I guess maybe some sort of ticketing system /might/ do something like that. But I bet that the intersection between such configurations and Mailman configured as Mark is describing to be quite small.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------ 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
