summaryrefslogtreecommitdiff
path: root/Mailman/pythonlib
diff options
context:
space:
mode:
authorklm1998-07-12 03:22:42 +0000
committerklm1998-07-12 03:22:42 +0000
commit496988dcbff4c39a61009d2f1a7bccf921e1c232 (patch)
treecf35b843f25bf60087cb5c45dbbd9991a3c23159 /Mailman/pythonlib
parent262e7302dc79352e1dc3c2ebfb4fe80803a5b835 (diff)
downloadmailman-496988dcbff4c39a61009d2f1a7bccf921e1c232.tar.gz
mailman-496988dcbff4c39a61009d2f1a7bccf921e1c232.tar.zst
mailman-496988dcbff4c39a61009d2f1a7bccf921e1c232.zip
Informatively reject mail-command attempts to subscribe
already-subscribed members. (The prior checkin was for web-based subscription attempts.) NOTE that both these already-subscribed actions can constitute privacy leaks - someone could venture subscription attempts with addresses which they are trying to test for already-existing membership - and this response will provide unequivocal confirmation in the cases when the addresses are subscribed. One possible remedy is to send the refusal to the address being subscribed. This way the person taking the action gets no additional info unless they have access to the subscribees email channel. Problem with this is that it complicates the mail-command refusal process substantially, since it's currently geared, very simply, to send the refusal to the requesting address. Do we think the privacy leak is important enough to fill this hole?
Diffstat (limited to 'Mailman/pythonlib')
0 files changed, 0 insertions, 0 deletions