Mailman 3 May 2006 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Bugs-1498290 ] Footer sometimes appended to last line of message
by SourceForge.net May 31, 2006

May 31, 2006

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_…

1 0

[ mailman-Bugs-1498213 ] bad email sanitisation issue
by SourceForge.net May 31, 2006

May 31, 2006

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_…

1 0

[ mailman-Bugs-1498213 ] bad email sanitisation issue
by SourceForge.net May 31, 2006

May 31, 2006

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_…

1 0

[ mailman-Bugs-1497366 ] Differentiate between subscribers/others for held messages
by SourceForge.net May 30, 2006

May 30, 2006

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_…

1 0

[ mailman-Bugs-1484722 ] Topic regexes are never applied
by SourceForge.net May 30, 2006

May 30, 2006

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_…

1 0

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists
by SourceForge.net May 30, 2006

May 30, 2006

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_…

1 0

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists
by SourceForge.net May 29, 2006

May 29, 2006

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_…

1 0

[ mailman-Feature Requests-1496741 ] Info header for admin-approved mails
by SourceForge.net May 29, 2006

May 29, 2006

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_…

1 0

[ mailman-Patches-1483446 ] Daily mbox files for list mbox archives
by SourceForge.net May 28, 2006

May 28, 2006

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_…

1 0

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists
by SourceForge.net May 27, 2006

May 27, 2006

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: 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: 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_…

1 0

[ mailman-Feature Requests-1441723 ] privacy hole in password reminder
by SourceForge.net May 27, 2006

May 27, 2006

Feature Requests item #1441723, was opened at 2006-03-02 05:48 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1441723&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: dmvianna (dmvianna) Assigned to: Nobody/Anonymous (nobody) Summary: privacy hole in password reminder Initial Comment: Mailman sends me password reminders in plain text. I can disable this feature, but other users can manually make it send a reminder just as if I had forgot the password, with no other question being asked. If smart enough to intercept that message, the attacker could: 1) Get my password; 2) get my IP in the mail header. Possible solutions: 1) Some sites and programs use a "secret question" which right answer would give the user the chance to get a password reminder. 2) The password could be prompted in a secure html page. I find this safer, as compared to plain text mails. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-05-26 18:48 Message: Logged In: YES user_id=1123998 I'm not sure what IP you think would be in the email header that isn't already publicly available via a DNS query of your email domain, or why you think even that IP would be in the header of an intercepted mail. Also, when you say "If smart enough to intercept that message", are you aware of an attack tht would enable this, or are you just concerned that it could happen. Finally, password reminders will go away in Mailman 2.2. We'll try to keep your concern in mind as we work on their replacement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1441723&group_…

1 0

[ mailman-Bugs-1495781 ] Non-existent class reference while upgrading lists
by SourceForge.net May 26, 2006

May 26, 2006

Bugs item #1495781, was opened at 2006-05-26 15:14 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=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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495781&group_…

1 0

[ mailman-Feature Requests-1495305 ] re-confirm memberships
by SourceForge.net May 26, 2006

May 26, 2006

Feature Requests item #1495305, was opened at 2006-05-25 21:00 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=1495305&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: Daevid Vincent (daevid) Assigned to: Nobody/Anonymous (nobody) Summary: re-confirm memberships Initial Comment: I have a suspicion that some of my lists' mails are not getting to their destinations. This could be that some people used their job email and no longer work there, could be that they are on AOL or hotmail (which seem to just silently discard), or could be just people that joined up and now 'junk mail or filter' the list because they're either to stupid or lazy to properly unsubscribe. Bottom line is that I'm paying per emails sent (via my quota on DynDNS) and I want to unsubscribe these dead members. It would be great if I could push a button in the web GUI (or run some command on the CLI) and mailman would reset every members status to 'unconfirmed' (or whatever it is), mail them a link to click (with some crazy code in it like when you join a list), and then mark the responders as 'confirmed'. Then after some period of time, say a week or so, I could then go into the GUI, click some link and see a list of all 'unconfirmed' people with the option to unsubscribe them all (without sending an email obviously, since the address is bogus). Extra points if I can schedule this task to occur every month, every six months, once a year, etc... (probably some 'day' interval would be sufficient here). ÃÃ5ÃÃ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1495305&group_…

1 0

[ mailman-Bugs-1484722 ] Topic regexes are never applied
by SourceForge.net May 26, 2006

May 26, 2006

Bugs item #1484722, was opened at 05/09/06 07:28 Message generated for change (Comment added) made by sf-robot 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: None 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: SourceForge Robot (sf-robot) Date: 05/25/06 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: 05/10/06 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: 05/09/06 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_…

