[Mailman-Users] Post-subscription processing

Jim Popovitch jimpop at gmail.com
Fri Aug 16 06:39:41 CEST 2013

On Thu, Aug 15, 2013 at 11:46 PM, Jay Ashworth <jra at baylink.com> wrote:
> ----- Original Message -----
>> From: "Mark Sapiro" <mark at msapiro.net>
>> On 08/15/2013 07:17 PM, Jim Popovitch wrote:
>> > What's the sanest way to export a list of current subscribers
>> > everytime there is a new subscriber? I want to maintain a table of
>> > current list members (for postfix to reject if to:list !=
>> > from:subscriber)
>> How about unsubscribes? Changes of address? I would suggest that the
>> most reliable way is to put hooks in the
>> Mailman/OldStyleMemberships.py
>> member adaptor routines addNewMember and removeMember. This will get
>> changes of address too because that is done by a remove and add.
> Perhaps I'm missing something, but doesn't Mailman already have "only
> allow members to post to the list"?
> NANOG had to make special provisions, but that was because they wanted
> to have a read-only status to put people in when they needed a timeout.

The SDLU list is whitelist'ed from spamassassin processing, so a fair amout
of spam from non-members gets into the moderator queue. The goal is to
reject at the MTA where sender is not in a sender_access restriction table
(which will be maintained by this modification to Mailman).

Mark, thanks for the ideas and input. I want to avoid the cron solution, in
order to prevent racing issues with folks who subscribe and immediately

-Jim P.

More information about the Mailman-Users mailing list