summaryrefslogtreecommitdiff
path: root/Mailman/SecurityManager.py
diff options
context:
space:
mode:
authorbwarsaw2002-07-17 19:57:09 +0000
committerbwarsaw2002-07-17 19:57:09 +0000
commit855ca22a19c08d6a7f9b0d78856ca8b4af16f6c6 (patch)
treef832c0ee1fb378a0a63c8d923353642896618a29 /Mailman/SecurityManager.py
parent1c80294e6f84cb174fb5d9f12fd32f871dea0b35 (diff)
downloadmailman-855ca22a19c08d6a7f9b0d78856ca8b4af16f6c6.tar.gz
mailman-855ca22a19c08d6a7f9b0d78856ca8b4af16f6c6.tar.zst
mailman-855ca22a19c08d6a7f9b0d78856ca8b4af16f6c6.zip
process(): Implement a suggestion by David W. Tamkin on list-managers
(forward by JC Lawrence): Nick gave the example, | > Reply-to: listname@listdomain, posting-user@example.com JCL commented, | Having [mutiple addresses in] Reply-To is a Good ... and Damned Useful [Thing]. It seems to me, though, that the list membership would be better served with this form: Reply-To: postauthor@its.domain, listname@listserver.domain because the MUAs with which I'm familiar make it anywhere from slightly easier to far easier for the respondent to remove addresses from the right of the reply's To: than from the left. Also clean up some Pychecker nits.
Diffstat (limited to 'Mailman/SecurityManager.py')
0 files changed, 0 insertions, 0 deletions