[
https://issues.apache.org/jira/browse/JAMES-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier resolved JAMES-4006.
---------------------------------
Resolution: Fixed
https://github.com/apache/james-project/pull/2034 fixed this
> Bouncer should pass DSN to bounce processor
> -------------------------------------------
>
> Key: JAMES-4006
> URL: https://issues.apache.org/jira/browse/JAMES-4006
> Project: James Server
> Issue Type: Bug
> Components: Matchers/Mailets (bundled)
> Affects Versions: master, 3.8.1
> Reporter: Karsten Otto
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Bouncer utility currently ignores all mails without a regular sender
> address, which includes the null sender <> as used by DSNs. This is correct
> when bouncing via the mailet context, i.e. generating a bounce mail from the
> original. However, when there is a specified bounce processor, this should
> get the original mail as it is. So in this case the Bouncer must _not_ ignore
> null sender mails.
> Background: I use the bounce processor to handle temporary delivery failures,
> by storing them in a mail repository, and reprocessing them periodically via
> Webadmin. Obviously I would like to handle DSNs in the same manner, but
> currently they get dropped after the first failure.
> With this change, other use cases will have to handle null sender mails in
> the bounce processor if necessary, e.g. via the IsNullSender matcher. Note
> that the Bounce mailet as a likely candidate already ignores null sender
> mails by default, without any additional configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
