On Thu, Apr 23, 2020 at 1:33 AM Rich Kulawiec <r...@gsp.org> wrote: > - I've received erroneous bounces from @email.uscc.net as well. > It should be possible to track down the culprit via Mailman's logs > and the MTA's logs.
Hi Rich, One of the annoyances with both those guys and the swedish folks is that they're not sending messages to the return path, they're responding to the header from address. Mailman at NANOG never sees it. It doesn't pass through their servers. Even if mailman saw it, mailman doesn't use VERP. It has to scan the message to match the subscriber and that doesn't consistently work. The subscriber address forwards to another address, the second address bounces and the bounce message doesn't necessarily contain the original subscriber address. To identify these jokers the ops will probably have to send a unique message to each subscriber with crafted headers. That can be folded in to a message that would go to the list anyway but the capability isn't baked in to mailman. > - There is zero point in obfuscating email addresses in archives or > anywhere else on the 'net. None. There hasn't been any point for > most of twenty years. Not with open subscription where any spammer can join the list to harvest the addresses of everybody who sends. Regards, Bill Herrin -- William Herrin b...@herrin.us https://bill.herrin.us/
