Comment 3 for bug 1325568

I agree that both features overlap. Maybe they overlap the same way as the anonymous_list and reply_goes_to_list feature? Both rewrite the reply-to address with the list address, but their intentions are differently.

I hope I am able to show the difference, I think, there is: The intention of my patch is to provide some pseudo-identity on an anonymous_list. The intention of the from_is_list feature -- correct my if I am wrong -- is to agree with spam protection standards.

What my propsal does differently is, that

* it works hand in hand with anonymous_list
quote from the documentation of from_is_list
"It is not useful to apply actions other than No to an anonymous list, and if you do so, the result may be surprising."
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Gui/General.py

* it lets the list admin configure a name: sort of a pseudonym, if you like -- that way a (fixed) name is set even if the sender forgot to configure his/her e-mail client correctly (e. g. forget to set a name at all or accidentally set his/her real name)

* the rewrite by from_is_list is not stored in the archives according to the changelog of 2.1.18
https://launchpad.net/mailman/+milestone/2.1.18
and this bug
https://bugs.launchpad.net/mailman/+bug/1311431
but I think that would defeat the purpose of (pseudo) anonymization.

Maybe "pseudonymous_list" would be a more fitting description for the configuration value or the value could be integrated into the "anonymous_list" configuration? Like this:

[x] no
[ ] anonymous
[ ] pseudonymous

That way it might add less complexity to the mailing list configuration than when it is a separate configuration value.