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

Richard Wackerbarth richard at nfsnet.org
Wed Apr 18 21:22:25 CEST 2012


I definitely agree that "Now's the time".

I don't understand the proposal. By "added to this hash", do you mean
"included in the set of elements that get hashed" or do you mean
"appended to the hash value"?

Presumedly, the sole purpose in publishing an algorithm to create the
hash is to make it possible for two handlers to independently develop
the same hash given only the message. Otherwise, a "secret" method could
be used to assign a unique identifier to the message.

In either case, this suggested change renews my argument that the
resulting hash should be tagged, visibly, with a "protocol revision
designator". Omitting that designation transforms the chosen calculation
method into a "secret".


On Apr 18, 2012, at 1:53 PM, Barry Warsaw wrote:

> Public bug reported:
> Currently, we define the X-Message-ID-Hash as the base32 encoding of the
> sha1 hash of the Message-ID content (sans angle brackets as defined in
> RFC 5322).  The suggestion is made that List-Post value should be added
> to this hash so as to be able to distinguish cross-posted messages.
> This should be fine, and pretty easy.  My only concern is that the
> header name is now a misnomer.
> I wonder, is it worth coming up with a better header?  Now's the time to
> do it since it's likely that there are almost no consumers of this
> standard.
> What about `Permalink-Hash` ?
> ** Affects: mailman
>     Importance: High
>         Status: Confirmed
> ** Tags: mailman3

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  Add List-Post value to permalink hash input

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list