[
https://issues.apache.org/jira/browse/JAMES-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136710#comment-17136710
]
Rémi Kowalski commented on JAMES-3210:
--------------------------------------
The return-path should not be used in DSN usage.
REGARDING RFC 3834 "Recommendations for Automatic Responses to Electronic Mail"
which specify the usage of the return-path field was quoted :
3.2.1. Use of DSNs and MDNs instead of this specification
> In general, it is appropriate to use Delivery Status Notifications
> (DSNs) for responses that are generated by the mail transport system
> as a result of attempts to relay, forward, or deliver mail, and only
> when the purpose of that response is to provide the sender of the
> subject message with information about the status of that mail
> delivery. For instance, a "virus scanner" which is activated by a
> mail delivery process to filter harmful content prior to delivery,
> could return a DSN with the Action field set to "failed" with a
> Status code of 5.7.1 (Delivery not authorized, message refused) if
> the entire message was not delivered due to security reasons; or it
> could return a DSN with the Action field set to "relayed" or
> "delivered" (as appropriate) with a Status code set to 2.6.4
> (conversion with loss performed) if the message was relayed or
> delivered with the presumably harmful content removed. The DSN
> specification [I2.RFC3464], rather than this document, governs the
> generation and format of DSNs.
And the RFC 3464 specifying the DSN :
> The DSN MUST be addressed (in both the message header and the
> transport envelope) to the return address from the transport envelope
> which accompanied the original message for which the DSN was
> generated. (For a message that arrived via SMTP, the envelope return
> address appears in the MAIL FROM command.)
The DOD should be updated to add integration test validating that the DSN is
sent to the sender (in envelope and headers)
the PR verifying this : https://github.com/linagora/james-project/pull/3446
> Handle Return-Path header in DSNBounce mailet
> ---------------------------------------------
>
> Key: JAMES-3210
> URL: https://issues.apache.org/jira/browse/JAMES-3210
> Project: James Server
> Issue Type: Bug
> Components: Matchers/Mailets (bundled)
> Affects Versions: 3.5.0
> Reporter: Rémi Kowalski
> Priority: Major
>
> ```
> At the origin of the complain:
> ```
> This message was created automatically by mail delivery software.
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@eu-west-1.amazonses.com
> (generated from
> SRS0=78Gj=WP=eu-west-1.amazonses.com=0102016ca8bd7b6d-b28772f6-6c71-4676-8834-c48740efb2a8-000...@ik2.com)
> host feedback-smtp.eu-west-1.amazonses.com [54.239.37.176]
> SMTP error from remote mail server after end of data:
> 554 DSN is not RFC 3464 compliant. MSGID: (FleYRCEogpaDtH6q8Ml2-1):
> The DSN MUST be addressed (in both the message header and the transport
> envelope) to the return address from the transport envelope which accompanied
> the original message for which the DSN was generated.
> https://tools.ietf.org/html/rfc3464
> ```
> DOD:
> handle the Return-Path header in the DSNBounce mailet and add an integration
> test
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
