Barry,
Congratulations, you mail d(a)emon, you! And all the other responsible
d(a)emons. Has it really been 20 years since the NIST workshop?
Skip
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo
Barry> In the General admin page, check the value for
Barry> admin_immed_notify.
>> That's already set to Yes... :-/
Barry> Hmm.
My sentiments exactly.
I'm not at all familiar with the Mailman source code, but it appears that
the decision to send out an admin message is made in
Barry> In MM2.1, the -admin address is an alias for -bounces not -owner.
Thanks for this clarification.
Barry> In the General admin page, check the value for
Barry> admin_immed_notify. That controls whether you get those pending
Barry> subscription notifications and such.
That'
seems to go to all three of us. What I
don't understand is what the cedu-admin address is for and where the admin
messages are going.
It seems clear that I missed something during the 2.0->2.1 upgrade, but I'm
at a loss to see what. Any guid
I seem to recall that one of the original motivations for SpamBayes was to
support spam filtering within Mailman (or nearby, if not within). Has
anyone taken steps to more tightly integrate the two aside from doing
something like running sb_filter.py in front of Mailman's processing? I
think Spa
>> I know this is anal, but it bugs me every time Mailman discards a
>> message then sends me a note with this text:
>>
>> The attached message has been automatically discarded.
>>
>> It should be
>>
>> The attached message was automatically discarded.
Dan>
I know this is anal, but it bugs me every time Mailman discards a message
then sends me a note with this text:
The attached message has been automatically discarded.
It should be
The attached message was automatically discarded.
FYI.
--
Skip Montanaro
Got gigs? http://www.musi
