Thanks for the bug report, EOLE team.
I can confirm that the exiqgrep command indeed fails on Jammy. I will
see about backporting the fix to the package.
BTW, this also affects Debian and there's a bug opened against the
Debian exim4 package.
** Changed in: exim4 (Ubuntu)
Status: New => Triaged
** Changed in: exim4 (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Bug watch added: Debian Bug tracker #1006661
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006661
** Also affects: exim4 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006661
Importance: Unknown
Status: Unknown
** Changed in: exim4 (Ubuntu)
Importance: Undecided => High
** Also affects: exim4 (Ubuntu Jammy)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966923
Title:
exiqgrep -r and -f options match all messages if no
To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1966923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
