I'm reading the following thread from 2004:
http://mail.python.org/pipermail/mailman-users/2004-July/037954.html. I
would like to solve a similar problem. This thread states:
You can use the mailman command-line tools to synchronize against
external databases. There are various people on the
Hi all,
I'm administering a Mailman list using version 2.1.14. It's a private list,
whereby only list members can post to it (generic_nonmember_action is set to
discard).
I've just had an email sent through the list which was sent from a web service
(Evite.com to be precise) by one of the
Hi.
I'm running a mailman (v.2.1.12) mailinglist on a Centos 6.2 system.
Now I'm wondering if the version 2.1.12 that comes with both RHEL6 Centos 6
contain any known bugs that make mailman 2.1.12 vulnerable?
The system is SeLinux enabled.
Regards,
/PGE
Jeremy Fairbrass wrote:
I'm administering a Mailman list using version 2.1.14. It's a private list,
whereby only list members can post to it (generic_nonmember_action is set to
discard).
I've just had an email sent through the list which was sent from a web service
(Evite.com to be precise)
Pro Green European wrote:
I'm running a mailman (v.2.1.12) mailinglist on a Centos 6.2 system.
Now I'm wondering if the version 2.1.12 that comes with both RHEL6 Centos 6
contain any known bugs that make mailman 2.1.12 vulnerable?
See the NEWS file at
David wrote:
Can anyone suggest a better way to find examples and more help for syncing
Mailman with external customer data?
Basically, you have to do the heavy lifting. Mailman's bin/sync_members
tool is what you use to actually sync the list's membership with your
database, but you first have