Perhaps you are interested:
I have written a mailman authentification CGI for F*EX
(Frams' Fast File Exchange http://fex.rus.uni-stuttgart.de/)
The F*EX adminstrator can enable mailman mailing lists for using F*EX.
The mailing list user then can use F*EX for sending arbitrary big files to
any other user.
You can see such a F*EX mailman authentification on
Ullrich Horlacher Server- und Arbeitsplatzsysteme
Rechenzentrum E-Mail: horlacher(a)rus.uni-stuttgart.de
Universitaet Stuttgart Tel: ++49-711-685-65868
Allmandring 30 Fax: ++49-711-682357
70550 Stuttgart (Germany) WWW: http://www.rus.uni-stuttgart.de/
-----BEGIN PGP SIGNED MESSAGE-----
I recently had a request to make it so a Mailman domain I had setup
would include a default set of email addresses in the
accept_these_nonmembers field of each list. I thought it was a
reasonable request as these people are responsible essentially all
things in that domain. Default.py and mm_cfg.py are not currently setup
to allow this.
Does anyone think this is a reasonable feature request?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
I am working on implementing openID server for the mailman setup I am
I have started using mailman only recently and need help/feedback on my
We want to provide the list users an option whether or not to have enable
On the "" page, the users will see an option for
1. Enable/Disable openID login for your subscription
2. Sign in with existing openID login for your subscription
*1. Enable/Disable openID login for your subscription* *account*
For enabling and diabling the openID feature, the users login their
subscribed accounts as they do now for changing any of the subcription
On this page if they enable the openID feature, they recieve an automated
reply with their openID identifier.
The password for the openID identifier is the same as that for the
subscription accounts. If they change their subscription passwords, their
openID password gets changed too.
*2. Sign in with existing openID login*
The user gets redirected to a page where it enters it's openID identifer and
the password and can now manage its account settings with the openID
identifier. This authentication and further logging, modification of
subscription configurations will be handled by the openID server.
As I understand, the *changes that need to be made to the existing mailman
code* include the following:
Changing the MemberAdaptor.py and UserDesc.py for including information
whether or not openID identifier is enabled for a paricular user.
Propogating changes made to openID-identified-accounts to the subscription
Changing the webpage interfaces for provinding and allowing users to access
I want to know if there's already an openID enabled version of mailman
And what files would I need to make changes to include openID support in
Is there any reason something like DEFAULT_ACCEPT_THESE_NONMEMBERS
hasn't been pushed up into MailList.py? It would be handy for me to
apply such a default, though I realize I may be in the minority. I am
considering applying a small patch to support this, but would like to
know if something like this might be implemented in the future by your
I communicated briefly with msapiro in #mailman on freenode and it
sounded like some work on mailman 3 (styles / templates) might be an
area this would fall into. This email is mostly a follow up to see if
any one else has any thoughts on this.
We, the Python.org postmasters, received about 2.200 bounces at Mailman day
from monthly password reminders that did not reach the recipient.
Ralf said such bounces do not increase a mailing list members bounce score.
Is this correct? If it is, can we add such behaviour to the MM3 feature list?
state of mind
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht München Partnerschaftsregister PR 563
I have a customer who wants a one-way distribution list set up that will
handle millions of recipients... like 10 million. It is a double opt-in, and
its not spam.. <g>
I'm thinking this is probably too much for MM 2 to handle. Will MM3 be able
to scale to this size?
If anyone has suggestions for me for current software that can do this, feel
free to email me off-list. Bounce processing is important, as is user management.
I tried creating a new mailing list for xocd and got the error
shown below. You recently created new mailing list, so I thought
you might know about this land mine that I just stepped on while
using the std gui interface:
Bug in Mailman version 2.1.5
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem.
Printing of traceback and other system information has been
explicitly inhibited, but the webmaster can find this
information in the Mailman error logs.
The admin web page mentions having proper authority.
Is it possibly that I just don't know the List creators
BTW, any thoughts on the openembedded effort we discussed earlier?
I'm wrapping up some work on AES and hope to get back to submitting
xtensa kernel patches for xtensa as a part time project.