[ 
https://issues.apache.org/jira/browse/JAMES-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220640#comment-17220640
 ] 

Benoit Tellier commented on JAMES-3431:
---------------------------------------

Hello Otto.

Thanks for the report, this seems very interesting.

We need to cary over these parameters from the SMTP server stack through the 
mailetcontainer into RemoteDelivery. The way I would see to do it is:
 - Either to modify the Mail object in order to modify the recipient property, 
in order to take parameters into account, but this is a breaking change in one 
of our core APIs.
 - Or a mail attribute could be set up, for each recipient.

Regarding "remote delivery", SMTPTransport seems to handle DSN extension, 
`mail.smtp.dsn.notify` configure it server wide. I'm however unsure we could 
get this working in a MX forwarding context (as this is a configured value). 
Subclassing SMTPTransport seems brittle, getting rid of javax.mail not doable 
quickly. Would configuring this at the server level help your use case?

And of course James needs to comply to DSN specification as you mentionned: 
https://issues.apache.org/jira/browse/JAMES-362 


> 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

Reply via email to