[
https://issues.apache.org/jira/browse/JAMES-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243007#comment-17243007
]
Karsten Otto commented on JAMES-3431:
-------------------------------------
I believe variant 2 (Re-implement DSNParameters mapping) would be the best
solution to get the DSN feature done with minimal impact on the general code
base.
Variant 4 (remove Java serialization) seems like cleaner solution overall, but
with a wide impact on the James code base, and a high potential for unexpected
difficulties. Seems more like a long term strategy.
Maybe go for variant 2 for now, with an option to re-visit it at a later date,
once there is a viable basis for it from variant 4?
> 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:<[email protected]> RET=HDRS ENVID=QQ314159
> RCPT TO:<[email protected]> NOTIFY=SUCCESS,FAILURE,DELAY
> ORCPT=rfc822;[email protected]
> RCPT TO:<[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
