Sebastian Andrzej Siewior wrote in
<20230307_213502_4a7zc...@breakpoint.cc>:
|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.
|It would be beneficial for the human parser to have the timestamp
Sebastian Andrzej Siewior wrote:
> On 2023-03-07 08:43:38 [+], Eric Wong wrote:
> > Thanks Kevin. Any chance you can restore the %Y%m%d%H%M%S prefix?
> >
> > I brought this up here in a patch <20210110213922.iqTO594q5DM@dcvr>.
>
> couldn't fine this.
My patch predates message_id_format, th
Eric Wong wrote:
> > -fmt = "<%z@%f>";
> > +fmt = "<%Y%02m%02d_%02H%02M%02S_%r%r@%f>";
>
> Kinda shocked that the %02's are necessary for a user-facing
> config file, but yes, it's a much more reasonable default with
> this patch so users won't have to deal with it :>
I was so shocked by
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
On Tue, Mar 07, 2023 at 10:43:00PM +0100, Steffen Nurpmeso wrote:
> Sebastian Andrzej Siewior wrote in
> <20230307_213502_4a7zc...@breakpoint.cc>:
> > 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
> >
On 2023-03-07 15:15:22 -0800, Kevin J. McCarthy wrote:
> 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.
Anyway, the message-id format is configurable with $message_id_
