Mailman 3 November 2002 - Mailman-Developers

[ mailman-Bugs-419992 ] bin/arch messed up existing web archive
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #419992, was opened at 2001-04-29 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i… Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch messed up existing web archive Initial Comment: When running arch and webpages still exists, the web archive is messed up. This is quite confusing. A warning should be printed if arch is started on a list where there is already stuff in the web archive. Optionally it could delete the files is is regenerating first. Details: arch seems to attach each mail again to the .txt monthly archive files here and then build the web archive out of this. No wonder that the mail I deleted is still in after the process.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i…

1 0

[ mailman-Bugs-635542 ] Uncaught MMNoSuchUserError
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

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: Open Resolution: None >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-637410 ] autorespond_requests "w/discard" ignored
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

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: Open Resolution: None >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-Bugs-616674 ] bin/arch not processing mbox import corr
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #616674, was opened at 2002-09-30 13:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: fuzzy (fuzzynco) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch not processing mbox import corr Initial Comment: I needed to import an archive from yahoo!groups. a list formerly on Y!G is now on my server with MM2.1b3. After creating the mbox file with a perl script na dtesting it with pine (to make sure all the email is acuallu there), I tried to import it using arch. there are a few thousand emails in the file, but arch only finds 2? I posted to the mm users mailing list and got a reply from Larry Weeks, said to send him a copy of the file, and he tested it with bin/arch from 2.0.6 and it works as expected. since the mbox file is readable by pine, shouldn't arch handle it correctly? email me if i can provide any thing that would help diagnose the problem. thanks... fuzzy(a)pooh.asarian.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_i…

1 0

[ mailman-Bugs-620033 ] gate_news should catch lost connection
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #620033, was opened at 2002-10-07 22:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_i… Category: nntp/news Group: 2.1 beta Status: Open Resolution: Accepted >Priority: 7 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: gate_news should catch lost connection Initial Comment: Sep 20 10:51:35 2002 gate_news(9301): Traceback (most recent call last): Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 270, in ? Sep 20 10:51:35 2002 gate_news(9301): main() Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 250, in main Sep 20 10:51:35 2002 gate_news(9301): process_lists(lock) Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 194, in process_lists Sep 20 10:51:35 2002 gate_news(9301): conn, first, last = open_newsgroup(mlist) Sep 20 10:51:35 2002 gate_news(9301): File "/home/mailman/cron/gate_news", line 89, in open_newsgroup Sep 20 10:51:35 2002 gate_news(9301): password=mm_cfg.NNTP_PASSWORD) Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 117, in __init__ Sep 20 10:51:35 2002 gate_news(9301): self.welcome = self.getresp() Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 203, in getresp Sep 20 10:51:35 2002 gate_news(9301): resp = self.getline() Sep 20 10:51:35 2002 gate_news(9301): File "/usr/local/lib/python2.2/nntplib.py", line 192, in getline Sep 20 10:51:35 2002 gate_news(9301): line = self.file.readline() Sep 20 10:51:35 2002 gate_news(9301): IOError : [Errno 131] Connection reset by peer ---------------------------------------------------------------------- Comment By: Ron Jarrell (jarrell) Date: 2002-10-22 11:19 Message: Logged In: YES user_id=34619 Didn't work... This comes up, btw, not during initial connection, but if the connection goes away during a gate_news run, like the daemon on the other end dies, or the news server reboots, etc. You get an IOerror on the mailman side. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-15 15:00 Message: Logged In: YES user_id=12800 I'm applying this patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-15 14:19 Message: Logged In: YES user_id=12800 I didn't realize that nntplib.NNTP() can raise an IOError -- I thought it would have been a socket.error. Oh well, here's an untested patch. I think I'll check this in just because I don't see how it could break anything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=620033&group_i…

1 0

[ mailman-Bugs-630497 ] Traceback in error file
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #630497, was opened at 2002-10-29 09:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_i… Category: bounce detection Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Andy Carpenter (acarpenter) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in error file Initial Comment: Since I upgraded to 2.1b4, I have started to get the following tracebacks in the error log file. It is a characteristics of our busiest mail list that many of the posts come from the far east with unicode characters in their subject line. Oct 29 14:19:35 2002 (26533) Uncaught runner exception: ASCII decoding error: or dinal not in range(128) Oct 29 14:19:35 2002 (26533) 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/IncomingRunner.py" , line 129, in _dispo se status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py" , line 167, in _dopip eline mlist.BounceMessage(msg, msgdata, e) File "/usr/local/mailman/Mailman/Bouncer.py", line 273, in BounceMessage lang=self.preferred_language) File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=630497&group_i…

1 0

[ mailman-Bugs-540978 ] List-* header multiline split bug
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

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: Open Resolution: None >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-610570 ] RFC 2369 URL is broken
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #610570, was opened at 2002-09-17 10:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_i… Category: documentation Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Nick Arnett (narnett) Assigned to: Nobody/Anonymous (nobody) Summary: RFC 2369 URL is broken Initial Comment: Paths to RFCs have changed. The correct one for 2369 is now http://www.faqs.org/rfcs/rfc2369.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_i…

1 0

[ mailman-Bugs-643231 ] Last archived date is incorrect
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #643231, was opened at 2002-11-24 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_i… Category: Pipermail Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Last archived date is incorrect Initial Comment: The last archived date/time is incorrect. Time appears to be GMT, not local time (e.g. ahead 5 hrs for sites in EST) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643231&group_i…

1 0

[ mailman-Bugs-629616 ] Invalid admin notification
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #629616, was opened at 2002-10-27 19:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_i… Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Invalid admin notification Initial Comment: Using latest CVS (2.1b4). When someone subscribes through the web interface (listinfo page), the list admin will receive an invalid email if subscription notification has been turned on. The email contains the content of adminsubscribeack.txt, but no string interpolation is done. This is not the case if subscribing using the mail command interface or subscribed by the admin using the admin page. Also, if the subscribing user chooses a different language than the list language, the email notification sent to the admin will have a Subject: according to the list language, but body according to what the subscribing user chose. Which is probably not what we want... ;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=629616&group_i…

1 0