Mailman 3 January 2005 - Mailman-coders

[ mailman-Bugs-1100227 ] stops delivering messages
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1100227, was opened at 2005-01-11 15:45 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100227&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: steev hise (steev23) Assigned to: Nobody/Anonymous (nobody) Summary: stops delivering messages Initial Comment: Every once in a while, at random intervals (like after running fine for a few weeks or more), suddenly messages stop getting sent out to all mailing lists. They still go to the archives, they just don't get sent. can't find any clues in the logs. Is this a known bug? couldn't find one in tracker. Mailman Version: 2.1.5 python sys.version = 2.2.2 (#1, May 3 2003, 19:23:40) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] thanx, steev(a)detritus.net ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:52 Message: Logged In: YES user_id=67709 Too few information to answer. Have you checked both Mailman and MTA logs? Are you sure all the qrunnders are running (paticularly OutgoingRunner)? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100227&group_…

1 0

[ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1090439, was opened at 2004-12-23 16:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_… Category: None Group: 2.1 (stable) Status: Open Resolution: Later Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:42 Message: Logged In: YES user_id=67709 Sorry but fix will be after 2.1.6 release. In the meantime, the site owner can reset the password of this person from bin/withlist script. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_…

1 0

[ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1090439, was opened at 2004-12-23 16:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_… Category: None Group: 2.1 (stable) Status: Open >Resolution: Later Priority: 5 Submitted By: Bernhard Reiter (ber) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_…

1 0

[ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1085651, was opened at 2004-12-15 08:54 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_… 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: Brad Knowles (shub) Date: 2005-01-17 00: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 01: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 04: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-1090208 ] Password reminder bug (wrong "From" address, etc)
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1090208, was opened at 2004-12-23 05:13 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_… Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Brett Garrett (dolphyn) Assigned to: Nobody/Anonymous (nobody) Summary: Password reminder bug (wrong "From" address, etc) Initial Comment: Summary of bug: On a system with multiple domains and multiple lists, the password reminder sometimes contains information about a list to which the user is not subscribed, or in some cases, about a list that does not exist. Likewise, the "From" address of the password reminder can be incorrect. Details: The cron script "mailpasswds" contains the following code: siteowner = Utils.get_site_email(host, 'owner') sitereq = Utils.get_site_email(host, 'request') sitebounce = Utils.get_site_email (host, 'bounces') The problem is, this code is oblivious to the user's actual subscriptions. On a CPanel server, for example, it always defaults to mailman-owner@host, etc. This results in confusion among users. Since the "From" address of the reminder is mailman- owner@host and that address is also referenced in the mail, users send their questions to that address -- which may go to the server administrator, or to nobody at all, instead of the appropriate list owner. On my setup (a CPanel system) the following replacement code appears to correct most of the problem (in combination with an "import string" statement near the top of the script): siteowner = string.replace ( listaddr, '@', '- owner@' ) sitereq = string.replace ( listaddr, '@', '- request@' ) sitebounce = string.replace ( listaddr, '@', '- bounces@' ) I have not tested it thoroughly, but I think it corrects the siteowner and sitereq values. (For some reason the corrected sitebounce address does not have any effect. The reminder messages still have a return-path of mailman-bounces@servername instead of the appropriate listname-bounces@host. But, I don't think this matters as much as making sure the siteowner and sitereq addresses are correct.) Thank you! ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:27 Message: Logged In: YES user_id=67709 The feature that monthly password reminder is sent from 'mailman-owner' and not from the list owner is introduced from 2.1. This is because a member can subscribe to multiple lists and we cannnot decide which list should be picked for the sender. So was introduced the 'site list.' From NEWS: o There is now a `site list' which is a mailing list that must be created first, and from which all password reminders appear to come from. It is recommended that this list be called "mailman(a)your.site". ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-12-23 11:12 Message: Logged In: YES user_id=75166 CPanel sells a modified version of Mailman as part of its commercial hosting product. They have not made their modifications available to the Open Source developers and users of Mailman. Unless you can identify that this problem is present with unmodified, stable Mailman distribution source from sourceforge you will have to take this matter up with your ISP/or CPanel. This is not least because without the source code of the CPanel modifications it will be problematic diagnosing the cause of the problem you observe. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_…

1 0

[ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #1100788, was opened at 2005-01-12 10:51 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Later Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:16 Message: Logged In: YES user_id=67709 Closing because '/' was already fixed in 2.1.6. Others should be fixed in 3.0 (later). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-13 15:35 Message: Logged In: YES user_id=12800 Ideally, we'd allow any RFC 2822 legal address in, but I'd rather be secure than accept very uncommon corner cases. So where some characters cause Mailman problems, it's okay to leave them in _badchars. I think the number of people this will affect will be exceedingly small. ---------------------------------------------------------------------- Comment By: reeg (reeg) Date: 2005-01-13 08:53 Message: Logged In: YES user_id=1146038 Till now I had only a problem with the / because in one company the have adresses like "name/departmant/country@domain". Thanks for the change in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 02:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_…

1 0

[ mailman-Bugs-880073 ] list-id might violate RFC2919 and RFC2822
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Bugs item #880073, was opened at 2004-01-19 20:23 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_i… Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: list-id might violate RFC2919 and RFC2822 Initial Comment: Code in http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/Cook… (as shipped with mailman 2.1.4) will use formataddr for the List-Id: listid_h = formataddr((desc, listid)) This will violate the RFC2919, if not(desc), because the angle-brackets might be left out. 3. The List-Id Header Field The List-Id header MAY optionally include a description by including it as a "phrase" [DRUMS] before the angle-bracketed list identifier. The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF Unlike most headers in [RFC822], the List-Id header does not allow free insertion of whitespace and comments around tokens. [Go inside ~mailman/bin] python Python 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> import paths >>> from email.Utils import formataddr >>> formataddr(("A strange mailing list","strange.list.org")) 'A strange mailing list <strange.list.org>' >>> formataddr((None,"strange.list.org")) 'strange.list.org' >>> formataddr(("","strange.list.org")) 'strange.list.org' Solution: go back to old code and check http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_i… to limit the line length so you don't violate RFC2822 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:12 Message: Logged In: YES user_id=67709 This was already fixed in CVS/2.1.6b ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 17:23 Message: Logged In: YES user_id=113859 Added a fix for the problem: [ 933762 ] fix for #880073 list-id can violate RFC2919 https://sourceforge.net/tracker/index.php?func=detail&aid=933762&group_id=1… ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-19 20:25 Message: Logged In: YES user_id=113859 I'm raising the priority to 6 because many people get annoyed if the List-ID headers change. Mailman 2.1.3 did better in the RFC2919 regard, 2.1.4 breaks it in an attempt to fix other bugs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_i…

1 0

[ mailman-Patches-933762 ] fix for #880073 list-id can violate RFC2919
by SourceForge.net Jan. 17, 2005

Jan. 17, 2005

Patches item #933762, was opened at 2004-04-12 17:22 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_i… Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for #880073 list-id can violate RFC2919 Initial Comment: To make sure RFC2919 is not violated. "<" and ">" will be added if no list description exists. The maxlinelen=998 is a precaution to keep the may line length of RFC2822. Fixes [ 880073 ] list-id might violate RFC2919 and RFC2822 https://sourceforge.net/tracker/index.php?func=detail&aid=880073&group_id=1… ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:11 Message: Logged In: YES user_id=67709 This was already fixed in CVS/2.1.6b. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_i…

1 0

[ mailman-Bugs-1102176 ] Track invited emails
by SourceForge.net Jan. 14, 2005

Jan. 14, 2005

Bugs item #1102176, was opened at 2005-01-14 11: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=1102176&group_… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Dwayne Bailey (dwaynebailey) Assigned to: Nobody/Anonymous (nobody) Summary: Track invited emails Initial Comment: Currently there is no tracking of people who have been sent invite emails. This cause a problem in that you might invite people from a given list of emails to join the mailing list. Then from some other list or at some other time you might issue another invite. Receiving a number of invites from a list that you are not interested looks bad. It would be great if Mailman could track email addresses that have been invited and just like invites are not sent to people already subscribed they are not sent to people already invited. The use could of course have the option to ignore the "already invited" list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1102176&group_…

1 0

[ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address
by SourceForge.net Jan. 13, 2005

Jan. 13, 2005

Bugs item #1100788, was opened at 2005-01-12 05:51 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-13 10:35 Message: Logged In: YES user_id=12800 Ideally, we'd allow any RFC 2822 legal address in, but I'd rather be secure than accept very uncommon corner cases. So where some characters cause Mailman problems, it's okay to leave them in _badchars. I think the number of people this will affect will be exceedingly small. ---------------------------------------------------------------------- Comment By: reeg (reeg) Date: 2005-01-13 03:53 Message: Logged In: YES user_id=1146038 Till now I had only a problem with the / because in one company the have adresses like "name/departmant/country@domain". Thanks for the change in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 21:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_…

1 0