[
https://issues.apache.org/jira/browse/JAMES-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330234#comment-17330234
]
Jean Helou commented on JAMES-3569:
-----------------------------------
Hmm I don't know, the processing for rewrites to local addresses vs remote
addresses is really very different :
the RewriteTableProcessors splits local adresses from remote addresses, it sets
the local addresses on the existing email and creates a new mail with the
remote recipients which it then sends through the mailContext. this behaviour
is explicitely asserted in the processor tests so it seems to be intentional
but I can't really tell why it is/was necessary ...
The fix we made with [~matthieu] (PR incoming) doesn't change this behaviour
(maybe matthieu has a better undertanding why it was necessary)
(our fix also contains a bit of boyscouting and removes mockito usage in the
processor test along with adding an assertion that the attributes are not lost )
> RecipientRewriteTable sometimes drops attributes from emails
> ------------------------------------------------------------
>
> Key: JAMES-3569
> URL: https://issues.apache.org/jira/browse/JAMES-3569
> Project: James Server
> Issue Type: Bug
> Components: SMTPServer
> Affects Versions: 3.6.0
> Reporter: Jean Helou
> Priority: Major
>
> When a mail has a recipient with a mapping to a remote email address,
> RecipientRewriteTable creates a new mail and copies over a few fields.
> Unfortunately it doesn't copy all the fields and in particular it drops the
> mail attributes that have been computed by the pipeline up to this point.
> For recipients which are rewritten to a local address there is no information
> loss.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
