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

Norman Maurer commented on JAMES-881:
-------------------------------------

I tried to reproduce it without any luck... anymore details you could give ?

> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to