Mailman 3 December 2002 - Mailman-Developers

[ mailman-Bugs-540978 ] List-* header multiline split bug
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #540978, was opened at 2002-04-08 08:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: Markus Mandalka (mandalka) Assigned to: Nobody/Anonymous (nobody) Summary: List-* header multiline split bug Initial Comment: I have a list antiatomforum(a)lists.kommunikationssystem.de and others with long names. It seems that mailman can not handle with such long names, because in the subscribe-mail (which you have to answer to be in the list) the first columns are some things from the header (unsubscribe: xxx(a)lists.xxx and so on). Whith names like atest(a)lists.kommunikationssystem.de it works. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 17:38 Message: Logged In: YES user_id=12800 Changing the summary ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-15 00:37 Message: Logged In: NO I just installed mailman and can confirm this bug as well. When the list address + hostname is too long (in my case the listname was north-texas-stovebolters- club(a)stovebolt.stovebolt.com -- 52 characters total) the headers overflow into the body of the message. The "break point" was at the List Subscribe line: ******************* This is header: List-Subscribe: <http://stovebolt.stovebolt.com/mailman/listinfo/north- texas-stovebolters-club>, (total of 94 characters before the split) ******************* This is body <mailto:north-texas-stovebolters-club- request(a)stovebolt.stovebolt.com?subject=subscribe> List-Unsubscribe: <http://stovebolt.stovebolt.com/mailman/listinfo/north- texas-stovebolters-club>, <mailto:north-texas-stovebolters-club- request(a)stovebolt.stovebolt.com?subject=unsubscribe> List-Archive: <http://stovebolt.stovebolt.com/pipermail/north-texas- stovebolters-club> List-Help: <mailto:north-texas-stovebolters-club- request(a)stovebolt.stovebolt.com?subject=help> Sender: north-texas-stovebolters-club- bounces(a)stovebolt.stovebolt.com Errors-To: north-texas-stovebolters-club- bounces(a)stovebolt.stovebolt.com ************************ This is the initial text of the message that was posted. I'm sure that I'll be there. :-) **************************** It looks like there's a line break or line limit that's causing the problem. Perhaps it's line 33: MAXLINELEN = 78 The first line that breaks (in my case) is a line that has 94 characters in the first part, none of which can be separated (no spaces or line breaks, just continuous text.) The very next line drops to the body. I believe giuans is correct that the problem is in the wrap section of the code, because the break occurs immediately after a comma, which, if I'm understanding the code correctly, is inserted by the program after an overlength line occurs, to split the line at 78 (or as close to that as it can get.) I think the correct fix would be to add the "h" portion subsequent to the split so that each line in the header would have the required semi-colon to indicate that it's header. If the MTA sees a line with no semicolon, it's going to think that it's body text, not header. ***************** Present code: if len(h) + 2 + len(v) > 78: v = CONTINUATION.join(v.split(', ')) msg[h] = v ****************** Possible fix if len(h) + 2 + len(v) > 78: v=CONTINUATION.join(h + v.split(',')) msg[h] = v or something like that. (I haven't worked with php, so I'm not familiar with its functions and syntax.) The idea is to split a line like this: Line exceeds 78 characters? h+v, h+ rest of v HTH. ---------------------------------------------------------------------- Comment By: Jean Millerat (drsigmund) Date: 2002-07-04 04:13 Message: Logged In: YES user_id=70686 I have reached the same bug with mailing list adresses such as <11 characters>@<30 characters> whereas <8 characters>@<30 characters> works properly. The effect of this bug is that the headers of the subcription annoucement or any further email from the list are "mangled" as was said on [mailman-developers]. As an example when one of the List-* header line is too long, it is broken in two parts (and the second part is indented). Since then, Outlook (and I suppose other email clients) think this second part of the broken header line is the beginning of the body of the message. Therefore the remaining headers are sent as part of the body of the message ! I think this bug does not only occur with too long email adresses but may occur with too long header lines whichever line it is (even with the Subject line especially when this subject line is very long because of quoted-printable characters). See [mailman-developers] for the description of maybe the same bug, in mails dealing with headers being "mangled". My current workarounds : - using short mailing list names. - and not sending quoted-printable characters within subject lines. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-02 10:27 Message: Logged In: YES user_id=531451 I've found it. A fast fix for is to comment lines 149-150 in Mailman/Handlers:/CookHeaders.py: --- CookHeaders.py 2002-05-02 14:51:36.000000000 +0200 +++ CookHeaders.py.new 2002-05-02 16:12:09.000000000 +0200 @@ -146,8 +146,8 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded, but is at least text-MUA friendly. The # adding of 2 is for the colon-space separator. - if len(h) + 2 + len(v) > 78: - v = CONTINUATION.join(v.split(', ')) +# if len(h) + 2 + len(v) > 78: +# v = CONTINUATION.join(v.split(', ')) msg[h] = v # Always delete List-Archive header, but only add it back if the list is # actually archiving Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18, Postfix 1.1.7. I know there should be a better way, but I'm not a Python programmer at all. :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-11 18:03 Message: Logged In: YES user_id=12800 I've confirmed this bug, but don't have a fix for it right now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_i…

