Mailman-coders May 2006

mailman-coders@python.org

1 participants
37 discussions

[ mailman-Bugs-1498290 ] Footer sometimes appended to last line of message

by SourceForge.net

Bugs item #1498290, was opened at 2006-05-31 11:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498290&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jonathan Kamens (jikamens) Assigned to: Nobody/Anonymous (nobody) Summary: Footer sometimes appended to last line of message Initial Comment: If someone submits a multipart/alternative message, and the text part doesn't have a trailing newline, then the footer is started at the end of the last line in the text part, rather than starting on a new line. I think the code that appends the footer should be fixed so that if the text message doesn't end with a newline, one is added before the footer is appended. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498290&group_…

15 years, 7 months

[ mailman-Bugs-1498213 ] bad email sanitisation issue

by SourceForge.net

Bugs item #1498213, was opened at 2006-05-31 15:26 Message generated for change (Comment added) made by kangbooboo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498213&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: kangoo (kangbooboo) Assigned to: Nobody/Anonymous (nobody) Summary: bad email sanitisation issue Initial Comment: hi, we're using 2.1.5 and when someone added an email address with quotes (") we got errors a bit everywhere and mails not getting sent ^^ I looked into changelog up to 2.1.8 which is current stable and this looks closely to bug #1030228, but different character. I would suggest adding the quote character to the filter (ascii 042) Or better, rewritte the filter but the reverse way. only allow [a-zA-Z0-9\-\_\.\+] for email addresses ? (i made this up from memory but email addresses cannot contain much more ? maybe im saying something stupid here) ---------------------------------------------------------------------- >Comment By: kangoo (kangbooboo) Date: 2006-05-31 15:36 Message: Logged In: YES user_id=671502 i forgot to say this is done when you're not using the web interface to input the email+name (else name or mail with quotes gets rejected as unknown) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498213&group_…

15 years, 7 months

[ mailman-Bugs-1498213 ] bad email sanitisation issue

by SourceForge.net

Bugs item #1498213, was opened at 2006-05-31 15:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498213&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: kangoo (kangbooboo) Assigned to: Nobody/Anonymous (nobody) Summary: bad email sanitisation issue Initial Comment: hi, we're using 2.1.5 and when someone added an email address with quotes (") we got errors a bit everywhere and mails not getting sent ^^ I looked into changelog up to 2.1.8 which is current stable and this looks closely to bug #1030228, but different character. I would suggest adding the quote character to the filter (ascii 042) Or better, rewritte the filter but the reverse way. only allow [a-zA-Z0-9\-\_\.\+] for email addresses ? (i made this up from memory but email addresses cannot contain much more ? maybe im saying something stupid here) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1498213&group_…

15 years, 7 months

[ mailman-Bugs-1497366 ] Differentiate between subscribers/others for held messages

by SourceForge.net

Bugs item #1497366, was opened at 2006-05-30 10:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1497366&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jonas Maebe (jmaebe) Assigned to: Nobody/Anonymous (nobody) Summary: Differentiate between subscribers/others for held messages Initial Comment: I've turned off notifications about messages held for approval, since virtually all of them are spam with forged from-addresses and I don't want to inundate random people with such notifications. However, every now and then the reason is that a subscriber tried to send too big an attachment, or because a mail triggered my html regexp in the privacy filters. Therefore I would like to propose an option to only send "Message held for approval" messages to subscribers, but not to anyone else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1497366&group_…

15 years, 7 months

[ mailman-Bugs-1484722 ] Topic regexes are never applied

by SourceForge.net

Bugs item #1484722, was opened at 2006-05-09 07:28 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1484722&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Jesse Keating (jkeating-redhat) Assigned to: Nobody/Anonymous (nobody) Summary: Topic regexes are never applied Initial Comment: Topic filters are checked via a provided regex. The code that applies regexes to a message, and tags a message with a topic and adds a header is called Tagger.process. This function is only called by a test/ script, to test the code path. In the production code Tagger.process is never called, so a mail is never checked/tagged with a topic, and thus when later checked for who it should be delivered to based on topic, it has no topic so it doesn't get delivered correctly. This is 2.1.8. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-05-29 18:53 Message: Logged In: YES user_id=1123998 Original problem was due to submitter not recognizing that topic regexps are compiled in VERBOSE mode requiring escaping of significant white space. This 'gotcha' is planned to be addressed in the next release. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2006-05-25 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-05-10 20:02 Message: Logged In: YES user_id=1123998 Yes, Tagger is in GLOBAL_PIPELINE, so unless you have redefined GLOBAL_PIPELINE in mm_cfg.py to not include Tagger or the list has a pipeline attribute defined (default lists don't) that doesn't include Tagger, Mailman.Handlers.Tagger.process() is called by IncomingRunner in processing the message through the pipeline. ---------------------------------------------------------------------- Comment By: Jesse Keating (jkeating-redhat) Date: 2006-05-09 07:52 Message: Logged In: YES user_id=1519854 Upon closer looking, it would seem that this could be called through a pipeline. I'm looking in our config to see if we haven't defined this as a pipeline. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1484722&group_…