1 0

[ mailman-Bugs-1495122 ] Mailman strips format=flowed from Content-Type header
by SourceForge.net May 25, 2006

May 25, 2006

Bugs item #1495122, was opened at 2006-05-25 21: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=1495122&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: Bart Jacobs (radiantskies) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman strips format=flowed from Content-Type header Initial Comment: It seems that Mailman strips the format=flowed argument from the Content-Type: text/plain header when delivering incoming e-mails to subscribers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_…

1 0

[ mailman-Feature Requests-1486877 ] administrator vs. moderator settings
by SourceForge.net May 20, 2006

May 20, 2006

Feature Requests item #1486877, was opened at 2006-05-11 21:01 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1486877&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: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: administrator vs. moderator settings Initial Comment: Werner Lemberg recently sent a message to mailman-users about separately defining notifications for administrators vs. moderators. While wholeheartedly supporting Werner's general proposal (I currently filter hundreds of useless notifications every day), I'd like to suggest a slightly different variation -- perhaps it's easier to implement too: Have an interface which allows specifying, for any given email address, 1) whether it is a moderator or an administrator 2) whether it should get the daily mails 3) whether it should get the immediate notifications For an interface, I can imagine a screen similar to the current membership management screen (though with many fewer columns). I think this is preferable because on some lists I list myself as a moderator, on others as an administrator, for various reasons. But I never want to get the immediate notifications, regardless of whether I am an admin or a moderator. It occurs to me that the split into "admin" and "moderator" is perhaps misleading in the first place, since the main difference (AFAIK) is whether the given address is listed on the publicly viewable HTML pages. Maybe they should just all be "administrative email address", and whether it is listed or not on the public page is a fourth specification. Other related options I can think of could perhaps be specified the same way, on a per-administrative-email basis: whether it gets (un)subscribes, and whether it gets disabled/deleted bounce notifications. (There is no use in sending anything but the immediate notifications to our robot helper.) Whether it's possible to specify defaults for all these things is not important to me. Having hardwired defaults would be fine. Hope this makes some kind of sense and can be considered for a future release ... Thanks, karl ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2006-05-20 21:07 Message: Logged In: YES user_id=33248 I'm not sure admins/moderators should be shoehorned into the regular subscriber list, tempting though it is. They have additional settings (the various notifications) which are not relevant to regular subscribers, and conversely most subscriber settings are not relevant to owners. Finally, when owners are also subscribers, they'd need to be able to control everything separately. Overall, I see a lot more potential for confusion than simplification. But since no developers have responded, I guess it's all pretty much a moot point anyway. Karl ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-05-11 22:18 Message: Logged In: YES user_id=3142 I agree that changes to the Owner/Moderator interfaces need some thought. My thought is this: Just eliminate the concept of separate interface settings for defining list Owners and Moderators and replace it by adding Mod and Owner fields to normal users just like NoMail. This way Owners could easily rotate Moderators, and both could easily change their email delivery options from NoMail to Digest to Normal. Tuff luck if all the Owners set NoMail at the same time, however some might want that capability. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1486877&group_…

1 0

[ mailman-Feature Requests-1489244 ] Add forward option for moderated member post to list
by SourceForge.net May 16, 2006

May 16, 2006

Feature Requests item #1489244, was opened at 2006-05-15 21:41 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=1489244&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: isisdesign (isisdesign) Assigned to: Nobody/Anonymous (nobody) Summary: Add forward option for moderated member post to list Initial Comment: On the Privacy Options: Sender filters page, the second item is: Action to take when a moderated member posts to the list. The three options are Hold, Reject and Discard. What is needed for posts from moderated members is the ability to forward the email to a specified email address. This could be added either as a forth radio button for forward with the additional field for the address to forward to -- or -- as a separate action with just a field for an address to forward to if one is supplied. The latter way is more powerfull so i would suggest that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1489244&group_…

1 0

[ mailman-Feature Requests-1488954 ] approval password linked to sender
by SourceForge.net May 15, 2006

May 15, 2006

Feature Requests item #1488954, was opened at 2006-05-15 16:44 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=1488954&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: David Lee (davidlee) Assigned to: Nobody/Anonymous (nobody) Summary: approval password linked to sender Initial Comment: The existing "Approved:" mechanism needs a password shared in common across multiple people (which feels poor and doesn't scale well) and across multiple lists (again, scaling problems). Is there a facility, or plans for such, for each permitted sender to have (optionally) their own password, useable across many lists? (For more info see email to mailman-users 15/May/2006. Let me know if you want me to copy-and-paste here.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1488954&group_…

