Mailman 3 August 2002 - Mailman-Developers

Message unparsable errors
by Bob Puff＠NLE Aug. 24, 2002

Aug. 24, 2002

In doing a routine looksee at my MM 2.1b3 install, I saw some data in my error log: Aug 13 21:01:29 2002 (9001) lost data files for filebase: 1029286885.82315+6620b 7dc5eb172c8752545915a9096a3778b0616 Aug 13 21:07:31 2002 (9001) message is unparsable: 1029287248.371788+6b3b5f5a932 4846f9ca26c0d3209f046aca69449 Aug 13 21:07:31 2002 (9001) lost data files for filebase: 1029287248.371788+6b3b 5f5a9324846f9ca26c0d3209f046aca69449 Aug 13 21:12:31 2002 (9001) message is unparsable: 1029287493.927862+c335a400f9a 1513dd5a6ca7d2c2154f72846c3fe Aug 13 21:12:31 2002 (9001) lost data files for filebase: 1029287493.927862+c335 a400f9a1513dd5a6ca7d2c2154f72846c3fe Aug 13 21:58:31 2002 (9001) message is unparsable: 1029290306.708443+f57c6fcfcbf f0bd3662c8a47e39e113f2352fa1c Aug 13 21:58:31 2002 (9001) lost data files for filebase: 1029290306.708443+f57c 6fcfcbff0bd3662c8a47e39e113f2352fa1c Aug 16 21:05:41 2002 (9001) message is unparsable: 1029546301.349363+ad52387697e 04f59e9a9647ead0822b6e27497ee Aug 16 21:05:41 2002 (9001) lost data files for filebase: 1029546301.349363+ad52 387697e04f59e9a9647ead0822b6e27497ee Aug 16 21:08:41 2002 (9001) message is unparsable: 1029546511.308229+be0a322837d cec9eda90366f706bd2e5594ed906 Aug 16 21:08:41 2002 (9001) lost data files for filebase: 1029546511.308229+be0a 322837dcec9eda90366f706bd2e5594ed906 As far as I can tell, no message was sent to MM2.1 on August 16 - at least it's not recorded in the post log. Also, in the vette log, what does this mean: Jul 24 08:59:43 2002 (9003) Precedence: bulk message ignored by: aes-la-request@ light-list.com Aug 15 08:00:04 2002 (9003) Precedence: bulk message ignored by: aes-la-request@ light-list.com Thanks! Bob

2 1

[ mailman-Bugs-599544 ] user mailman can't start mailmanctl
by noreply＠sourceforge.net Aug. 24, 2002

Aug. 24, 2002

Bugs item #599544, was opened at 2002-08-24 02:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=599544&group_i… Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: user mailman can't start mailmanctl Initial Comment: with the latest cvs as of Aug 24, mailmanctl can't be started by the mailman user. root can start. A quick patch is attatched. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-24 19:50 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=599544&group_i…

1 0

[ mailman-Bugs-599544 ] user mailman can't start mailmanctl
by noreply＠sourceforge.net Aug. 24, 2002

Aug. 24, 2002

Bugs item #599544, was opened at 2002-08-24 06:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=599544&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: user mailman can't start mailmanctl Initial Comment: with the latest cvs as of Aug 24, mailmanctl can't be started by the mailman user. root can start. A quick patch is attatched. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=599544&group_i…

1 0

[ mailman-Bugs-596361 ] rejection-notice not translated
by noreply＠sourceforge.net Aug. 24, 2002

Aug. 24, 2002

Bugs item #596361, was opened at 2002-08-17 06:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_i… Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: rejection-notice not translated Initial Comment: on the admindb screen, detailed description of the held messages include 'rejection-notice' field to be sent to the message sender but the default value in the text form is in english and not translated into the list-preferred language. Following short patch may work: --- admindb.py.orig Fri Aug 16 11:39:53 2002 +++ admindb.py Sat Aug 17 14:57:37 2002 @@ -595,8 +595,8 @@ t.AddRow([ Bold(_('If you reject this post,<br>please explain (optional):')), TextArea('comment-%d' % id, rows=4, cols=80, - text = Utils.wrap(msgdata.get('rejection-notice', - _('[No explanation given]')), + text = Utils.wrap(_(msgdata.get('rejection-notice', + _('[No explanation given]'))), column=80)) ]) row, col = t.GetCurrentRowIndex(), t.GetCurrentCellIndex() ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-08-24 00:17 Message: Logged In: YES user_id=67709 Sorry for the inconvenience. I uplaod a diff file. There is some clutter in creating mailman.pot, so I revised the patch. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 21:16 Message: Logged In: YES user_id=12800 In general it's better to attach patches instead of pasting them in. SF doesn't preserve whitespace :( Updating this one so SF will send me the whitespace preserved patch in an email notification. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_i…

1 0

problem with log rotation for mailman on RedHat 7.3
by Barry Gould Aug. 24, 2002

Aug. 24, 2002

