[
https://issues.apache.org/jira/browse/JAMES-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285634#comment-17285634
]
ASF GitHub Bot commented on JAMES-3431:
---------------------------------------
chibenwa opened a new pull request #299:
URL: https://github.com/apache/james-project/pull/299
Otto, Karsten Andreas reported the following issues so far regarding DSN
```
1. When I send a mail to an unknown user, the DSN report (part 1) has no
text after "Error message:". There is a comment in the mail MailDispatcher
class that might explain it?
// In order for this server to meet the requirements of the SMTP
// specification, mails on the ERROR processor must be returned to
// the sender. Note that this email doesn't include any details
// regarding the details of the failure(s).
// In the future we may wish to address this.
Anyways, this is no big issue for us, as we can describe the problem in
the <messageString>. But the empty text is confusing, I thought it to be a bug
at first.
=> Please change the report generation to just hide the "Error message:"
part if there is no error message to report.
2. I see a strange date format in the DSN report (part 2), e.g.
Last-Attempt-Date: Mon, 15 Feb 2021 15:45:20 XXXXX (CET)
According to rfc3464#section-2.3.7 this header must use the numeric
timezone format (+hh:mm/-hh:mm). Does the XXXXX serve any special purpose?
=> Please fix this date format here to comply with the RFC.
3. We would also like to have the Arrival-Date (rfc3464#section-2.2.5)
header in the DSN report (part 2) as well. In the past I found it a useful
diagnostic in conjunction with Last-Attempt-Date, especially with delayed
delivery cases. Does James per chance already record the timestamp on each
incoming mail?
=> Please add the Arrival-Date header to the DSN report. Record the
necessary timestamp on mail arrival if James does not have this data already.
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Relay DSN options on RemoteDelivery
> -----------------------------------
>
> Key: JAMES-3431
> URL: https://issues.apache.org/jira/browse/JAMES-3431
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery, SMTPServer
> Affects Versions: 3.5.0
> Reporter: Karsten Otto
> Priority: Major
>
> Since James claims to support the DSN SMTP extension, it may receive a mail
> submission according to [RFC 3461|https://tools.ietf.org/html/rfc3461]:
> {code:java}
> MAIL FROM:<al...@example.org> RET=HDRS ENVID=QQ314159
> RCPT TO:<d...@ivory.edu> NOTIFY=SUCCESS,FAILURE,DELAY
> ORCPT=rfc822;d...@ivory.edu
> RCPT TO:<f...@bombs.af.mil> NOTIFY=NEVER{code}
> In this case James should
> * remember the given DSN options (NOTIFY, ORCPT, RET, ENVID) for each
> recipient, and
> * provide the same options when relaying the mail to remote servers via the
> RemoteDelivery mailet.
> (The DSN options should be accessible to other interested mailets as well,
> e.g. for bounce processing.)
> Possibly related issues:
> https://issues.apache.org/jira/browse/JAMES-322
> https://issues.apache.org/jira/browse/JAMES-362
>
--
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
