Mailman 3 May 2006 - Mailman-coders

[ 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