[Mailman-Users] Posts by non-subscribers not getting automatically discarded
I have two lists which have started being spammed by non-members and I have tried to set it for automatic discarding with no notification to the admin. However, I still get notices that my attention is required. When I look at the list I see, for each problem post: + the post is being deferred due to improper content + I get the options to discard or ban them forever I do not have content filtering turned on. What am I doing wrong? Thanks, -Tom -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Gmail RFC 2822
I am not sure the best place to solve this problem but I will start with this list since the problem is impacting a heavy traffic mailman listserv. Google recently started enforcing only a single From: header in RFC2822 causing bounces to members of a very heavy traffic list. A single person with bad mail client configuration is getting all of the Google Apps recipients removed from a list frequently. Postfix log entry: May 15 8:49:57 list01 postfix/smtp[27955]: 35C865058D2: to= jsm...@example.com, relay=aspmx.l.google.com[74.125.137.27]:25, delay=3.1, delays=0.07/2.3/0.03/0.61, dsn=5.7.1, status=bounced (host aspmx.l.google.com[74.125.137.27] said: 550-5.7.1 [126.24.19.8 11] Our system has detected that this message is not 550-5.7.1 RFC 2822 compliant. To reduce the amount of spam sent to Gmail, this 550-5.7.1 message has been blocked. Please review 550 5.7.1 RFC 2822 specifications for more information. f47si18577759yhf.187 - gsmtp (in reply to end of DATA command)) http://webapps.stackexchange.com/questions/42771/emails-sent-to-gmail-domain-suddenly-not-rfc-2822-compliant-possible-to-bypass My question is can Mailman strip out the duplicate From: headers leaving the first one? I have searched for a Postfix solution with no luck. I guess I could work up a procmail solution for all inbound mail but really didn't want to add that layer of complexity if it could be handled by Postfix or Mailman. Thanks, 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Posts by non-subscribers not getting automatically discarded
On 05/15/2013 07:48 AM, Tom Browder wrote: However, I still get notices that my attention is required. When I look at the list I see, for each problem post: + the post is being deferred due to improper content The phrase improper content does not appear in any standard GNU Mailmamn hold reason. Either you are not reporting the actual reason or you have a custom or modified handler in the pipeline ahead of Moderate or both. Moderate is the handler that will apply generic_nonmember_action to a non-member post. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Gmail RFC 2822
On 05/15/2013 08:45 AM, Dave Jones wrote: My question is can Mailman strip out the duplicate From: headers leaving the first one? I have searched for a Postfix solution with no luck. I guess I could work up a procmail solution for all inbound mail but really didn't want to add that layer of complexity if it could be handled by Postfix or Mailman. Mailman can do this, but it requires a custom handler http://wiki.list.org/x/l4A9. Alternatively, you could use header_filter_rules with a regexp like ^From:(.|\n)*^From: to detect multiple From: headers and reject the post. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Posts by non-subscribers not getting automatically discarded
On Wed, May 15, 2013 at 12:47 PM, Mark Sapiro m...@msapiro.net wrote: On 05/15/2013 07:48 AM, Tom Browder wrote: ... + the post is being deferred due to improper content The phrase improper content does not appear in any standard GNU Mailmamn hold reason. Either you are not reporting the actual reason or you have a custom or modified handler in the pipeline ahead of Moderate I'm sorry, you're correct, Mark. I forgot you told me earlier how to write such a handler which I implemented successfully. You said: You need to implement a custom handler http://wiki.list.org/x/l4A9. That FAQ contains a skeleton example MyHandler.py which does what you ask and more. So I guess the real question is how do I postpone that handler until AFTER the check for whether the poster is a member? After reviewing the original implementation instructions I think I can fix the problem. Consider the problem solved unless I run into problems. Thanks so much! Best regards, -Tom -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Search by Message-ID, preserving Cc for direct recipients
On 05/14/2013 10:17 AM, Jed Brown wrote:
I would like to be able to search the archives of a mailman list using
the Message-ID, ideally using a stable URL like
http://mid.gmane.org/${message_id}
http://mail-archive.com/search?l=midq=${message_id}
but preferably on our own host as we're not currently mirrored and would
rather link to our own archives when referencing on old discussion on
the list. Our current archives (e.g., [1]) are searched using htdig,
but it doesn't seem to support query by Message-ID. Your wiki page [2]
also suggests Swish, MnoGoSearch, and Namazu. Can any of these search
by Message-ID, or is our best bet to get indexed by mail-archive.com and
direct people there?
The Message-ID of the post is in the HTML page containing the post, but
it is only in an In-Reply-To= fragment of a mailto: URL that isn't
indexed in htdig. Also, it's URL encoded so , and @ are %3C, %3E and
%40 respectively. The actual Message-ID: headers are in the periodic
*.txt files.
This leads to a few possibilities such as teaching htdig to index the
.txt files (may be tricky, I just spent a couple of minutes looking at
this and didn't see it), changing the noindex start and end tags in the
list's archives/private/LIST/htdig/LIST.conf file so that everything in
the HTML files including the URL encoded Message-ID is indexed or
writing a separate CGI search script to search the .txt files for the
Message-ID.
Or, use mail-archive.com which is probably simplest.
Second question: Why are direct recipients dropped from the Cc header of
the copy sent via the list? This seems partially addressed in the
archives [3], but I think it's important for high-volume lists when
people filter conversations based on whether they are a direct
recipient. Is there an option somewhere to keep Cc headers intact
without changing other behavior?
[1] http://lists.mcs.anl.gov/pipermail/petsc-dev/
[2] http://wiki.list.org/display/DOC/How+do+I+make+the+archives+searchable
[3] http://mail.python.org/pipermail/mailman-developers/2006-May/018777.html
I've learned a lot in the last 7 years ;)
The reason is to keep the Cc: list from growing excessively long in long
threads involving many people (see the subsequent post(s) in that thread).
--
Mark Sapiro m...@msapiro.netThe 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
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Search by Message-ID, preserving Cc for direct recipients
Mark Sapiro m...@msapiro.net writes: The Message-ID of the post is in the HTML page containing the post, but it is only in an In-Reply-To= fragment of a mailto: URL that isn't indexed in htdig. Also, it's URL encoded so , and @ are %3C, %3E and %40 respectively. The actual Message-ID: headers are in the periodic *.txt files. This leads to a few possibilities such as teaching htdig to index the .txt files (may be tricky, I just spent a couple of minutes looking at this and didn't see it), changing the noindex start and end tags in the list's archives/private/LIST/htdig/LIST.conf file so that everything in the HTML files including the URL encoded Message-ID is indexed or writing a separate CGI search script to search the .txt files for the Message-ID. Or, use mail-archive.com which is probably simplest. Okay, thanks. I'll talk with the others here and decide what to do. I've learned a lot in the last 7 years ;) The reason is to keep the Cc: list from growing excessively long in long threads involving many people (see the subsequent post(s) in that thread). Yeah, I saw that, but I don't care how long the Cc list gets. I would rather allow people to filter aggressively and not worry about missing posts that may be relevant to them. It's common on other lists (evidently not those managed by mailman, vger.kernel.org is a high-profile example) to by convention, always Cc everyone that is likely to be interested. Asking recipients to write rules in terms of thread ancestry isn't sufficient either: when we later do more work that is somehow related, we might start a new thread and Cc everyone from prior threads that were related. If the list chronically drops Cc, it can be hard to figure out everyone that should be Cc'd in a new topic. Anyway, can I interpret your response as being that mailman always drops Cc and there is no configuration option? -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Search by Message-ID, preserving Cc for direct recipients
On 05/15/2013 12:47 PM, Jed Brown wrote:
Anyway, can I interpret your response as being that mailman always drops
Cc and there is no configuration option?
I guess that depends on what you call a configuration option.
You could put this in mm_cfg.py
GLOBAL_PIPELINE.remove('AvoidDuplicates')
That would just remove the Handler so every list member that is a direct
recipient would receive both the list and the direct copy regardless of
her avoid duplicates setting, or you could apply the attached patch to
Mailman/Handlers/AvoidDuplicates.py, or you could patch the module but
name the patched module say Mailman/Handlers/MyAvoidDuplicates.py and put
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('AvoidDuplicates'),
'MyAvoidDuplicates')
GLOBAL_PIPELINE.remove('AvoidDuplicates')
im mm_cfg.py. See the FAQ at http://wiki.list.org/x/l4A9. Note: the
first line is wrapped but it doesn't matter because of Python's implies
continuation inside parens. Also note that this latter method is
preferable to simple patching AvoidDuplicates.py for reasons mentioned
in the FAQ.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--- Mailman/Handlers/AvoidDuplicates.py 2008-11-14 10:54:42.0 -0800
+++ Mailman/Handlers/AvoidDuplicates.patched2013-05-15 13:05:58.477617000
-0700
@@ -85,8 +85,8 @@
if send_duplicate:
msgdata.setdefault('add-dup-header', {})[r] = True
newrecips.append(r)
-elif ccaddrs.has_key(r.lower()):
-del ccaddrs[r.lower()]
+# elif ccaddrs.has_key(r.lower()):
+# del ccaddrs[r.lower()]
else:
# Otherwise, this is the first time they've been in the recips
# list. Add them to the newrecips list and flag them as having
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Search by Message-ID, preserving Cc for direct recipients
Mark Sapiro m...@msapiro.net writes:
On 05/15/2013 12:47 PM, Jed Brown wrote:
Anyway, can I interpret your response as being that mailman always drops
Cc and there is no configuration option?
I guess that depends on what you call a configuration option.
You could put this in mm_cfg.py
GLOBAL_PIPELINE.remove('AvoidDuplicates')
That would just remove the Handler so every list member that is a direct
recipient would receive both the list and the direct copy regardless of
her avoid duplicates setting,
That's a side-effect that we don't want.
or you could apply the attached patch to
Mailman/Handlers/AvoidDuplicates.py, or you could patch the module but
name the patched module say Mailman/Handlers/MyAvoidDuplicates.py and
put
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('AvoidDuplicates'),
'MyAvoidDuplicates')
GLOBAL_PIPELINE.remove('AvoidDuplicates')
im mm_cfg.py.
This looks reasonable.
I think this is sufficiently useful to justify supporting without
patching, but this patch isn't hard to carry. Thanks for your detailed
answer.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Domain not found problems
I'm having problems with DOMAIN not found errors. Is there anyway to edit/remove them from the qfiles/out .pck files? They don't seem to be getting purged by mailman and hang around way too long. I'm using postfix and mailman 2.1.12 under ubuntu 8.04. I found item 4.20 in the FAQ, but I'm not sure if it would work and still working on learning postfix as my normal admin is ill. I'd only want it to work for mailman and not for other users regarding this problem. I'm disabled due to vision problems so I did look through the archives until my eyes went buggy. Thanks -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Domain not found problems
On 05/15/2013 05:02 PM, Richard Shetron wrote: I'm having problems with DOMAIN not found errors. Is there anyway to edit/remove them from the qfiles/out .pck files? They don't seem to be getting purged by mailman and hang around way too long. If the MTA (Postfix) is returning a 4xx status for the domain not found, Mailman will move the queue entry to the retry queue and it will be retried (moved back to the out queue) every DELIVERY_RETRY_WAIT seconds (default 1 hour) until it is DELIVERY_RETRY_PERIOD (default 5 days) old at which time the remaining undelivered recipients will be treated as a bounce. If that is too long to wait, you can shorten the time by setting DELIVERY_RETRY_PERIOD = days(1) or maybe DELIVERY_RETRY_PERIOD = hours(12) or whatever in mm_cfg.py, or since the deliverable addresses should have been delivered, simply remove the .pck file from the queue. To be more selective about which recipients to remove, see http://www.msapiro.net/scripts/remove_recips I'm using postfix and mailman 2.1.12 under ubuntu 8.04. I found item 4.20 in the FAQ, but I'm not sure if it would work and still working on learning postfix as my normal admin is ill. I'd only want it to work for mailman and not for other users regarding this problem. Then this is not what you want as it would affect all mail. Further, it just moves the problem to Postfix which probably keeps retrying at intervals until its expiration time elapses. -- Mark Sapiro m...@msapiro.netThe 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
