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

On Apr 22, 2012, at 03:31 PM, Jeff Breidenbach wrote:
In theory, I agree, which is why you'll see the posting address used as the primary key into the mailinglist table in the database. You'll almost always see that in the To: header, although some situations might cause mismatches, e.g. acceptable aliases. According to the language in RFC 2369, this also (only!) may show up in the List-Post header for the from-list copy of the message, but you might find the List-Post has nothing useful, e.g. "NO" (with some random goo of trailing comment). List-ID will always be included in the from-list copy.
Well, Message-ID also fails the "human friendly" part, e.g. from your message:
Message-ID: <CAHjiUboZzYAE1dgApzfFNMqv_X+X6xA9E1bOc3F+mQ3qcTeeeQ@mail.gmail.com>
My fingers already hurt typing that into my spell-correcting smartphone. :)
FWIW, Base 32 was deliberately chosen because it's case insensitive, and allows for optional mapping of commonly mistaken substitutions (e.g. zero for oh, and one for eye or el). IOW, it's much more forgiving of the human part of the process.
Certainly no need for a triumverate of short hash, long hash, and message-id. Less is better.
Agreed. Is 32 bytes too long? Is 4 bytes too short? What's an acceptable trade-off between collision likelihood and human convenience?
-Barry
participants (1)
-
Barry Warsaw