[exim-dev] [Bug 2013] Bounce message missing Diagnositic-Code for unrouteable addresses

[admin]

https://bugs.exim.org/show_bug.cgi?id=2013

Jeremy Harris  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Jeremy Harris  ---
I agree that a disgnostic-type of "smtp" would not be appropriate, since the
processing in Exim has not gotten as far as an SMTP connection. I just checked
the registry (at https://www.ietf.org/assignments/dsn-types/dsn-types.txt) and
there is no other type defined.  We could define an experimental type (X-foo
style), though I think I've see that practice deprecated in some other context,
recently.  I don't know what O365 would do with such.

You could try building with EXPERIMENTAL_DSN_INFO to see if O365 make any of
the
additional information then added to the DSN visible.

In the meantime, rejected.

-- 
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/ ##

[exim-dev] [Bug 2013] Bounce message missing Diagnositic-Code for unrouteable addresses

[admin]

https://bugs.exim.org/show_bug.cgi?id=2013

Wolfgang Breyha  changed:

   What|Removed |Added

 CC||wbre...@gmx.net

--- Comment #2 from Wolfgang Breyha  ---
According to RFC the Diagnostic-Code Field is optional.

Since the addr->user_message does not contain a SMTP return code the only
diagnostic-type defined in the IANA registry "smtp" is not appropriate IMO (see
RFC3464:2.1.2b).

In absence of any other diagnostic-type I decided to stick to the "optional"
part of the RFC.

-- 
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/ ##

[exim-dev] [Bug 2013] Bounce message missing Diagnositic-Code for unrouteable addresses

[admin]

https://bugs.exim.org/show_bug.cgi?id=2013

--- Comment #1 from Alexandru Chirila  ---
Created attachment 969
  --> https://bugs.exim.org/attachment.cgi?id=969=edit
Add support the Diagnostic-Code in bounces for unroutable addresses

Proposed patch for adding support the Diagnostic-Code for unroutable addresses.
The `print_dsn_diagnostic_code` function has been adjusted to push the correct
value for the code, and then called when the bounce is generated called
regardless of the value for the host used. 

It seems that function claimed in the documentation it already does this, but
the actual implementation doesn't? 


If af_pass_message is true
and addr->message is set it uses the remote host answer. if not
addr->user_message
is used instead if available.


-- 
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/ ##