Suppress moderation message in mailman 2.1 ?
I run a two-way usenet <-> mailman gateway. When I forward someting from the usenet group to mailman, it gets moderated, which is what I want since a fair amount of the stuff in the usenet group is spam. When mailman mdoerates the message, it sends the usual moderation message to the usenet poster, which many posters find confusing. Even worse, since many usenet posters use fake addresses, the moderation messages can go to random strangers.
Is there something I can put in the message header to say not to send the moderation messages? I don't want to turn them off globally since they're fine for people who send mail directly to the list.
R's, John
On 11/06/2017 07:05 AM, John Levine wrote:
I run a two-way usenet <-> mailman gateway. When I forward someting from the usenet group to mailman, it gets moderated, which is what I want since a fair amount of the stuff in the usenet group is spam.
I can't understand what the issue is. Normally, posts from usenet will be accepted without moderation unless the poster happens to be a moderated list member, or possibly if LISTNAME-bounces@list.domain is a moderated member hopefully with delivery disabled, or if the list's emergency moderation is set, but emergency holds send no notices.
So my first question is how/why are the posts being held?
When mailman mdoerates the message, it sends the usual moderation message to the usenet poster, which many posters find confusing.
This should not happen. The code that sends the user notice of a held post specifically exempts posts from usenet.
Even worse, since many usenet posters use fake addresses, the moderation messages can go to random strangers.
Is there something I can put in the message header to say not to send the moderation messages? I don't want to turn them off globally since they're fine for people who send mail directly to the list.
I don't understand why they are sent now. They shouldn't be. In order to understand what's happening, I need to know why the message is held, i.e. what is the reason given in the admindb UI or mailman's vette log, and whether you have done anything specific to cause the message to be held
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In article 851008d1-e6dd-bafe-9e85-e1ebaf1b81a9@msapiro.net you write:
So my first question is how/why are the posts being held?
Because the people posting from usenet aren't list subscribers. They read the messages on usenet.
When mailman mdoerates the message, it sends the usual moderation message to the usenet poster, which many posters find confusing.
This should not happen. The code that sends the user notice of a held post specifically exempts posts from usenet.
Clearly it is expecting something that my gateway isn't including. How does it try to guess that a message came from a usenet gateway?
R's, John
On 11/06/2017 10:17 AM, John Levine wrote:
In article 851008d1-e6dd-bafe-9e85-e1ebaf1b81a9@msapiro.net you write:
So my first question is how/why are the posts being held?
Because the people posting from usenet aren't list subscribers. They read the messages on usenet.
Then your Mailman must be 2.1.17 or later, and you have a regexp matching anything in hold_these_nonmembers or your Mailman is older than 2.1.3. From 2.1.3 to 2.1.16, posts from usenet were not subject to membership tests. Since then, posts from usenet with a sender who is a moderated member or a non-member matching a pattern in hold_these_nonmembers will be held.
When mailman mdoerates the message, it sends the usual moderation message to the usenet poster, which many posters find confusing.
This should not happen. The code that sends the user notice of a held post specifically exempts posts from usenet.
Clearly it is expecting something that my gateway isn't including. How does it try to guess that a message came from a usenet gateway?
cron/gate_news sets fromusenet = True in the message metadata. This and not sending notices to posters from usenet has been the case since at least 2.1.1.
The code in cron/gate_news is
# Post the message to the locked list inq = get_switchboard(mm_cfg.INQUEUE_DIR) inq.enqueue(msg, listname = mlist.internal_name(), fromusenet = 1)
The code in Mailman/Handlers/Hold.py is
# We may want to send a notification to the original sender too fromusenet = msgdata.get('fromusenet') # Since we're sending two messages, which may potentially be in different # languages (the user's preferred and the list's preferred for the admin), # we need to play some i18n games here. Since the current language # context ought to be set up for the user, let's craft his message first. cookie = mlist.pend_new(Pending.HELD_MESSAGE, id) if not fromusenet and ackp(msg) and mlist.respond_to_post_requests and \ mlist.autorespondToSender(sender, mlist.getMemberLanguage(sender)):
followed by sending the message conditional on 'not fromusnet' and the other conditions.
What do you have in those modules? What Mailman version is this? What packager's patches are included?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
In article 8d629943-93d6-2546-71f9-4484d8ecf431@msapiro.net you write:
cron/gate_news ....
I'm not using that. My news server isn't on the same network as the mailman system, and the gateway is basically a few lines of procmail and formail I've been using for a decade to splice usenet groups to various mailing lists.
I don't know what version of mailman they use, it's ntp.org.
R's, John
On November 6, 2017 7:25:11 PM PST, John Levine johnl@taugh.com wrote:
In article 8d629943-93d6-2546-71f9-4484d8ecf431@msapiro.net you write:
cron/gate_news ....
I'm not using that. My news server isn't on the same network as the mailman system, and the gateway is basically a few lines of procmail and formail I've been using for a decade to splice usenet groups to various mailing lists.
I don't know what version of mailman they use, it's ntp.org.
So basically there's nothing you can do. Your process posts from usenet like any other post. Treating those differently would require source modification on the Mailman server.
You could set respond_to_post_requests to No, but then email posters wouldn't get notifications either.
Or you could try to use Mailman's usenet gateway if the host supports it.
-- Mark Sapiro mark@msapiro.net Sent from my Not_an_iThing with standards compliant, open source software.
Why not, when sending usenet posts to the list, merely change the 'from' address to yourself (or a special-purpose mailbox, or something)? This would require only changes to stuff you made yourself (the usenet -> list processing).
Adam Goldberg AGP, LLC +1-202-507-9900
-----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+adam=agp-llc.com@python.org] On Behalf Of Mark Sapiro Sent: Tuesday, November 07, 2017 9:43 AM To: mailman-users@python.org; John Levine johnl@taugh.com Subject: Re: [Mailman-Users] Suppress moderation message in mailman 2.1 ?
On November 6, 2017 7:25:11 PM PST, John Levine johnl@taugh.com wrote:
In article 8d629943-93d6-2546-71f9-4484d8ecf431@msapiro.net you write:
cron/gate_news ....
I'm not using that. My news server isn't on the same network as the mailman system, and the gateway is basically a few lines of procmail and formail I've been using for a decade to splice usenet groups to various mailing lists.
I don't know what version of mailman they use, it's ntp.org.
So basically there's nothing you can do. Your process posts from usenet like any other post. Treating those differently would require source modification on the Mailman server.
You could set respond_to_post_requests to No, but then email posters wouldn't get notifications either.
Or you could try to use Mailman's usenet gateway if the host supports it.
-- Mark Sapiro mark@msapiro.net Sent from my Not_an_iThing with standards compliant, open source software.
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/adam%40agp-llc.com
Hello
Long time ago I asked, why Mailman delivers only to server-internal recipients. We found out, that the reason was the removed localhost from whitelist in plesk outbound filter. My hoster (I'm only custumer) could not bring to function the recommended solutions, either connecting to a new free port or to a port with authetication. He was doubtful to apply the patch, described in https://bugs.launchpad.net/mailman/+bug/558281 .
Now I changed the hoster, but his Mailman works in the same manner. I suspect, every lowcoast hoster has configured his apache-plesk-package in the same way, I wil be the only one mailman.user, and the operator is not familar to that.
Is there meanwhile an implementation of this patch in newer version, so an reinstallation of MM gives secure and easy adjustments for that case? Or a foolproof step by step instruction to fix it ?
greats Kapuzino
On 11/11/2017 10:34 PM, Kapuzino wrote:
He was doubtful to apply the patch, described in https://bugs.launchpad.net/mailman/+bug/558281 . ... Is there meanwhile an implementation of this patch in newer version, so an reinstallation of MM gives secure and easy adjustments for that case?
That "bug" was fixed in Mailman 2.1.23 released over a year ago (27-Aug-2016). Any 2.1.23 or later Mailman should have this feature.
Or a foolproof step by step instruction to fix it ?
Nothing is foolproof ;)
The actual patch is at http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1649. To apply it in an older Mailman, go to that link and click the "download diff" link to obtain the actual patch. To apply the patch to an installed Mailman, change the first 3 lines from
=== modified file 'Mailman/Defaults.py.in' --- Mailman/Defaults.py.in 2016-04-21 15:01:01 +0000 +++ Mailman/Defaults.py.in 2016-05-06 21:44:28 +0000
to
=== modified file 'Mailman/Defaults.py' --- Mailman/Defaults.py 2016-04-21 15:01:01 +0000 +++ Mailman/Defaults.py 2016-05-06 21:44:28 +0000
I.e. change Defaults.py.in to Defaults.py and delete the lines beginning with
=== modified file 'NEWS' --- NEWS 2016-05-05 01:27:19 +0000 +++ NEWS 2016-05-06 21:44:28 +0000
Then, if you don't know how to apply the resulting patch, you probably shouldn't be doing it, but with the modified patch in a file, cd to the directory containing the Mailman/ directory and do
patch -p0 < /the/file/containing/the/patch
You will then have to set things like
SMTP_AUTH, SMTP_USER, SMTP_PASSWD, SMTP_USE_TLS, SMTPHOST and SMTPPORT in mm_cfg.py.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Adam Goldberg -
John Levine -
Kapuzino -
Mark Sapiro