Re: [Mailman-Users] invites for large user list fails
Mark Sapiro wrote: Anne Ramey wrote: Is there a known problem with inviting relatively large groups of addresses at once, ex. 6K at a time? I usually just subscribe, so I haven't run into this before, but I have a list owner who gets an error when trying to subscribe a list of 6000 addresses, but I've been breaking it up to smaller groups (400) and they seem to work fine. But when I get up to 1000+ it fails. If we try to invite the whole list we get: Server error! The server encountered an internal error and was unable to complete your request. Error message: Premature end of script headers: admin If you think this is a server error, please contact the webmaster mailto:[EMAIL PROTECTED]. Error 500 on the screen and: admin(10796): [- Mailman Version: 2.1.9rc1 -] admin(10796): [- Traceback --] admin(10796): Traceback (most recent call last): admin(10796): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10796): main() admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 117, in main admin(10796): subscription_confirm(mlist, doc, cookie, cgidata) admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 350, in subscription_confirm admin(10796): userdesc = mlist.pend_confirm(cookie, expunge=False)[1] trimmed The above traceback is not from the error in inviting. It is from an error that occurred in trying to accept (or possibly not accept) an invitation or some other subscription confirmation. It was generated by the confirm CGI, not the admin CGI. I don't have time to look at it in more detail for a couple of days, but I will. It could be due to some corruption in the list's pending database caused by the invite error. It appears you are correct and there is no log for the error from the admin invite except the premature end of headers from apache (see below). This error didn't really tell me what was wrong, but I guess I'm just not reading it right. This was the only thing I could find that seemed to be an error: TypeError: unsubscriptable object Does this mean there was just one address on the list that freaked it out? f it is one email address, how do I tell which one? They all look OK to me when I scroll through. I think the 'invite large list' error is the CGI running into an Apache imposed CPU time limit and thus being killed and not given a chance to log any error. You may find more info in the apache error_log. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.018.htp which has to do with memory limits and MemoryError from Mailman/Python, but in this case, you would be looking for an RLimitCPU directive in your Apache config, not RLimitMEM. I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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:
Re: [Mailman-Users] List creator's (authentication) password
Wanjiku Maina wrote: Can the list creator password be null? Yes and no. You can set the password to the null string, but the list create script itself only accepts non-null passwords. You could modify the Mailman/Cgi/create.py script itself to just not require a password or to change the List creator's (authentication) password: message to something like List creator's password (enter x): But is your server accessible from the internet? If so, do you really want to allow anyone in the world to create and administer (and send spam from) lists on your server. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Anne Ramey wrote: I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. I suspect there may be a problem with the pending database for this list. Download http://veenet.value.net/~msapiro/scripts/list_pending (mirrored at http://fog.ccsf.edu/~msapiro/scripts/list_pending), save it in Mailman's bin/ directory and run it on the offending list and see what happens. It will probably throw the TypeError: unsubscriptable object exception. If so, there is at least one bad entry in the pending.pck file. In that case, I can provide a modified script which will delete the bad entries. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] urgent: no mail shows up as pending...
Maulwurf wrote:
Sep 12 13:24:28 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.114 seconds
Above is from smtp log and is successful delivery of a mailman
generated notice (the message ID is a mailman generated one).
__post
Sep 12 09:56:15 2007 (25625) post to esel-mehl from
[EMAIL PROTECTED], size=8726,
message-id=[EMAIL PROTECTED], 1 failures
Sep 12 10:01:38 2007 (25625) post to safari from [EMAIL PROTECTED],
size=242776, message-id=[EMAIL PROTECTED], success
Sep 12 10:24:20 2007 (25625) post to esel-mehl from
[EMAIL PROTECTED], size=8991,
message-id=[EMAIL PROTECTED], 1 failures
Sep 12 11:54:27 2007 (25625) post to esel-mehl from
[EMAIL PROTECTED], size=10681,
message-id=[EMAIL PROTECTED], 1 failures
Sep 12 12:08:23 2007 (25625) post to beatboxing from
[EMAIL PROTECTED], size=7727,
message-id=[EMAIL PROTECTED], 1 failures
does not seem related (time earlier...)
The failures correspond with messages in the smtp_failure log.
smtp could be related - but here everything seems alright, doesn't it?
__smtp
Sep 12 13:08:20 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.100 seconds
Sep 12 13:24:28 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.114 seconds
Sep 12 13:29:20 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.120 seconds
Sep 12 13:32:35 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.497 seconds
Sep 12 13:32:36 2007 (25625)
[EMAIL PROTECTED] smtp to esel-mehl for
1 recips, completed in 0.065 seconds
These too are all normal delivery of Mailman generated notices.
__smtp-failure
Sep 12 13:38:27 2007 (25625) All recipients refused: {'[EMAIL PROTECTED]':
(550, '5.1.1 [EMAIL PROTECTED]: Recipient address rejected: User unknown
in local recipient table')}, msgid: mailman.6561.1189597105
Sep 12 13:38:27 2007 (25625) delivery to [EMAIL PROTECTED] failed with
code 550: 5.1.1 [EMAIL PROTECTED]: Recipient address rejected: User
unknown in local recipient table
This is a Mailman generated notice to [EMAIL PROTECTED] which the
outgoing MTA can't deliver.
don't know if one of them is the messages that i have been sending...?!
Probably not, but they might be notices of the held message.
these are my latest entries in error
they don't seem to be related with my sending (at 13:00)
Sep 12 11:50:49 2007 (1557) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Handlers/Moderate.py, line 109, in process
Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
File /usr/lib/mailman/Mailman/Handlers/Hold.py, line 224, in
hold_for_approval
id = mlist.HoldMessage(msg, reason, msgdata)
File /usr/lib/mailman/Mailman/ListAdmin.py, line 189, in HoldMessage
self.__opendb()
File /usr/lib/mailman/Mailman/ListAdmin.py, line 86, in __opendb
self.__db = cPickle.load(fp)
UnpicklingError: invalid load key, 'U'.
Sep 12 11:50:49 2007 (1557) SHUNTING:
1189586196.3920839+935d0b4da5eaa35f51fe0714411d6b1d85fd8d38
snip
Sep 12 12:45:00 2007 (1557) Uncaught runner exception:
Sep 12 12:45:00 2007 (1557) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Handlers/Moderate.py, line 109, in process
Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
File /usr/lib/mailman/Mailman/Handlers/Hold.py, line 224, in
hold_for_approval
id = mlist.HoldMessage(msg, reason, msgdata)
File /usr/lib/mailman/Mailman/ListAdmin.py, line 189, in HoldMessage
self.__opendb()
File /usr/lib/mailman/Mailman/ListAdmin.py, line 86, in __opendb
self.__db = cPickle.load(fp)
MemoryError
Sep 12 12:45:00 2007 (1557) SHUNTING:
1189589342.6301639+c26ce6b7163c2cc5dfeacc835d0cda2c53095ae9
snip
It appears that at least one list has a corrupt request.pck file
causing the UnpicklingError. The MemoryError might also be due to a
corrupt request.pck file.
Run bin/show_qfiles on qfiles/shunt/* to see the shunted messages which
will tell you what they are and what lists they're for.
--
Mark
Re: [Mailman-Users] invites for large user list fails
Mark Sapiro wrote: Anne Ramey wrote: I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. I suspect there may be a problem with the pending database for this list. Download http://veenet.value.net/~msapiro/scripts/list_pending (mirrored at http://fog.ccsf.edu/~msapiro/scripts/list_pending), save it in Mailman's bin/ directory and run it on the offending list and see what happens. It will probably throw the TypeError: unsubscriptable object exception. If so, there is at least one bad entry in the pending.pck file. In that case, I can provide a modified script which will delete the bad entries. Thank you very much for the script. It didn't throw any errors that I could see...just a lot of entries that look like this: cookie: 796cc3d566c11147296cd748690a972a364a479c type: S data: UserDesc [EMAIL PROTECTED] () [amekando] [digest? no] [en] I increased this time on my server # Timeout: The number of seconds before receives and sends time out. # Timeout 1000 from 300 to 1000 and managed to enter 1000 invites at once. It did the same thing with 2000. I think you were right about apache terminating the process. Is anyone else running lists that process large #s of invites at once? What should my apache limit be to be effective? Thanks, Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Anne Ramey sent the message below at 13:14 9/13/2007: I increased this time on my server # Timeout: The number of seconds before receives and sends time out. # Timeout 1000 from 300 to 1000 and managed to enter 1000 invites at once. It did the same thing with 2000. I think you were right about apache terminating the process. Is anyone else running lists that process large #s of invites at once? What should my apache limit be to be effective? End original message. - Why not just process it in batches? If a thousand works fine, then do a thousand at a time. Why is it so important to do it in one gulp? Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Default-Text goodbye_msg
de ren0r wrote: i found that option SEND_GOODBYE_MSG in my Defaults.py - But i want to setup the Default-Text, too. How to do that? Actually, the Defaults.py/mm_cfg.py setting is DEFAULT_SEND_GOODBYE_MSG, not SEND_GOODBYE_MSG. There is no setting for default text for the goodbye_msg. This text has to be set individually for each list. The default is to just send a message with subject 'You have been unsubscribed from the listname mailing list' (translated to the list's preferred language), and an empty body. If the list has a goodbye_msg, that is used as the message body. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman version 2.1.9, content filtering action changed??
Hi, I need some help with unexplained behaviour changes to the Content Filtering action of a Mailman list, version 2.1.9. The Mailman list is Xx, and the unexplained behaviour was first noticed with e-mail postings on/after Sept.6/07. The unwelcome changes are that since Sept.6/07, the Content Filtering configuration is not stripping any e-mail message attachments; even though multipart and image content are listed. Multipart/mixed, and multipart/alternative were stripped from e-mail postings before Sept.6/07. Since Sept.6/07, such offending e-mails are now being Content filtered/rejected to the listowner. No multipart, or image attachments are now being removed from the e-mail posting attempts? Xx list Content Filtering configuration: Should Mailman filter the content of list traffic according to the settings below? (Edit filter_content) [ ] No [X] Yes Remove message attachments that have a matching content type. (Details for filter_mime_types) image multipart(trial addition of: multipart/mixed multipart/alternative image/gif image/jpg resulted in the same multipart rejection of posting.) Remove message attachments that don't have a matching content type. Leave this field blank to skip this filter test. (Details for pass_mime_types) [Blank] (trial addition of: multipart text/plain resulted in the same multipart rejection of posting.) Also, (trial addition of: text/plain resulted in the same multipart rejection of posting.) Remove message attachments that have a matching filename extension. (Edit filter_filename_extensions) doc pdf exe bat cmd com pif ppt scr vbs cpl dat Also, (trial removal of: vcf gif gif jpg jpg resulted in the same multipart rejection of posting.) Remove message attachments that don't have a matching filename extension. Leave this field blank to skip this filter test. (Edit pass_filename_extensions) [Blank] Should Mailman collapse multipart/alternative to its first part content? (Edit collapse_alternatives) [ ] No [X] Yes Should Mailman convert text/html parts to plain text? This conversion happens after MIME attachments have been stripped. (Edit convert_html_to_plaintext) [ ] No [X] Yes Action to take when a message matches the content filtering rules. (Details for filter_action) [ ] Discard [ ] Reject [X] Forward to List Owner [ ] Preserve I wish to re-establish the past, correct content filtering of: multipart/mixed multipart/alternative image/jpg image/gif winmail.dat htm html Since Sept.06/07 There have been 73 postings. There have been 35 multipart rejections/content filtering without stripping. There have been 36 text/plain postings that were accepted (normal). There have been 02 blank, no message body content postings slip through. Can the missing, listed stripping actions be restored to the Content Filtering configuration? Help and advice appreciated. Thank you, Art _ Share More On Messenger with a Windows Live Space http://spaces.live.com/?mkt=en-ca -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman version 2.1.9, content filtering action changed??
Arthur Hatch wrote: I need some help with unexplained behaviour changes to the Content Filtering action of a Mailman list, version 2.1.9. The Mailman list is Xx, and the unexplained behaviour was first noticed with e-mail postings on/after Sept.6/07. And what happened on Sept 6, '07. What changed in your system or your Mailman. The unwelcome changes are that since Sept.6/07, the Content Filtering configuration is not stripping any e-mail message attachments; even though multipart and image content are listed. Multipart/mixed, and multipart/alternative were stripped from e-mail postings before Sept.6/07. Since Sept.6/07, such offending e-mails are now being Content filtered/rejected to the listowner. No multipart, or image attachments are now being removed from the e-mail posting attempts? Because you has said that no multipart or image content-types should be accepted and that such messages should be forwarded to the listowner, so that's what Mailman is doing. It you restore the content filtering settings to what they were befor Sept 6, Mailman will do what it did before Sept 6. Xx list Content Filtering configuration: Should Mailman filter the content of list traffic according to the settings below? (Edit filter_content) [ ] No [X] Yes Remove message attachments that have a matching content type. (Details for filter_mime_types) image multipart(trial addition of: multipart/mixed multipart/alternative image/gif image/jpg resulted in the same multipart rejection of posting.) You are saying remove all content of type multipart/*. Thus anything which is not a single part message of content-type image/* will be filtered to nothing ad forwarded to the list owner per below. Remove message attachments that don't have a matching content type. Leave this field blank to skip this filter test. (Details for pass_mime_types) [Blank] (trial addition of: multipart text/plain resulted in the same multipart rejection of posting.) Also, (trial addition of: text/plain resulted in the same multipart rejection of posting.) Remove message attachments that have a matching filename extension. (Edit filter_filename_extensions) doc pdf exe bat cmd com pif ppt scr vbs cpl dat Also, (trial removal of: vcf gif gif jpg jpg resulted in the same multipart rejection of posting.) This is irrelevant, because any multipart messages (i.e. messages with attachments) have already been completely filtered. Remove message attachments that don't have a matching filename extension. Leave this field blank to skip this filter test. (Edit pass_filename_extensions) [Blank] Should Mailman collapse multipart/alternative to its first part content? (Edit collapse_alternatives) [ ] No [X] Yes This is irrelevant because all multipart/alternative parts have already been removed. Should Mailman convert text/html parts to plain text? This conversion happens after MIME attachments have been stripped. (Edit convert_html_to_plaintext) [ ] No [X] Yes Action to take when a message matches the content filtering rules. (Details for filter_action) [ ] Discard [ ] Reject [X] Forward to List Owner [ ] Preserve I wish to re-establish the past, correct content filtering of: multipart/mixed multipart/alternative image/jpg image/gif winmail.dat htm html Since Sept.06/07 There have been 73 postings. There have been 35 multipart rejections/content filtering without stripping. There have been 36 text/plain postings that were accepted (normal). There have been 02 blank, no message body content postings slip through. Can the missing, listed stripping actions be restored to the Content Filtering configuration? Sure, if you know what the pre Sept 6 settings were. The above does not make clear what you actually want to accept, but I suggest the following settings. filter_content - Yes filter_mime_types - empty You could put 'image' here, but it isn't necessary if you do the next. You don't want multipart because that will allow only single part text/* and possibly single part application/*, etc. if any MUA will create such a message. accept_mime_types - multipart text message/rfc822 This will accept multipart/* and message/rfc822 parts for further examination, but will only accept text/* parts from within those parts. filter_filename_extensions - irrelevant, because no attached files that aren't text/* will make it past accept_mime_types pass_filename_extensions - irrelevant, because no
Re: [Mailman-Users] Mailman version 2.1.9, content filtering action changed??
Mark Sapiro wrote: Arthur Hatch wrote: Remove message attachments that have a matching content type. (Details for filter_mime_types) image multipart(trial addition of: multipart/mixed multipart/alternative image/gif image/jpg resulted in the same multipart rejection of posting.) You are saying remove all content of type multipart/*. Thus anything which is not a single part message of content-type image/* will be filtered to nothing ad forwarded to the list owner per below. Sorry, that should say Thus anything which is not a single part message of content-type other than image/* will be filtered to nothing and the original forwarded to the list owner per below. -- 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
