aaronco thirtysix wrote:
could already view prior archived postings directly via https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug
No surprise there - is publicly archived, after all.
One idea for Michael Or Other Possible BALUG.org Admins(*) pending any possible BALUG-lists-targeting spammers, is similarly as sudoroom.org to consider blocking Tor if that should prove necessary(?)
Has thus far been no reason to do so. And blocking Tor may not be very feasible anyway. See, e.g.: https://support.torproject.org/abuse/i-want-to-ban-tor/ https://www.reddit.com/r/networking/comments/7j1vks/best_way_to_block_tor_on... https://www.google.com/search?q=how+to+block+tor etc.
So far I think the only explicit actions I've needed to do against spammers and bad bots, and has been quite effective thus far: Apache2 tuning (notably to keep bad bots from overwhelming system resources) "of course" some MTA anti-spam stuff doku wiki: disabled web self creation of accounts (from bot abuse) WordPress registration: added captcha for self-registration
Spam posting via Mailman 2 that actually makes it to list has thus far been exceedingly rare ... I think like thus far once in over a decade. Between MTA anti-spam and Mailman itself (most notably generally defaulting to disallowing non-members to post), at least thus far in practice, spam hasn't really been much of an issue for mailman.