Re: Publicly available mbox archives of debian mailing lists + Bug#161440
- To: firstname.lastname@example.org
- Subject: Re: Publicly available mbox archives of debian mailing lists + Bug#161440
- From: Martin Mewes <email@example.com>
- Date: Mon, 2 May 2005 10:25:09 +0200
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <20050428170051.GA3757@zero.mknod.org>
- References: <20050428031742.GA5878@localhost.localdomain> <email@example.com> <20050428170051.GA3757@zero.mknod.org>
Graham Wilson <firstname.lastname@example.org> wrote :
> On Thu, Apr 28, 2005 at 12:45:17PM +0200, Martin Mewes wrote:
> > Pascal Hakim <email@example.com> wrote :
> > > You might want to obscure those a little bit. You should probably
> > > munge the Return-Path from those emails, and possibly the top
> > > Received: header.
> > Munging works are in queue. The Mbox-Project is working on this,
> > right now I am only hosting the files.
> What are you talking about munging? Aren't all of the mbox files only
> available as compressed tarballs?
Munging means, that all headers which should be necessary for archiving
(and not doing harmful whings to threading) should be ...
Date, From, To, Subject, Message-ID, Mail-Followup-To, References,
Mime-Version, Content-Type, Content-Disposition, In-Reply-To,
Resent-Message-ID, Resent-From, X-Mailing-List, X-Loop, The
List-Headers, Resent-Sender, Resent-Date.
In this case we will untar the archives, do a formail on them and repack
them again some day. The only thing which matters right now is time to
do it ;-)
bis dahin/kind regards
FAQ fuer firstname.lastname@example.org
FAQ fuer email@example.com