1 0

[ mailman-Bugs-1240368 ] header problems
by SourceForge.net May 14, 2006

May 14, 2006

Bugs item #1240368, was opened at 2005-07-18 09:06 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1240368&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: Sepphoria (sepphoria) Assigned to: Nobody/Anonymous (nobody) Summary: header problems Initial Comment: If a header and a footer are added to mail sent to regular list members under Non-Digest options, using Outlook as the email client for sending email, Outlook delivers the email with the header as a .txt attachment, and the body of the email as an .html file attachment. The footer is normal. Using a different email client (Netscape) for sending email, Outlook delivers the email with the header and footer in a .txt attachment. The text of the email is normal (in the body of the email). This is the case for version 2.1.5. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-05-14 07:13 Message: Logged In: YES user_id=1123998 See http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.039.htp ---------------------------------------------------------------------- Comment By: Girla (girla) Date: 2006-05-14 07:07 Message: Logged In: YES user_id=1210276 Have the same problem, in case when mail has file(s) attachment(s): then header going as normal mail body, then in msg attachment mail body, then file(s) attachment, and footer in msg attachment. Using The Bat!, Mozilla Thunderbird, variuos webmails. Version MailMan 2.1.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1240368&group_…

1 0

[ mailman-Bugs-1240368 ] header problems
by SourceForge.net May 14, 2006

May 14, 2006

Bugs item #1240368, was opened at 2005-07-18 19:06 Message generated for change (Comment added) made by girla You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1240368&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: Sepphoria (sepphoria) Assigned to: Nobody/Anonymous (nobody) Summary: header problems Initial Comment: If a header and a footer are added to mail sent to regular list members under Non-Digest options, using Outlook as the email client for sending email, Outlook delivers the email with the header as a .txt attachment, and the body of the email as an .html file attachment. The footer is normal. Using a different email client (Netscape) for sending email, Outlook delivers the email with the header and footer in a .txt attachment. The text of the email is normal (in the body of the email). This is the case for version 2.1.5. ---------------------------------------------------------------------- Comment By: Girla (girla) Date: 2006-05-14 17:07 Message: Logged In: YES user_id=1210276 Have the same problem, in case when mail has file(s) attachment(s): then header going as normal mail body, then in msg attachment mail body, then file(s) attachment, and footer in msg attachment. Using The Bat!, Mozilla Thunderbird, variuos webmails. Version MailMan 2.1.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1240368&group_…

1 0

[ mailman-Feature Requests-1486877 ] administrator vs. moderator settings
by SourceForge.net May 11, 2006

May 11, 2006

Feature Requests item #1486877, was opened at 2006-05-11 17:01 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1486877&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: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: administrator vs. moderator settings Initial Comment: Werner Lemberg recently sent a message to mailman-users about separately defining notifications for administrators vs. moderators. While wholeheartedly supporting Werner's general proposal (I currently filter hundreds of useless notifications every day), I'd like to suggest a slightly different variation -- perhaps it's easier to implement too: Have an interface which allows specifying, for any given email address, 1) whether it is a moderator or an administrator 2) whether it should get the daily mails 3) whether it should get the immediate notifications For an interface, I can imagine a screen similar to the current membership management screen (though with many fewer columns). I think this is preferable because on some lists I list myself as a moderator, on others as an administrator, for various reasons. But I never want to get the immediate notifications, regardless of whether I am an admin or a moderator. It occurs to me that the split into "admin" and "moderator" is perhaps misleading in the first place, since the main difference (AFAIK) is whether the given address is listed on the publicly viewable HTML pages. Maybe they should just all be "administrative email address", and whether it is listed or not on the public page is a fourth specification. Other related options I can think of could perhaps be specified the same way, on a per-administrative-email basis: whether it gets (un)subscribes, and whether it gets disabled/deleted bounce notifications. (There is no use in sending anything but the immediate notifications to our robot helper.) Whether it's possible to specify defaults for all these things is not important to me. Having hardwired defaults would be fine. Hope this makes some kind of sense and can be considered for a future release ... Thanks, karl ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-05-11 18:18 Message: Logged In: YES user_id=3142 I agree that changes to the Owner/Moderator interfaces need some thought. My thought is this: Just eliminate the concept of separate interface settings for defining list Owners and Moderators and replace it by adding Mod and Owner fields to normal users just like NoMail. This way Owners could easily rotate Moderators, and both could easily change their email delivery options from NoMail to Digest to Normal. Tuff luck if all the Owners set NoMail at the same time, however some might want that capability. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1486877&group_…

1 0

[ mailman-Feature Requests-1486877 ] administrator vs. moderator settings
by SourceForge.net May 11, 2006

