[Mailman-Developers] [Bug 985149] [NEW] Add List-Post value to permalink hash input

[Barry Warsaw]

On Apr 19, 2012, at 10:30 AM, Stephen J. Turnbull wrote:

>On Thu, Apr 19, 2012 at 5:03 AM, Barry Warsaw <barry at list.org> wrote:
>
>>  - Proposal is to append the List-Post value as input to the hash, after
>>   the Message-ID value (sans angle brackets).
>
>First, List-POST, not List-ID?  List-Post is not permanent!

Sorry, yes I definitely meant List-ID.

>Second, that order is wrong IMHO; the idea of the hash is to identify
>the message in a fixed-length format.  If you want to qualify it with
>list information, why not add the list identifier to the *output* of
>the hash?  Now you have a well-defined[1] format that (1) allows you
>to distinguish cross-posted instances of the same message *and* (2)
>identify cross-posted instances of the same message, depending on your
>application.

I think the hash value should be opaque.  Jeff can perhaps elaborate his
use-case but I don't think the List-ID needs to be (or frankly *should* be)
extractable from the hash, but instead just needs to inform the hash value.
IOW, if you cross-post a message with Message-ID: <foo> to one at example.org and
two at example.com, you'd get two different messages forwarded to the archives,
and they would have different Permalink: hash values.  Before this proposal,
they'd have the same value.

Of course, the List-ID itself should be preserved in the message that the
archiver gets, so an archiver could still discriminate on that.

>[1] I haven't read the List-ID RFC recently, but I think its format is
>quite restricted and likely to be of reasonable length.  I don't see
>why Mailman can't require a List-ID for every list.

Mailman always adds a List-ID header.  RFC 2919 describes it.  TL;DR:

List-ID: <listname.dom.ain>

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20120420/88ec0185/attachment.pgp>