--On 7. März 2016 um 14:35:47 -0800 Mark Sapiro <m...@msapiro.net> wrote:
If an exception is caught, the date is simply set to the current time.
I understand the patch, but I'm not sure if setting the current time is
appropriate. In particular, the self.__super_set_date(message) method,
if it doesn't find a valid date: or x-list-received-date: header in the
message will set the time to that of the previous article + 1 second.
I suppose that didn't work, because there were multiple such messages in a
row, if you can even call them that ;-)
In any case, I'd like to understand more about why/how the issue occurs.
To that end, I'd like to see a copy of the offending message from the
mbox file. Also, I wonder if bypassing the error and setting a date
which will almost certainly archive the message in the wrong period is
better than fixing the message in the mbox.
The thing is that initially I had no way of finding out which messages
caused the problem. That's why I primarily looked for a way to just
complete the job of rebuilding the archive. I agree that there may be
better solutions. I could imagine skipping such broken messages, for
example.
Here are the culprits. They are now easy to find, because they are all new
in the archive :-) (which is public, btw:
<https://lists.uni-koeln.de/pipermail/linux-users/2016-March/thread.html>)
---------------------
From foo@bar Mon Nov 7 14:08:46 2005
169562
From foo@bar Mon Nov 7 14:08:46 2005
27203
From foo@bar Mon Nov 7 14:08:46 2005
108420
From foo@bar Mon Nov 7 14:08:46 2005
35662
----------------------
Don't ask me how they ended up in that .mbox file in the first place ;-)
I assume they are an artefact from the time when we moved from Majordomo to
Mailman.
Then there are a few broken spam messages:
----------------------
From owner-linux-us...@rrz.uni-koeln.de Mon Nov 7 14:13:18 2005
Received: (from daemon@localhost)
by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) id CAA05687
for linux-users-out; Mon, 18 Dec 2000 02:34:21 +0100 (MET)
Received: from horizon.barak-online.net (horizon.barak.net.il
[206.49.94.218])
by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id CAA05681
for <linux-us...@rrz.uni-koeln.de>; Mon, 18 Dec 2000 02:34:18 +0100
(MET)
Received: from rrz.uni-koeln.de (pop09-1-ras1-p146.barak.net.il
[212.150.107.146])
by horizon.barak-online.net (8.9.3/8.9.1) with SMTP id DAA28082
for linux-us...@rrz.uni-koeln.de; Mon, 18 Dec 2000 03:33:39 +0200
(IST)
Message-Id: <200012180133.daa28...@horizon.barak-online.net>
From: mnadiv<mna...@barak-online.net>
REPLY-TO: mna...@barak-online.net
X-Mailer: EzyMassMailer V2.xx
Date: 18 ãöîáø 2000
From owner-linux-us...@rrz.uni-koeln.de Mon Nov 7 14:08:09 2005
Received: from mail1.rrz.Uni-Koeln.DE (localhost [127.0.0.1])
by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with ESMTP id
g5UBbvtD027896
(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168
verify=NOT)
for <linux-users-...@mail1.rrz.uni-koeln.de>; Sun, 30 Jun 2002
13:37:57 +0200 (MEST)
Received: (from daemon@localhost)
by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.3/Submit) id g5UBbvU7027895
for linux-users-out; Sun, 30 Jun 2002 13:37:57 +0200 (MEST)
Received: from yahoo.com ([213.201.170.67])
by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with SMTP id
g5UBbstC027887
for <linux-us...@uni-koeln.de>; Sun, 30 Jun 2002 13:37:55 +0200
(MEST)
Received: from [181.21.240.177] by f64.law4.hottestmale.com with asmtp; 01
Jul 0102 04:46:55 -0900
Received: from 15.9.163.146 ([15.9.163.146]) by m10.grp.snv.yahui.com with
QMQP; Sun, 30 Jun 0102 19:38:13 -0800
Reply-To: <sann...@yahoo.com>
Message-ID: <025b58a45d4d$4771c5b1$6dd17ce3@warwgu>
From: <sann...@yahoo.com>
To: susann...@yahoo.com
Subject: Hello
Date: Sun, 30 Jun 0102 17:30:47 -0600
----------------------
There is a single legitimate message with a broken Date header:
From owner-linux-us...@rrz.uni-koeln.de Mon Nov 7 14:11:54 2005
Received: (from daemon@localhost)
by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) id AAA14125
for linux-users-out; Fri, 4 Feb 2000 00:50:08 +0100 (MET)
Received: from mailhost.informatik.uni-bonn.de
(olymp.informatik.uni-bonn.de [131.220.4.1])
by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id AAA14116
for <linux-us...@rrz.uni-koeln.de>; Fri, 4 Feb 2000 00:50:06 +0100
(MET)
Received: from zeus.informatik.uni-bonn.de (zeus.informatik.uni-bonn.de
[131.220.5.25])
by mailhost.informatik.uni-bonn.de (Postfix) with ESMTP
id 15D5562E9; Fri, 4 Feb 2000 00:51:32 +0100 (MET)
Received: (from guertler@localhost)
by zeus.informatik.uni-bonn.de (8.8.8+Sun/8.8.8) id AAA19251;
Fri, 4 Feb 2000 00:51:43 +0100 (MET)
From: Michael Guertler <guert...@triton.informatik.uni-bonn.de>
Message-Id: <200002032351.aaa19...@zeus.informatik.uni-bonn.de>
Subject: Re: AVI -> MPEG
To: ocor...@astro.uni-bonn.de (Oliver Cordes)
Date: Fri, 4 Feb 100 00:51:42 +0100 (MET)
At the very least I would suggest that arch should dump the headers of the
offending message, so that it can be repaired, but I'm open for other
suggestions.
Cheers
Sebastian
--
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
