https://bugs.exim.org/show_bug.cgi?id=2826
Bug ID: 2826
Summary: redirect router looses DSN track
Product: Exim
Version: 4.94
Hardware: x86
OS: All
Status: NEW
Severity: wishlist
Priority: medium
Component: Routing
Assignee: unalloca...@exim.org
Reporter: ar...@maven.pl
CC: exim-dev@exim.org
There are two machines. MX and MBOX.
MX gets mail to dest-u...@dest-domain.com over SMTP with DSN request
RCPT TO:<dest-u...@dest-domain.com> NOTIFY=SUCCESS,FAILURE,DELAY
MX then does one or more redirects:
driver = redirect
data = ${lookup mysql{SELECT physical_mailbox FROM WHERE ... AND
login='${quote_mysql:$local_part}' AND vhost = '${quote_mysql:$domain}'}}
or later (this one could be replaced with manualrouter probably)
driver = redirect
data = $local_part@${lookup mysql{ROUTE_HOST-which-returns-MBOX}}
and the mail gets delivered to (DSN capable) MBOX. Unfortunately it is
delivered without any DSN RCPT TO options passed at smtp time. Just plain RCPT.
According to
https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_redirect_router.html
"If success DSNs have been requested redirection triggers one and the DSN
options are not passed any further."
so any redirect that will succeed will cause loosing all DSN flags and final
MBOX server won't get DSN request and won't be able to generate more accurate
DSN return message.
This feature request is about changing the way DSN works with such routers, so
dsn flags are not lost and used later in final smtp connection (if possible)
etc.
Current behaviour looses usable data and causes DSN responses to be much less
accurate that they could be.
Don't know if this affects other types of routers.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