15 years, 7 months

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists

by SourceForge.net

Bugs item #1495781, was opened at 2006-05-26 15:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495781&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Paul Sokolovsky (pfalcon) Assigned to: Nobody/Anonymous (nobody) Summary: Non-existent class reference while upgrading lists Initial Comment: Mailman 2.1.8, Mailman/versions.py:489 : msg = Message.OutgoingMessage(text) There's no OutgoingMessage in Message any longer. Hit this while running list_lists while migrating sf.net lists. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-05-29 18:48 Message: Logged In: YES user_id=1123998 Patch included in subversion trunk. ---------------------------------------------------------------------- Comment By: Paul Sokolovsky (pfalcon) Date: 2006-05-29 16:36 Message: Logged In: YES user_id=11970 I had to comment that line altogether to proceed at that time, but after applying it, migrated few haundreds lists more, so it seems to be ok. Thank Mark! Hope it will get into 2.1.9. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-05-26 21:11 Message: Logged In: YES user_id=1123998 I'm not certain about this, but I think the attached patch will fix it. Please try it and report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495781&group_…

15 years, 7 months

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists

by SourceForge.net

Bugs item #1495781, was opened at 2006-05-26 15:14 Message generated for change (Comment added) made by pfalcon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495781&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Sokolovsky (pfalcon) Assigned to: Nobody/Anonymous (nobody) Summary: Non-existent class reference while upgrading lists Initial Comment: Mailman 2.1.8, Mailman/versions.py:489 : msg = Message.OutgoingMessage(text) There's no OutgoingMessage in Message any longer. Hit this while running list_lists while migrating sf.net lists. ---------------------------------------------------------------------- >Comment By: Paul Sokolovsky (pfalcon) Date: 2006-05-29 16:36 Message: Logged In: YES user_id=11970 I had to comment that line altogether to proceed at that time, but after applying it, migrated few haundreds lists more, so it seems to be ok. Thank Mark! Hope it will get into 2.1.9. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-05-26 21:11 Message: Logged In: YES user_id=1123998 I'm not certain about this, but I think the attached patch will fix it. Please try it and report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495781&group_…

15 years, 7 months

[ mailman-Feature Requests-1496741 ] Info header for admin-approved mails

by SourceForge.net

Feature Requests item #1496741, was opened at 2006-05-29 09:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1496741&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Josef Spillner (dr_maux) Assigned to: Nobody/Anonymous (nobody) Summary: Info header for admin-approved mails Initial Comment: One suggestion based on an issue occurring in current practice: When people not subscribed send an email to the list, the administrator will usually approve it. Some senders put something like "please CC: me" in there, but in most cases they don't and other list members don't know immediately about the subscription status. A configurable info text should be introduced, stating something like "Warning - this message comes from a non-subscribed sender, please reply with CC: activated". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1496741&group_…

15 years, 7 months

[ mailman-Patches-1483446 ] Daily mbox files for list mbox archives

by SourceForge.net

Patches item #1483446, was opened at 2006-05-07 14:14 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Daily mbox files for list mbox archives Initial Comment: The daily mbox patch changes the way Mailman does its archive-to-mbox archiving, if that is enabled. The standard Mailman system single .mbox file per list used for mbox archiving can, over time, become very unwieldy, presenting problems for disk space management. The mailman daily mbox patch modifies Mailman's behaviour so that a sparse series of daily mbox files is used for archiving rather than a single mbox file. Each archived message is normally appended to a daily mbox file for the UTC date when the message is first archived. For more information, download the patch and check out the file README.dailymbox or visit the URL http://www.openinfo.co.uk/mm/ patches/dailymbox/ Apply the patch from within the Mailman build directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-05-28 17:10 Message: Logged In: YES user_id=3142 Working very well on a production system. Nice addition to Mailman, makes file management and backups MUCH easier. Thanks!! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_…

15 years, 7 months

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists

by SourceForge.net

15 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders May 2006