something really strange is going on with log rotation for the RedHat mailman package... it keeps adding more and more .x.gz... files in the log dir. I don't think I've modified it since installing RedHat, other than upgrading the mailman rpm due to the security notice. let me know if you have any questions. Thank you, Barry [root@mail log]# rpm -q mailman mailman-2.0.11-1 [root@mail log]# ll /var/log/mailman/ total 4 -rw-rw-r-- 1 mailman mailman 0 Aug 18 04:02 error -rw-rw-r-- 1 mailman mailman 0 Aug 19 04:02 error.1.gz -rw-rw-r-- 1 mailman mailman 0 Aug 20 04:13 error.1.gz.1.gz -rw-rw-r-- 1 mailman mailman 0 Aug 21 04:02 error.1.gz.1.gz.1.gz -rw-rw-r-- 1 mailman mailman 0 Aug 22 04:02 error.1.gz.1.gz.1.gz.1.gz -rw-rw-r-- 1 mailman mailman 0 Aug 23 04:02 error.1.gz.1.gz.1.gz.1.gz.1.gz -rw-rw-r-- 1 mailman mailman 200 Aug 14 12:32 error.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz [root@mail log]# cat /etc/logrotate.d/mailman /var/log/mailman/* { missingok } Barry Gould Site Administrator, Harte-Hanks Shoppers 714-577-4313 or 877-244-4421 http://www.pennysaverusa.com http://www.theflyer.com

1 0

