Philip Guenther <guenther@gac.edu> wrote:
Since confirm operates before the reject list is checked, we're sending out the messages regardless of whether or not we know these people aren't initiating the request.
Didn't someone recently assert that this isn't true?
Yes, and repetitions doesn't make it more true. The reject file is checked before confirm is called in case of a a subscribe request. The only exception is a unsubscribe request. It seems to me rather esoteric that an attacker uses the confirm unsubscribe mechanismn to harass people. At first he would need to know on which lists the people are he want's to harass. I never heard about such cases. I see no reason to extend the rc.request file to prevent something like this. There is also no reject file check in the ordinary rc.request of SL. I general I think there a many (real) security related topics in connection with email and mailing lists which are more worth to discuss (e. g. email forging, privacy) than these obscure scenarios. Werner