[Mailman-Developers] Improving the archives

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Nigel,

On Jul 20, 2007, at 10:38 AM, Nigel Metheringham wrote:

> On 20 Jul 2007, at 15:26, Barry Warsaw wrote:
>>> BTW lurker gives all messages an ID which is 3 parts separated by
>>> periods. The first part is a date field - ie 20070720, the second
>>> part is the receive time, UTC, as 6 digits, and the final part
>>> is some form of hex id. The nice part is if you quote just the
>>> first (or first 2) parts of message ID you get messages around that
>>> time...
>>
>> Obviously Mailman can't know the second and third parts so it can't
>> use them in its list copies.  I dislike using YYYMMDD because of the
>> high number of collisions.
>
> Its used as part of a UID, but has the nice feature of allowing easy
> queries as to other messages at that time.

That should definitely be a way to traverse to the message, but it's  
not the message's global id (a.k.a. canonical address relative to the  
base url of the message store).  An archiver could provide other ways  
to traverse to the message, such as:

/barry at python.org/ to see all messages by me
/barry at python.org/mailman-developers/20070720 to see all messages by  
me today to this mailing list
/Subject?Improving%20the%20archives&sort=thread to find all the  
messages in this thread regardless of when they were posted

etc.

> If the archiver is local you also have the information for part 2  
> of the
> UID - lurker takes it from the From_ line.

Mailman gets the From_ line before passing off to the archiver.  But  
that's interesting, does lurker /require/ the From_ line?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQCVAwUBRqDMInEjvBPtnXfVAQKJFAP/Y3FsBIXrSaRZ85eCl+pVTZxez2uRn0KB
2OMBV6vS/qC8K1R/myeGpBVr44yE/AfTa+kf+MLSlIlMpJdUlWDMWw2G90IPy1gv
t1VGrwbVPmOlLFxF8kIsi6NKIZpKoJrJVdQnSc+uPCqowIDU9FQ57+2hrH8HayTS
ISAZ0FTgAzk=
=sp+m
-----END PGP SIGNATURE-----