Am 12.01.24 um 11:40 schrieb Jeremy Harris via Exim-users:
If they're not willing to do that, and reissue the exim binary, a hack
in the perl
of exiqgrep is feasible...
\s*(?(?:\w{6}-\w{6}-\w{2}|\w{6}-\w{11}-\w{4})) # old, 2023
msgid formats
becomes
\s*(?(?:\w{6}-\w{6}-\w{2}|\w{6}-\w{11
Hello!
On Fri, 12 Jan 2024 at 10:40:45 (+), Jeremy Harris via Exim-users wrote:
> \s+(?<.*?>) matches the <> (though the ? is pointless, given the *)
Out of scope of the thread: it's actually not pointless as it limits
capture group, roughly saying, to `<[^>]*>' (the `?' makes `.*' be n
On 1/12/24 08:14, Cyborg via Exim-users wrote:
[~]# mailq
9h 2.2K 1rO3sE-005JbF-1D-H <> *** frozen ***
xxx...@.de
They need to pick up commit 1d19531abc45 at the very least:
Date: Sun Nov 19 11:31:45 2023 +
Support old-format message_id spoolfiles for mailq / -bp.
Am 12.01.24 um 09:28 schrieb Niels Kobschätzki:
There is a tool for converting old message-ids to new ones.
Or you wait until all messages with the old IDs are out of the queue.
It's not the message ids.
it's this => \s+(?<.*?>) part of the regexp.
As soon as you remove that part, it work
There is a tool for converting old message-ids to new ones.
Or you wait until all messages with the old IDs are out of the queue.
Best,
Niels
> On Jan 12, 2024, at 09:17, Cyborg via Exim-users
> wrote:
>
> Hi all,
>
> Fedora pushed an exim 4.97.1 update last night and now exiqgrep -cz sh
Hi all,
Fedora pushed an exim 4.97.1 update last night and now exiqgrep -cz
shows this error message, which breaks the munin plugin für the mailqueue.
[~]# mailq
9h 2.2K 1rO3sE-005JbF-1D-H <> *** frozen ***
xxx...@.de
[~]# exiqgrep -cz
Line mismatch: 9h 2.2K 1rO3
