On Wed, Jul 10, 2024 at 3:48 PM Matthew Blissett via Mailman-users < mailman-users@mailman3.org> wrote:
Hi,
With Mailman 2, I have configuration and scripts to reject non-members from posting to lists _during the SMTP connection_. This is better than bouncing (no backscatter), better than discarding messages (the user finds out) and better than moderation (spammy messages aren't forwarded to external email systems).
The configuration and scripts are described here: https://code.launchpad.net/~jimpop/mailman/check_subscriber
Is anything like this built-in to Mailman 3? I cannot find it in Gitlab.
MM2 stored the subscribers' addresses in the /PATH/TO/mailman/lists/LISTNAME/config.pck. MM3 has the subscribers' addresses stored in your favorite DB backend (PostgreSQL, MySQL.Sqlite). So you'll need to do an SQL lookup for the subscribers. I am wondering why you should waste those CPU cycles instead of just having MM3 do its work:
So, when "Default action to take when a non-member posts to the list = Discard", how does the user find out? I suppose it's an MH370 kind situation :(
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]