[ mailman-Bugs-214163 ] Netscape vCards (PR#201)
by noreply＠sourceforge.net Aug. 23, 2002

Aug. 23, 2002

Bugs item #214163, was opened at 2000-09-11 16:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214163&group_i… Category: None >Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Netscape vCards (PR#201) Initial Comment: Jitterbug-Id: 201 Submitted-By: Danny.Hite(a)ncmail.net Date: Mon, 14 Feb 2000 11:02:48 -0500 (EST) Version: 1.1 OS: Redhat Linux 6.1 Our organization uses Netscape 4.x for email. The problem is the vCard attachments to messages that are posted to <listname>-request@...... Below is a paste of the message that I get when sending these requests. And yes, if I turn off vCards, it does not give me the error messages. Just wondering if there is a workaround to this. ---------------Begin Paste--------------- This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address <test-request(a)wse114.deh.ehnr.state.nc.us>. To obtain instructions on valid Mailman email commands, send email to <test-request(a)wse114.deh.ehnr.state.nc.us> with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to <test-admin(a)wse114.deh.ehnr.state.nc.us>. The following is a detailed description of the problems. ***** who Digest Members: ?????.????(a)ncmail.net <<<<<<<<<<REPLACED BY ME>>>>>>>>>>>>> Non-Digest Members: danny.hite(a)ncmail.net Command? This is a multi-part message in MIME format. Command? --------------673C83360F5786D2AB551932 Command? Content-Type: text/plain; charset=us-ascii Command? Content-Transfer-Encoding: 7bit Command? --------------673C83360F5786D2AB551932 >>>>> >>>>> Too many errors encountered; the rest of the message is ignored: > Content-Type: text/x-vcard; charset=us-ascii; > name="Danny.Hite.vcf" > Content-Transfer-Encoding: 7bit > Content-Description: Card for Danny Hite > Content-Disposition: attachment; > filename="Danny.Hite.vcf" > > begin:vcard > n:Hite;Danny > tel;fax: > tel;work: > x-mozilla-html:FALSE > org:NC DENR;DEH > version:2.1 > email;internet:Danny.Hite@ncmail.net > title:LAN Administrator > adr;quoted-printable:;;=0D=0A;;;; > fn:Danny Hite > end:vcard > > --------------673C83360F5786D2AB551932-- > > ---------------End Paste--------------- ==================================================================== Audit trail: None ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:40 Message: Logged In: YES user_id=12800 MM2.1's mail command processor is MIME aware now. We can now close the oldest bug in the database. Yee haw! :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-15 17:52 Message: MailCommandHandler should be MIME aware, and refuse to parse any part that isn't text/* type. Since vCards are text/x-vcard type, MailCommandHandler should additionally have a list of text/* subtypes that are ignored. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214163&group_i…

1 0

[ mailman-Bugs-214205 ] e-mail<->usenet gateway Reply-To header (PR#303)
by noreply＠sourceforge.net Aug. 23, 2002

Aug. 23, 2002

Bugs item #214205, was opened at 2000-09-11 16:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_i… Category: nntp/news >Group: 2.1 beta Status: Open Resolution: None Priority: 4 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry A. Warsaw (bwarsaw) Summary: e-mail<->usenet gateway Reply-To header (PR#303) Initial Comment: Jitterbug-Id: 303 Submitted-By: orion(a)tribble.dyndns.org Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT) Version: 2.0beta4 OS: Debian linux potato I'm running a plain e-mail<->usenet gateway. When someone replies to a usenet post through the list, his e-mail client sets an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to improperly thread messages. I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line 82: # if the message is a reply to a previous post, change the header so # that newsreaders can thread it properly if msg.getheader('in-reply-to'): msg.headers.append('References: %s\n' % msg.getheader('in-reply-to')) del msg['in-reply-to'] I'm happy to say that this solved the problem. (before you laugh at me, take note that I never looked at python before.) ==================================================================== Audit trail: None ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:38 Message: Logged In: YES user_id=12800 Changing the group to 2.1 beta because I want to look at threading issues for gated messages before 2.1 final is released. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 08:34 Message: Logged In: YES user_id=531451 What a coincidence! I had the same problem and I looked into the code, then modified it to work properly. The coincidence is that my patch is *identical* to yours. So, for sure it works :-) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-27 17:00 Message: RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-19 12:48 Message: This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_i…

1 0

[ mailman-Bugs-219808 ] Missing dependancy for 'configure'.
by noreply＠sourceforge.net Aug. 23, 2002

Aug. 23, 2002

Bugs item #219808, was opened at 2000-10-30 17:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_i… Category: configuring/installing >Group: 2.1 beta Status: Open Resolution: None Priority: 2 Submitted By: Thomas Wouters (twouters) Assigned to: Thomas Wouters (twouters) Summary: Missing dependancy for 'configure'. Initial Comment: The Mailman makefile is missing a dependancy on 'configure', so when 'configure' is updated, it isn't re-run automatically, and you aren't warned to reconfigure. (definately low-priority bug though :) (I also ran into something weird when running 'config.status' to do the reconfiguring for me... it set 'MAILMAN_UID' in Defaults.py to 'mailman', without quotes, instead of the numeric uid. That might be caused by a mix of an old config.status and a new configure, though, as I wasn't able to reproduce it on another box.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_i…

1 0

[ mailman-Bugs-222962 ] Umlauts are behaving badly
by noreply＠sourceforge.net Aug. 23, 2002

Aug. 23, 2002

Bugs item #222962, was opened at 2000-11-20 06:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=222962&group_i… Category: Pipermail >Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Umlauts are behaving badly Initial Comment: Umlaut characters and our nice scandinavic characters are behaving badly in the pipermail archives. As an example see the archive: http://oh3tr.ele.tut.fi/pipermail/moppe-archive/ All ä:s and ö:s are displayed like "=E4" in the message body. If there are those characters in the subject the subject line will appear as total mess. This could be corrected if those 8bit characters would be allowed to go through the archiver as they are. At the moment the text version is also messed with those =E4 characters. Tested versions: up to Pipermail 0.05 (Mailman 2.0beta5). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:37 Message: Logged In: YES user_id=12800 I'm sure all this stuff is resolved in the latest MM2.1 betas. ---------------------------------------------------------------------- Comment By: Gisle Hannemyr (gisleh) Date: 2001-11-08 07:42 Message: Logged In: YES user_id=370926 The submitter states that "This could be corrected if those 8bit characters would be allowed to go through the archiver as they are". This is wrong. Mailers these days use quoted-printable encoding for 8-bit characters, and the archiver need to be aware om MIME headers and content encodings and decode things correctly (just like a MUA need to be). As Bernard has already stated, this is a missing feature, but an important one! ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2000-12-08 09:26 Message: Pipermail cannot handle mime messages and content encodings well. You could also say that it is missing the most part from being a nice mail archiving program. Mailman also needs to be internationalised. (Which is long overdue...but obviously somebody has to jump in there.) So it is not really bug, it is a missing feature. You could alternatively use a _real_ external mail archiving program. There are two I know of (both have their own problems) monarch and hypermail. Bernhard ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2000-11-23 19:43 Message: Yes, I would also like MIME-decoding of the subject-line in the header. I tested the release version now, and the same behavious is still there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=222962&group_i…

1 0

[ mailman-Bugs-227371 ] Bounced message not detected as bounce
by noreply＠sourceforge.net Aug. 23, 2002

Aug. 23, 2002

Bugs item #227371, was opened at 2001-01-02 22:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=227371&group_i… Category: bounce detection >Group: 2.0.x >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Bounced message not detected as bounce Initial Comment: SMTP Server ID: 220 csd.k12.nh.us FirstClass ESMTP Mail Server v5.50 ready Response from mail sent to invalid user[bouncethis(a)cnhec.concord.k12.nh.us] is not interpretted as a bounce and instead is sent to the list for delivery. (Good thing only subscribers can post or else a large mailstorm would have ensued). A copy of the bounce message follows: Received: .([204.238.196.5]) by dimentech.com with ESMTP id WAA08044 for <zzzzzzz(a)zzzzzzz.com>; Tue, 2 Jan 2001 22:32:36 -0500 (EST) Message-id: <fc.0084c06300094ece3b9aca00119ba7cf.94ecf(a)csd.k12.nh.us> Date: Tue, 02 Jan 2001 22:34:11 -0500 Subject: NDN: test X-FC-Icon-ID: 2031 X-FC-MachineGenerated: true To: dwatts(a)dimentech.com From: "Mailer-Daemon" <Mailer-Daemon(a)csd.k12.nh.us> MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-UID: 166 Sorry. Your message could not be delivered to: bouncethis,FCServer1 (The name was not found at the remote site. Check that the name has been entered correctly.) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:36 Message: Logged In: YES user_id=12800 I'm closing this because MM2.1 has much improved bounce processing, and because it's a royal pain to grok out the original bounce message when it was pasted in instead of attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=227371&group_i…

1 0