Re: [Mailman-Users] generic_nonmember_action and header_filter_rules
Is mm_cfg.py going to be replaced each time Mailman is upgraded, or
would these changes persist across upgrades?
On Oct 12, 2008, at 8:55 PM, Mark Sapiro wrote:
Russell Clemings wrote:
I have generic_nonmember_action set to reject. I also have
header_filter_rules set to hold if an incoming message has
X-Spam-Flag: YES in its headers.
My current problem is the second test overrides the first -- i.e., if
a non-member tries to post a message flagged as spam, it is held
rather than rejected. As you might imagine, this happens rather
often.
Is there a way to change the order of operations on these filters?
I'd
like to have posts from non-members rejected every time, whether they
match the spam filter or not.
This is cPanel's hack of Mailman (version 2.1.11.cp2), not the real
mccoy, fwiw.
Do you have access to mm_cfg.py? That's what's required to change
this.
IncomingRunner passes the message througe a pipeline of handler
modules. The first one that says hold|reject|discard this message
determins what is done. The default pipeline is
GLOBAL_PIPELINE = [
# These are the modules that do tasks common to all delivery paths.
'SpamDetect',
'Approve',
'Replybot',
'Moderate',
'Hold',
'MimeDel',
'Scrubber',
'Emergency',
'Tagger',
'CalcRecips',
'AvoidDuplicates',
'Cleanse',
'CleanseDKIM',
'CookHeaders',
# And now we send the message to the digest mbox file, and to the
arch and
# news queues. Runners will provide further processing of the
message,
# specific to those delivery paths.
'ToDigest',
'ToArchive',
'ToUsenet',
# Now we'll do a few extra things specific to the member delivery
# (outgoing) path, finally leaving the message in the outgoing
queue.
'AfterDelivery',
'Acknowledge',
'ToOutgoing',
]
SpamDetect does header_filter_rules; Moderate does member moderation
and non-member actions, and Hold does several miscellaneous holds.
To do what you want, you need to reorder the pipeline so that
SpamDetect comes after Moderate.
You could do this by putting the following in mm_cfg.py
GLOBAL_PIPELINE.remove('SpamDetect')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Hold'), 'SpamDetect')
which would remove SpamDetect from the pipeline and then insert it
between Moderate and Hold.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/pennguin%40mac.com
Security Policy: http://wiki.list.org/x/QIA9
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] LDAP
Anne Anderson wrote: Thanks! I checked out the link you sent, and have been talking with my colleagues about whether having list membership tied to LDAP groups would be of benefit to us. What I'm most interested in is whether list administrators and moderators would be able to access their administrative interfaces with their LDAP username and password. I'm not sure if this would work, though, because I think that since mailman asks only for a password (not a username) to get into the administrative interface, it must not know or care who you are as long as you give the right password. Mailman 3 is going in this direction, i.e. a real back end user database with user roles, but current Mailman 2.1/2.2 has as you note just per-list passwords for admin and moderator authentication. Converting this to user/password authentication, whether LDAP based or not, would be a significant change. I'm not aware of anyone having done this. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Users Being Unsubscribed
I run multiple lists using Mailman 2.1.8. Periodically some users receive a message asking them to confirm their unsubscribe from a given list. This happens despite the fact that they have taken no action to unsubscribe. It doesn't happen a lot, but enough that I know something is going on. It has even happened to me and my account that is subscribed to lists. What is triggering the unsubscribe attempt? Is it spam that is doing it. I know that if they ignore message, the unsubscribe attempt will age out, but they, the users don't understand what is going on. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Mailman 2.1.11 compatibility with python 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. I just upgraded to Python 2.6, and Mailman 2.1.11 has some issues. Notably the email module and raising text exceptions. Is any plan to release a version compatible with python 2.6 (or a patch) soon, or I need to downgrade my python installation?. Thanks in advance. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ [EMAIL PROTECTED] - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:[EMAIL PROTECTED] _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBSPUEpplgi5GaxT1NAQLY2AP+NQuIlcUx14aqUgAJ40Jnh2JvvbB5QvAi CrWLAaFDr/GHga22+zrnM9aomn6gMhetyfaKP6eMlCvNJN08t/8Zbm3R3pQB2uTS J7QKuo6KCGIqVS2cpu2BqqM8pnUjG59AaaCRcnzh3xTuPpddD1Vyj39GS303BYp2 42dpoqt40xw= =5B2Z -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.11 compatibility with python 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 14, 2008, at 4:44 PM, Jesus Cea wrote: I just upgraded to Python 2.6, and Mailman 2.1.11 has some issues. Notably the email module and raising text exceptions. Is any plan to release a version compatible with python 2.6 (or a patch) soon, or I need to downgrade my python installation?. I haven't tried it yet, but I'll be upgrading to Python 2.6 on my servers at some point in November. Please be sure to submit bug reports to the Launchpad tracker for any issues you find. If necessary we should release one more version to fix Python 2.6 compatibility issues. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkj1B7kACgkQ2YZpQepbvXFZywCdF7xkl1lHBoW8B3jJbUhjglGE DWIAoJAts5T0jYOc5TDAUDgnA/kP3dlc =+TGI -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Users Being Unsubscribed
David Andrews wrote: I run multiple lists using Mailman 2.1.8. Periodically some users receive a message asking them to confirm their unsubscribe from a given list. This happens despite the fact that they have taken no action to unsubscribe. It doesn't happen a lot, but enough that I know something is going on. It has even happened to me and my account that is subscribed to lists. What is triggering the unsubscribe attempt? Is it spam that is doing it. I know that if they ignore message, the unsubscribe attempt will age out, but they, the users don't understand what is going on. It could be spam, but it would have to be spam that spoofed the members address in the From: header and was sent to the listname-unsubscribe or listname-leave address. It could also be some person, for whatever reason, intentionally trying to unsubscribe someone else, either via email or via the http:/www.example.com/mailman/options/listname web page. As Brad suggests, you need to check MTA logs and web server logs for this activity at the time the confirmation notice was sent to narrow it down. There won't be anything in Mailman's logs about this. Mailman will only log the unsubscribe after it is confirmed. Also, this isn't bounce processing because bounce processing doesn't send an unsubscribe confirmation; it sends a re-enable delivery confirmation. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Users Being Unsubscribed
David Andrews wrote: What is triggering the unsubscribe attempt? Dunno. What's in your logs? Is it spam that is doing it. That's possible, but unlikely. More likely is NDNs, notices to the effect of Your message has been delayed but is still in the queue, etc But without knowing what's in your MTA and Mailman logs, it's impossible to go beyond pulling random straws out of thin air. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
