On Tue, Mar 07, 2023 at 10:35:02PM +0100, Sebastian Andrzej Siewior wrote:
The default message-id uses a timestamp and a few random bytes encoded as base64 (with safe URL dictionary) as the user part. This is fine already.
Hi Everyone,Just to reiterate. I'm only maintaining the stable branch at this point - meaning bug fixes.
Although #400 isn't technically a bug fix (since there is nothing illegal or wrong with the message-id) I am making an exception with the Base 64 encoding change because of the amount of pain it is apparently causing.
However, I don't have the time or interest to participate in another message-id bike shedding discussion, and don't plan on changing the default format in the stable branch.
Thanks for your understanding. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
