Mailman 3 October 2003 - Mailman-coders

[ mailman-Feature Requests-820728 ] limit postings by count
by SourceForge.net 09 Oct '03

09 Oct '03

Feature Requests item #820728, was opened at 2003-10-09 12:37 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=820728&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jim Jewett (jimjjewett) Assigned to: Nobody/Anonymous (nobody) Summary: limit postings by count Initial Comment: Place a limit on the number of postings/day before the list becomes temporarily moderated. (mlist.emergency gets set and EmergencyHold added to the processors.) Ideally, there would also be a separate per-poster limit before the individual became temporarily moderated. Reason: If one (or even several) individuals sets up a bad .vacation responder or succumbs to a virus, the list may soon be swamped with junk traffic. Better to shut it down than to swamp all readers. (Why yes, I am on a pair of lists sending out new digests every 5 minutes because of a .vacation loop problem. In this case, it would be enough to stop posts from this individual, but I realize that may not always be the case.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=820728&group_i…

1 0

[ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
by SourceForge.net 09 Oct '03

09 Oct '03

Patches item #820723, was opened at 2003-10-09 16:19 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=820723&group_i… Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i…

1 0

[ mailman-Patches-818601 ] "Announcement-only" list
by SourceForge.net 09 Oct '03

09 Oct '03

Patches item #818601, was opened at 2003-10-06 22:07 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_i… Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: "Announcement-only" list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-09 23:51 Message: Logged In: YES user_id=529503 rel.0.2. * Posttop handler now placed after Hold handler so that spam discarding and auto-response are capable. * Global pipelone processing are ommitted when: -------------------------------------- SpamDetect : [A] and [W] Approve : [W] ReplyBot : [W] Moderate : [A] Hold : - administrivia : [A] - too many recips : [A] - implicit dest. : [A] - suspicious headers : [A] and not [W] - message size : [A] and not [W] - news moderation : [A] and not [W] Posttop : (if [A], may be switched to owner pipeline.) AvoidDuplicates : [A] ------------------------------ [A]: list is announcement-only. [W]: message is posted from Web (by `poster'). * Additional modification to templates. * Some admin option categories are hidden. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_i…

1 0

[ mailman-Bugs-820322 ] Crash when global subcription change causes collision
by SourceForge.net 08 Oct '03

08 Oct '03

Bugs item #820322, was opened at 2003-10-08 15:47 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=820322&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rich Pasco (pasco) Assigned to: Nobody/Anonymous (nobody) Summary: Crash when global subcription change causes collision Initial Comment: I ran into this bug in MailMan version 2.1.2 today: If you change your e-mail address "globally" (on all lists to which you subscribe), and one of those lists (other than the one whose options page you're working from) already has a subscription under your new address (as well as your old address), then MailMan will crash (and display an exception traceback). For example, I was working from the web-team page http://domain.net/mailman/options/listname as I tried to change my address globally. This would affect about ten lists to which my old address subscribed, including a list called "Team" among others. But "Team" already had my new address among its subscribers, so it could not accept another one. Rather than giving a graceful error message when it discovered this, MailMan just crashed. I didn't capture the exception traceback, but it should be easy to reproduce. - Rich ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=820322&group_i…

1 0

[ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN
by SourceForge.net 08 Oct '03

08 Oct '03

Bugs item #803729, was opened at 2003-09-10 15:31 Message generated for change (Comment added) made by nemethe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin Németh (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- >Comment By: Ervin Németh (nemethe) Date: 2003-10-08 14:23 Message: Logged In: YES user_id=768522 It's quite unpleasant to recieve this mail daily. In addition there was a local mailing list to which no mail was delivered until digests to this list was turned off. Last day I have upgraded to mailman 2.1.3 and the last lines of the traceback changed: File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i…

1 0

[ mailman-Feature Requests-584468 ] listinfo: cache
by SourceForge.net 07 Oct '03

07 Oct '03

Feature Requests item #584468, was opened at 2002-07-21 14:32 Message generated for change (Comment added) made by pheinlein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo: cache Initial Comment: We`re running more than 700 lists on our mailinglist-server. Mailman needs between 20 and 40 seconds to generate the public listinfo page. Wouldn`t it be possible to generate a listinfo.cache including all these necessary informations to speed up the process? These listinfo.cache could be valid for some specific time, before it is removed and regenerated. Or this cache-file can be deleted if somenbody is changing his list configuration. Thanks... p.heinlein(a)jpberlin.de ---------------------------------------------------------------------- >Comment By: Peer Heinlein (pheinlein) Date: 2003-10-07 19:28 Message: Logged In: YES user_id=581680 I`d like to refresh my wish. With more then 1.000 lists on our server we really need a cached listinfo-overview. Building a listinfo-pages takes several seconds (as you can see on http://listi.jpberlin.de) and this only works if not too many different users try to access this page at the same time. I`d prefer the following model: Mailman generates a listinfo.pck or something like this, including all necessary information. If listinfo.pck doesn`t exist, Mailman generates a new one. This listinfo.pck has a lifetime after which it is deleted (e.g. 5 minutes). After creating or deleting a new list the listinfo.pck is deleted. Possible: After changing the configuration of a list Mailman deletes listinfo.pck which means, that the general lifetime cat be set up to 10/15/20 minutes, because everytime something SHOULD have changed, Mailman SHOULD have deleted listinfo.pck... :-) Isn`t that possible? That shouldn`t be too much work... Peer ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2002-08-10 09:38 Message: Logged In: YES user_id=581680 Having more then 700 lists on our server we now have problems generating the listinfo/admin overview-page, because the http-timeouts are faster then mailman :-) Is there something planned to solve the problem? Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=584468&group_i…

1 0

[ mailman-Bugs-818752 ] Changing option via email not work
by SourceForge.net 06 Oct '03

06 Oct '03

Bugs item #818752, was opened at 2003-10-07 02:51 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=818752&group_i… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Yuji Kitano (ykitano) Assigned to: Nobody/Anonymous (nobody) Summary: Changing option via email not work Initial Comment: Some of user options are not affected when you change them via an email. eg. When you send a command email to xxxx-request, system returns an email stating that option is set, but that is not set actually. set authenticate password set delivery off then to see if that option is set properly set authenticate password set show You can change options of ack, myposts, hide, etc via an email but cannot change options of delivery and digest. I can reproduce this issue on Mailman 2.1.2 and 2.1.3 on Redhat Linux. I even tried on Mailman-Users list and got the same result. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818752&group_i…

1 0

[ mailman-Bugs-818612 ] adding mime type for shortcut icon
by SourceForge.net 06 Oct '03

06 Oct '03

Bugs item #818612, was opened at 2003-10-06 15:30 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=818612&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: adding mime type for shortcut icon Initial Comment: Peter Bieringer reported that many browsers don't understand the <link REL="SHORTCUT ICON"> tag if we don't include the appropriate mime type: image/x-icon. It's possible this is simply a misconfiguration in the web server (which is supposed to serve the right mime type in the 1st place) but anyway forcing the type is cheap enough. I'm uploading the one-liner fix. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=818612&group_i…

1 0

[ mailman-Patches-818601 ] "Announcement-only" list
by SourceForge.net 06 Oct '03

06 Oct '03

Patches item #818601, was opened at 2003-10-06 22:07 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=818601&group_i… Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: "Announcement-only" list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_i…

1 0

[ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement!
by SourceForge.net 03 Oct '03

03 Oct '03

Bugs item #815297, was opened at 2003-09-30 17:42 Message generated for change (Comment added) made by mmutz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_i… Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- Comment By: Marc Mutz (mmutz) Date: 2003-10-03 15:54 Message: Logged In: YES user_id=82377 This is not limited to message/rfc822 at all: As a specific example, create a message with an attachment and add the header Content-Disposition: attachment; filename="more-than-70-chars. txt" (all in a single line), then send it through a mailman-managed ml. Result: mailman "fixes" the message to look like Content-Disposition: attachment; \tfilename="more-than-70-chars.txt" It even does that inside a multipart/signed part, and this is where it breaks the signature verification. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-09-30 17:46 Message: Logged In: YES user_id=113859 Here is the email signed by myself and broken after delivery through mailman. Check the "To:" header line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_i…

1 0