>>>>> "John" == John W Baxter <[EMAIL PROTECTED]> writes:
John> In addition, the Message-Id values would have to be
John> filtered, if used as is, for URL-unfriendly characters
I don't think so. AFAIK, that was fixed about 2000 RFCs ago. When
used as URLs, conforming agents will URL-encode them. How the archive
chooses to implement identifying a storage location from the decoded
URL is up to it. The URL-encoded string as filename is an obvious
choice, but database-based archives might just use the raw Message-ID.
BTW, I just realized that Google probably does index Message-IDs
already (as long as the archived message includes that header), so
Googleability is _not_ an advantage of my scheme over the header
digest approach. The ability to algorithmically construct URNs and
URLs however still is.
John> There's also the small point that the presence of
John> Message-Id: is a SHOULD, not a MUST (some compromise in the
John> musty past of the IETF, no doubt).
I would guess that's for the convenience of folks who use "telnet HOST
25" as their MTA. Humans are notoriously bad at generating unique
anything.<wink> Anyway, my algorithm just treats such messages as a
collision with all the others that don't have Message-IDs.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
------------------------------------------------------
Mailman-Users mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
