Mailman 3 June 2005 - Mailman-coders

[ mailman-Bugs-1221451 ] privacy issue with subscribers on deferred status
by SourceForge.net June 15, 2005

June 15, 2005

Bugs item #1221451, was opened at 2005-06-15 15:00 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=1221451&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: wheeltrish (wheeltrish) Assigned to: Nobody/Anonymous (nobody) Summary: privacy issue with subscribers on deferred status Initial Comment: I own a mailman listserver which is hosted on Dreamhost and they are currently running ver. 2.1.5 of mailman. My list is set to require approval of membership requests, which sends the requesters into a "deferred" status in the "Tend to Pending Moderator Requests" area. I've discovered recently that individuals on "Deferred" status CAN in fact post to my list, and their postings are seen by all approved members. The individuals on "Deferred" status do not receive the postings themselves, however. Is this right? Shouldn't an individual who is marked "Deferred" not be able to post until being approved? This prevents me from ever stopping individuals who would send malicious posts to my list from allowing them to do so. My list is a high volume list and increasing the level of moderation would be cumbersome. Is there a way to ensure that members can't post to a list until they are approved, or is this problem an actual bug in the software? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1221451&group_…

1 0

[ mailman-Feature Requests-1220821 ] Option to move "cruft" ("boilerplate") to bottom of digest
by SourceForge.net June 14, 2005

June 14, 2005

Feature Requests item #1220821, was opened at 2005-06-14 16: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=1220821&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: Folsom EV (folsomev) Assigned to: Nobody/Anonymous (nobody) Summary: Option to move "cruft" ("boilerplate") to bottom of digest Initial Comment: Mailman now inserts instructions about changing the subject, etc., at the top of each digest e-mail sent. This is annoying to regular readers who must page down past it every time. Please add an option to move this "cruft" or "boilerplate" from the top of the digest e-mail to the bottom. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1220821&group_…

1 0

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers
by SourceForge.net June 14, 2005

June 14, 2005

Patches item #1220144, was opened at 2005-06-14 15:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&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: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: allow specifying another list in accept_these_nonmembers Initial Comment: Add the capability to logically include the addresses all of the members of another list in the same Mailman installation to accept_these_nonmembers. '@listname' checks the poster's address against the membership of listname. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_…

1 0

[ mailman-Feature Requests-1219887 ] switch to not send body of spam to owner
by SourceForge.net June 13, 2005

June 13, 2005

Feature Requests item #1219887, was opened at 2005-06-13 18:47 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=1219887&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: hiawatha (h-iawatha) Assigned to: Nobody/Anonymous (nobody) Summary: switch to not send body of spam to owner Initial Comment: Suppose there is a spam filter that has an action of hold. The system response is to send a mail to list-owner to tigger moderation. The offending mail is included in that response. It seems crazy that having received spam it is again posted out (thus increasing its distribution). Also, its the case that its likely to not arrive at a list owner because it may be stopped at the gate (because other filters will see it as spam also) or after arriving it may go straight in the spam box and be unseen. So, when a filter identifies spam and the action is to hold then the email sent to list-owner should either be just a notification to trigger action or there should be an extra switch such as hold-andnotify-only as an action. Another possible approach is to have list-owners able to configure what they receive in owner notifications. I personally prefer such a switch to be on actions but the other would be a more flexible scheme. andy ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1219887&group_…

1 0

[ mailman-Feature Requests-748370 ] Would like alternate actions for anti-spam filters
by SourceForge.net June 13, 2005

June 13, 2005

Feature Requests item #748370, was opened at 2003-06-03 11:46 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748370&group_i… 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: John DuBois (jhdiii) Assigned to: Nobody/Anonymous (nobody) Summary: Would like alternate actions for anti-spam filters Initial Comment: Currently, the only option for spam processing is to hold it for approval. Would like the options of reject & discard. It would also be nice if the spam filter could be configured to take place before sender filtering, so that a members-only list could be configured to hold posts by non-members, but only in the case of messages that get past the spam filtering. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-06-13 09:42 Message: Logged In: YES user_id=1123998 In recent Mailman versions, Privacy options...->Spam filters->header_filter_rules does all you ask. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748370&group_i…

1 0

[ mailman-Bugs-1219686 ] qmail-to-mailman.py virtual domains requires manual changes
by SourceForge.net June 13, 2005

June 13, 2005

Bugs item #1219686, was opened at 2005-06-13 07:59 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=1219686&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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthew England (mengland) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py virtual domains requires manual changes Initial Comment: I find that if I want to support qmail-to-mailman.py for multiple virtual domains I must add a: local = re.sub("^lists.newdomain.tld-","",local) line for every virtual domain. Could qmail-to-mailman.py be changed to support all virtual domains with the same general code without manual changes? -Matt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1219686&group_…

1 0

[ mailman-Bugs-1219449 ] Virtual domain link not working on pipermail "blank" list
by SourceForge.net June 13, 2005

June 13, 2005

