Hi all!
We've got 3 students working on improved archives for Mailman as part of
Google Summer of Code this year, and before they start writing code
we'd like to gather some data on how people really use the archives. If
you have a minute, it'd help us a whole lot if you could fill out this
Khalil Abbas wrote:
>
>now if I changed this can...@mydomain email to act as a forwarder to the 6
>cancellation addresses of the 6 lists, so each incoming email gets distributed
>to :
>
>
>
>list1-le...@mydomain
>
>list2-le...@mydomain
>
>list3-le...@mydomain
>
>list4-le...@mydomain
>
>list5-le.
hello,
I'm running 6 mailing lists and having a hard time with cancellation requestes,
for I have one email address : can...@mydomain and then I collect all addresses
in the mailbox and remove them from all the 6 lists manually ..
now if I changed this can...@mydomain email to act as a f
On 05/27/10 01:38, Stephen J. Turnbull wrote:
No we weren't. I didn't understand that the policy of stripping
headers on entry to Mailman proposed in earlier messages had been
transmuted to presume an archive of pre-stripped messages.
*nod*
That's why I backed up and tried to clarify. ;)
Nathan A Trapp wrote:
>After much research, I am rather stumped at how to modify the mailman
>authentication system. I was wondering if anyone could point me towards the
>right Python files to edit in order to implement an alternate authentication
>scheme (such as CAS) for mailman administrativ
After much research, I am rather stumped at how to modify the mailman
authentication system. I was wondering if anyone could point me towards the
right Python files to edit in order to implement an alternate authentication
scheme (such as CAS) for mailman administrative login. I know I've seen t
