https://bugs.exim.org/show_bug.cgi?id=3026
Bug ID: 3026
Summary: -Mg option: no "cancelled by administrator" text in
bounce message, despite the doc say it will
Product: Exim
Version: 4.96
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Unfiled
Assignee: unallocated@???
Reporter: u34@???
CC: exim-dev@???
As in https://lists.exim.org/lurker/thread/20230920.211646.e11c6588.en.html :
An earlier, less detailed, version is at
https://lists.exim.org/lurker/message/20230819.231448.32a47d0e.en.html .
There is a mismatch between the documentation and the actual behavior of the
-Mg command line option. No "cancelled by administrator" text in bounce
message, despite the doc say there will be.
Breaking lines for readability, but otherwise quoting
https://exim.org/exim-html-current/doc/html/spec_html/ch-the_exim_command_line.html#SECID39
-Mg <message id> <message id> ...
This option requests Exim to give up trying to deliver the listed
messages, including any that are frozen. However, if any of the
messages are active, their status is not altered. For non-bounce
messages, a delivery error message is sent to the sender, containing
the text “cancelled by administrator”. Bounce messages are just
discarded. This option can be used only by an admin user.
How to reproduce?
In order to reproduce, there should be a mail server, supposedly acting as a
smart host for an exim instance. The mail server is only supposedly acting as a
smart host for the exim instance because it deliberately does not get messages
to deliver. There fore, there is no need to configure the mail server to act as
a smart host. What is important, at least in order to reproduce the problem the
way I confronted it, is to somehow make the exim client to defer sending
messages to the smart host. For example, by one of
1) Have a firewall block the connection between the two.
2) Have the mail server presents a certificate which the exim client refuses to
accept. Such as a self signed certificate. Which leads to the exim client
log
defer (-37) ...: TLS session: (SSL_connect): error:0A000086:SSL
routines::certificate verify failed
So far there is a smart host for an exim client which the exim client defer
sending messages to. Now for the exim client. For that, I used exim with the
default configuration. That is, a copy of the file at
src/src/configure.default. Within the config file of the client, I made only a
single change. Which is to uncomment the macro for ROUTER_SMRTHOST, and point
it to the mail server. After activating the client new configuration, I am
sending an email message with the exim client. The recipient is chosen such
that the message should be delivered by the smart host. The message won't be
sent to the smart host because the exim client will defer it. So the exim
client would keep retrying. At a random time between retries, an administrator
of the exim client, root in my case, should cancel the delivery with a -Mg
command line option. And here is the problem. No "cancelled by administrator"
text appears at the bounce message. The summary of the log in the exim client,
when a bad smart host certificate is used, is
msg_id <= P=local
msg_id SSL verify error
msg_id == R=smarthost T=smarthost_smtp defer (-37) : TLS session:
(SSL_connect): error:0A000086:SSL routines::certificate verify failed
msg_id retry time not reached
msg_id cancelled by root
bounce_id <= <> R=orig_id
bounce_id => sender
bounce_id Completed
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