1 0

[ mailman-Bugs-644773 ] "description" doesn't get encoded
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #644773, was opened at 2002-11-27 10:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_i… Category: None Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_i…

1 0

[ mailman-Bugs-621597 ] list creation ignores DEFAULT_EMAIL_HOST
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #621597, was opened at 2002-10-10 18:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621597&group_i… Category: None Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: list creation ignores DEFAULT_EMAIL_HOST Initial Comment: If I set DEFAULT_EMAIL_HOST in mm_cfg.py, its value is ignored when creating a new list. It's pretty easy to see why: MailList.InitVars uses DEFAULT_HOST_NAME. But the two are only equal as long as mm_cfg.py is not used. If DEFAULT_HOST_NAME and DEFAULT_EMAIL_HOST are really supposed to be the same, perhaps DEFAULT_HOST_NAME should not be set in Defaults.py -- rather, any code that looks at DEFAULT_EMAIL_HOST should check to see if DEFAULT_HOST_NAME happens to be defined in mm_cfg, and use it if so. Or something like that. I'm happy to supply a patch if someone agrees that this is a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621597&group_i…

1 0

[ mailman-Bugs-637410 ] autorespond_requests "w/discard" ignored
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #637410, was opened at 2002-11-12 16:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: autorespond_requests "w/discard" ignored Initial Comment: Gui/Autoresponse.py makes a distinction between autorespond_requests == 1 or == 2, but that's implemented in the MailCommandHandler.py module, which is unreferenced in b3 and gone in b4. CommandRunner._dispose could check for this after it calls Replybot.process(), I think. Or if the feature was intentionally left out, it could be left out of the web interface too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637410&group_i…

1 0

[ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Patches item #646989, was opened at 2002-12-02 11:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Rop Gonggrijp (rop) Assigned to: Nobody/Anonymous (nobody) Summary: NAH6 Secure List patch: GPG plugin Initial Comment: "NAH6 Secure List" is a patch for Mailman 2.1b5 that adds GPG functionality. It is built around a key-scheme that allows an admin to create an encrypted list for which even the server operator doesn't have access to the messages. Only the public key for the list is given to the server, so it can perform 'emergency encryption' in case someone forgets, and all users get the public and private key for the list. We think we've done a decent job of describing the new functionality from server-operator, list-admin and list- member points of view. There's also a technical document for those familiar with the Mailman code. Please have a look at: http://www.nah6.com/products/secure-list/ and follow the links from there We feel more people need this, and we'd really like it to be part of the Mailman distribution at some point... Kind Regards, Rop Gonggrijp Joshua Eichen Please forgive mangling the Mailman logo on the site: if y'all don't like it or think it's over the top we'll use something else.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_i…

1 0

[ mailman-Patches-643556 ] Update to portuguese listinfo template
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Patches item #643556, was opened at 2002-11-25 08:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643556&group_i… Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Update to portuguese listinfo template Initial Comment: This is the second half of the quick fixups I've done to the pt_BR translation. I've only hacked the listinfo template so far because it's the only thing that's been really bothering me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643556&group_i…

1 0

[ mailman-Patches-643547 ] Update portuguese translation
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Patches item #643547, was opened at 2002-11-25 08:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643547&group_i… Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Update portuguese translation Initial Comment: I've done a quick lookover the portuguese translation and I have a number of small fixes and unfuzzys to be added. This fixes mostly the listinfo page, which is the page my users actually hit the most, and there are some other assorted fixes (typos non-existant words etc). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643547&group_i…

1 0

[ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #635542, was opened at 2002-11-08 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_i… Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught MMNoSuchUserError Initial Comment: I found an unsubscribe confirmation message in the shunt directory. The error log suggests that someone used both the web and the reply to unsubscribe, but when the email confirmation arrived, he was already gone and qrunner faulted. I'm running a CVS build about a week old. Here's the traceback: Nov 08 05:29:33 2002 (23820) Uncaught runner exception: Nov 08 05:29:33 2002 (23820) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 199, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 117, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1107, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/mailman/Mailman/MailList.py", line 936, in ApprovedDeleteMember raise Errors.MMNoSuchUserError MMNoSuchUserError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635542&group_i…

1 0

[ mailman-Bugs-644294 ] Uncaught runner exception
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #644294, was opened at 2002-11-26 14:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i… Category: Pipermail Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- Comment By: Terry Grace (tgrace) Date: 2002-11-26 20:40 Message: Logged In: YES user_id=87771 Archives broken too. After restarting the deamons, only the first article posted gets archived. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i…

1 0

[ mailman-Bugs-637494 ] typo in README.SENDMAIL (CVS 2.4)
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #637494, was opened at 2002-11-12 19:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_i… Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: typo in README.SENDMAIL (CVS 2.4) Initial Comment: The README.SENDMAIL section on INTEGRATION has a typo: ...such that Sendmail will automatically recognize and delivery I presume it must be without the "y" in "delivery". ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 08:58 Message: Logged In: YES user_id=12800 Fixed thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=637494&group_i…

1 0