From owner-freebsd-hackers Tue Mar 25 00:29:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA28138 for hackers-outgoing; Tue, 25 Mar 1997 00:29:10 -0800 (PST) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA28131 for ; Tue, 25 Mar 1997 00:29:07 -0800 (PST) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id JAA11653; Tue, 25 Mar 1997 09:28:18 +0100 (MET) From: Mikael Karpberg Message-Id: <199703250828.JAA11653@ocean.campus.luth.se> Subject: Re: Cool Web page interface to mail + search engine? To: terry@lambert.org (Terry Lambert) Date: Tue, 25 Mar 1997 09:28:18 +0100 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <199703242142.OAA23592@phaeton.artisoft.com> from Terry Lambert at "Mar 24, 97 02:42:10 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Terry Lambert: > > > The benefit is in having a date-order stamp on message *that came > > > into* majordomo. [...] > OK... I was just thinking that the "massage" could be done by a local > SMTP modification on freefall to put the stamp in the desired format, > since it is a generated value anyway. This would save later header > banging. But if you must do header banging anyway... then toy can > go ahead and do it without worring about the issue. > > In any case, a known date stamp and Subject line should be enough > to thread most data correctly. I think something like a X-FreeBSD-List-Mark with date and sender of the message would be real nice for filtering. If you knew that it was always there in all mails from the lists, and it had a datestamp and all. Even if the indexing engine has to do major header parsing anyway, then at least people's filter wouldn't have to. That'd be nice, no? /Mikael