Bugs item #1219449, was opened at 2005-06-12 21:59 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=1219449&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: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthew England (mengland) Assigned to: Nobody/Anonymous (nobody) Summary: Virtual domain link not working on pipermail "blank" list Initial Comment: The "more information about this list" link for 2.1.6rc4, when generated from pipermail link for a list that has yet to receive an email, points to the domain's default Mailman web host domain instead of the "virtual" domain that that is supporting said list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1219449&group_…

1 0

[ mailman-Patches-1160353 ] XHTML Compliant Web UI
by SourceForge.net June 12, 2005

June 12, 2005

Patches item #1160353, was opened at 2005-03-09 21:40 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1160353&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: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: XHTML Compliant Web UI Initial Comment: This is a patch that will make the Web UI XHTML 1.0 Strict compliant. Currently I only have the listinfo pages XHTML compliant, but as time goes by I'm going to make the entire UI compliant. This also allows some small amount of CSS formatting as well. Hopefully this will be of use to somebody. ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2005-06-12 09:33 Message: Logged In: YES user_id=449953 This latest patch makes the entire web UI XHTML 1.0 strict compliant including the archive. To use this patch, unzip it, switch to your source directory and issue the command patch -p1 <path/to/xhtml-2.1.6-0.1.patch ---------------------------------------------------------------------- Comment By: Bryan Carbonnell (carbonnb) Date: 2005-05-04 21:32 Message: Logged In: YES user_id=449953 Starting with the patch for MM 2.1.6rc3, the archives are now XHTML1.0 Strict compliant as well as the rest of the UI. To use this patch, unzip it, switch to your source directory and issue the command patch -p1 <path/to/xhtml-2.1.6rc3-0.1.patch ---------------------------------------------------------------------- Comment By: Bryan Carbonnell (carbonnb) Date: 2005-04-24 08:21 Message: Logged In: YES user_id=449953 The patch for MM 2.1.6-RC1 and above makes the entire WEB UI XHTML1 compliant, except for the archive pages, since they are HTM 3.2 compliant already. To use this patch, unzip it, switch to your source directory and issue the command patch -p1 <path/to/xhtml-2.1.6rc1-0.1.patch ---------------------------------------------------------------------- Comment By: Bryan Carbonnell (carbonnb) Date: 2005-03-09 21:47 Message: Logged In: YES user_id=449953 To use this patch, unzip it, switch to your source directory and issue the command patch -p1 <path/to/xhtml-2.1.6b4-0.1.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1160353&group_…

1 0

[ mailman-Bugs-1218827 ] please do not put the list footer in attachment if possible
by SourceForge.net June 11, 2005

June 11, 2005

Bugs item #1218827, was opened at 2005-06-11 18:27 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=1218827&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: Nagy Gábor Péter (bagoy) Assigned to: Nobody/Anonymous (nobody) Summary: please do not put the list footer in attachment if possible Initial Comment: I manage a list, for a long time it was running on mailman 2.0.11, now it was upgraded to 2.1.5 I was happy to see that I could set the list language to our language, but soon people started to complain because of the list footer. The old version has just added the footer at the bottom of every message, and we never had a problem with that. The new one tries to be smart, and from time to time it puts the footer in another mime part, with different encoding. While I realize that this is good in certain cases, most of the time it is useless. Our list footer contains ascii characters only. Those ascii characters could be simply added at the end of any latin1, latin2, or utf8 messages without any problem. Now it seems that even though I did not put any 8 bit characters in the footer, mailman always kept the footer latin2. (because of the list language). Now I have set the list language to english, so we have the same footer, but this time it is (correctly) us-ascii. Still, sometimes I receive emails, where the us-ascii footer was not added at the end of an email. Today for example there was a utf8 mail on the list, and the footer came as an attachment. Please try to find a way to recognize the possible combinations, and try to avoid creating a new attachment. It seems that most of the list members use some microsoft email clients, and all but one m$ clients don't show the footer inline. And all the clients (opera and netscape too, I was told) shows the attachment sign for all these messages, and people don't know which mails have "real" attachments, and which ones have only the footer attached. Cheers, Gabor ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1218827&group_…

1 0

[ mailman-Bugs-1216556 ] purge all pending administration requests
by SourceForge.net June 7, 2005

June 7, 2005

Bugs item #1216556, was opened at 2005-06-07 13:20 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1216556&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: Closed >Resolution: Out of Date Priority: 5 Submitted By: Ken Yee (kenyee) Assigned to: Nobody/Anonymous (nobody) Summary: purge all pending administration requests Initial Comment: Ever have a list get targetted by spammers? A list I moderate is on Mailman 2.1.5 and when you click on the "tend to pending moderator requests", it just sits there trying to load the page w/ a gazillion spammer attempts to send to the list (which only allows posting by approved members). We need a way to purge requests after N days or have a "catch up" button that purges everything... ken ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-06-07 13:40 Message: Logged In: YES user_id=12800 Mailman 2.1.6 can be set up to auto-discard pending messages after a certain period of time. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1216556&group_…

1 0