[
https://issues.apache.org/jira/browse/JAMES-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220707#comment-17220707
]
Karsten Otto commented on JAMES-3431:
-------------------------------------
> Would configuring this at the server level help your use case?
Unfortunately not. The use case is a form of "registered mail" scenario, where
a user requires notification once certain important mails reach the recipients
inbox (NOTIFY=SUCCESS). But in general they only care about delivery failure
(NOTIFY=FAILURE) and don't want any confirmations for each and every mail.
Looking at the source code of SMTPTransport, mail.smtp.dsn.notify would set the
NOTIFY option to a fixed value regardless, which is not helpful.
However, I noticed that SMTPTransport actually can use the SMTPMessage subclass
of MimeMessage to specify the NOTIFY and RET options, and possibly even ENVID
via setMailExtension. Maybe this could be a backwards compatible way to make
DSN work, without abandoning javax.mail? Of course there are still all the
other issues regarding mail attributes and SMTP stack.
> 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
