Mark Sapiro writes: > To: the_list@... > Sender: her_real_address@... > From: the_list_or_some_bogus_address@...
*Don't* recommend using a bogus address -- that requires skill on the part of the user. The list address is "known good", use that. Problem example: if she's not at yahoo.com and uses a fake yahoo.com address, DMARC will cause bounces from random users whose providers respect p=reject. Of course you can mitigate this, but it's just *one* example, there are plenty of other ways this could go wrong, and explaining the constraints to the user just isn't worth the effort. Larry's answer (get a throwaway address) is the one that protects her privacy best, though. A sufficiently persistent attacker can probably trace her through the authenticating IP, but that would be a lot of effort. Use of an alias (eg, AOL screen name) or the Sender header probably exposes her "real" mailbox far too much for her comfort. ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