May 11, 2006

Feature Requests item #1486877, was opened at 2006-05-11 21:01 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=1486877&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: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: administrator vs. moderator settings Initial Comment: Werner Lemberg recently sent a message to mailman-users about separately defining notifications for administrators vs. moderators. While wholeheartedly supporting Werner's general proposal (I currently filter hundreds of useless notifications every day), I'd like to suggest a slightly different variation -- perhaps it's easier to implement too: Have an interface which allows specifying, for any given email address, 1) whether it is a moderator or an administrator 2) whether it should get the daily mails 3) whether it should get the immediate notifications For an interface, I can imagine a screen similar to the current membership management screen (though with many fewer columns). I think this is preferable because on some lists I list myself as a moderator, on others as an administrator, for various reasons. But I never want to get the immediate notifications, regardless of whether I am an admin or a moderator. It occurs to me that the split into "admin" and "moderator" is perhaps misleading in the first place, since the main difference (AFAIK) is whether the given address is listed on the publicly viewable HTML pages. Maybe they should just all be "administrative email address", and whether it is listed or not on the public page is a fourth specification. Other related options I can think of could perhaps be specified the same way, on a per-administrative-email basis: whether it gets (un)subscribes, and whether it gets disabled/deleted bounce notifications. (There is no use in sending anything but the immediate notifications to our robot helper.) Whether it's possible to specify defaults for all these things is not important to me. Having hardwired defaults would be fine. Hope this makes some kind of sense and can be considered for a future release ... Thanks, karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1486877&group_…

1 0

[ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments
by SourceForge.net May 11, 2006

May 11, 2006

Bugs item #1085651, was opened at 2004-12-15 09:54 Message generated for change (Comment added) made by proffe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&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: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- Comment By: Magnus Holmgren (proffe) Date: 2006-05-11 12:02 Message: Logged In: YES user_id=669310 This is a duplicate of bug #815297. ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-03-20 14:51 Message: Logged In: YES user_id=42389 That function does indeed not conserve whitespace. E-mail doesn't say whitespace in headers (or even the message) must be preserved, so strictly speaking it's not a bug. However, it is a missing feature, and I think python is the place to implement it, not mailman. The point is that signed e-mails with attachments are sent as two parts: One which is a complete e-mail by itself, and one which holds the signature for that e-mail. This is because in attachments whitespace must be preserved (as opposed to the situation in the message itself). It would be very convenient if such e-mail can be handled by python programs without rewriting the things which work fine for non-signed e-mails. If the attachment is really changed, of course the signature will be broken. However, if it is not, it should not be hard to write out the same message (with whitespace preserved) as was read in. If this is not possible, it is quite hard to do it in the program, as python doesn't seem to support loading a part of an e-mail which has headers of its own as a binary attachment (without touching whitespace, in particular). ---------------------------------------------------------------------- Comment By: Jonas Berlin (xkr47) Date: 2005-03-19 13:21 Message: Logged In: YES user_id=66259 from python's Message.py: def _get_params_preserve(self, failobj, header): # Like get_params() but preserves the quoting of values. BAW: # should this be part of the public interface? According to my analysis of the comment, the function in question does _not_ guarantee to preserve the header as-is, it only preserves _quoting_. Thus, I don't think we can call this a bug in python. If there's more official documentation elsewhere that states that it should preserve everything as-is, then ignore this comment altogether :). I didn't have time to grasp how mailman actually uses that Message class, but I think mailman should be changed to use functions that don't alter the message, and/or re-implement that work according to the requirements of mailman (or, users of mailman :). Anyway, an alternative could be to continue to use the Message.py functions to parse the values while analyzing the contents of the message, and then copypaste the original headers as-is after checking. - xkr47 ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-29 18:08 Message: Logged In: YES user_id=15365 Dear Bas, Thanks a lot for identifying the source of this bug and flagging an upstream bug on Python. Etienne ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-01-24 12:35 Message: Logged In: YES user_id=42389 I checked the source, and this appears to be a bug in Python. It can read and write e-mails, including headers, and they are interpreted. However, it doesn't preserve their whitespace, which is of course fatal for pgp signatures. The bug is filed for python here: http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=54… ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-18 18:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-17 01:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-08 02:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg <toniw(a)iki.fi> ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-30 05:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…

1 0

[ mailman-Bugs-1484722 ] Topic regexes are never applied
by SourceForge.net May 11, 2006

May 11, 2006

Bugs item #1484722, was opened at 2006-05-09 07:28 Message generated for change (Settings changed) 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: Pending Resolution: None 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-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_…

1 0