[
https://issues.apache.org/jira/browse/JAMES-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-881.
--------------------------------
Resolution: Won't Fix
James 2.3 is unmaintained, end of life.
Feel free to reopen if work is planned on this.
> ValidSentAddresses not removed from recipients list on SendFailedException
> --------------------------------------------------------------------------
>
> Key: JAMES-881
> URL: https://issues.apache.org/jira/browse/JAMES-881
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery
> Affects Versions: 2.3.0, 2.3.1
> Reporter: Jean Marc
> Priority: Major
>
> In the deliver() loop of RemoteDelivery, when a SendFailedException is
> received as a "452 Too Many Recipients" from a remote server, the processing
> continues to the next available server regardless of the ValidSentAddresses,
> and the whole list of original recipients is sent again to the next server of
> the domain, creating multiple duplicate emails in the recipients accounts.
> The typical example is Yahoo, which accepts a variable number of recipients
> per email from a specific server according to their internal business rules
> (bulk settings, SPF, reverse DNS, etc). For example, Yahoo servers receive a
> mail for 69 addresses, accepts the email for the first 30, then stops
> processing the mail and returns code=452 and the list of valid sent/unsent
> addresses. James logs the list of valid sent, and continues to the next mx
> record, sending the email to the 69 recipients again.
> Should the code 452 be treated as an error code, or RemoteDelivery remove the
> validSent from the list before 'continu'ing to the next server ?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
