exiqgrep -r and -f options match all messages if no
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
exim |
Fix Released
|
Unknown
|
|||
exim4 (Debian) |
Fix Released
|
Unknown
|
|||
exim4 (Ubuntu) |
Fix Released
|
High
|
Sergio Durigan Junior | ||
Jammy |
Fix Released
|
High
|
Sergio Durigan Junior |
Bug Description
On jammy, exiqgrep command shows syntax errors :
root@eolebase:~# exiqgrep
syntax error at /usr/sbin/exiqgrep line 56, near ") {"
syntax error at /usr/sbin/exiqgrep line 56, near ";}"
syntax error at /usr/sbin/exiqgrep line 57, near ";}"
syntax error at /usr/sbin/exiqgrep line 58, near ";}"
Execution of /usr/sbin/exiqgrep aborted due to compilation errors.
Version 4.95-4ubuntu1 uses patch 75_35-Exiqgrep-
This patch reflects upstream commit df618101a5ea15d
This upstream commit introduced a syntax error and have been fixed by a later commit 42ed39da5af8555
The patch 75_35-Exiqgrep-
Upstream bug : https:/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: exim4 4.95-4ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckR
Date: Tue Mar 29 12:37:59 2022
InstallationDate: Installed on 2022-01-06 (81 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211229)
PackageArchitec
SourcePackage: exim4
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Bryce Harrington (community): Approve
- Canonical Server packageset reviewers: Pending requested
-
Diff: 77 lines (+55/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/lp1966923-exiqgrep-syntax-error.patch (+46/-0)
debian/patches/series (+1/-0)
Changed in exim: | |
status: | Unknown → Fix Released |
tags: | added: server-todo |
Changed in exim4 (Debian): | |
status: | Unknown → New |
tags: | added: verification-done-jammy |
Changed in exim4 (Debian): | |
status: | New → Fix Released |
The original author of this comment is <email address hidden>.
If exiqgrep is invoked with -r or -f but without specifying a regular
expression - e.g. like
exiqgrep -i -r | xargs exim -Mrm
all enqueued are deleted.
Help output states
Selection criteria:
-f <regexp> Match sender address sender (field is "< >" wrapped)
...
which indicates that <regexp> is a required criteria.
I presume the absence of <regexp> is treated as an empty regex, matching
everything - but I would consider this a bug, or at least unexpected behaviour.
Needless to say the fallout of discovering this was somewhat significant. User
error, yes, but not immediately obvious.