You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Jean Marc (JIRA)" <se...@james.apache.org> on 2008/11/17 19:39:44 UTC

[jira] Created: (JAMES-881) ValidSentAddresses not removed from recipients list on SendFailedException

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.1, 2.3.0
            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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Commented: (JAMES-881) ValidSentAddresses not removed from recipients list on SendFailedException

Posted by "Jean Marc (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650208#action_12650208 ] 

Jean Marc commented on JAMES-881:
---------------------------------

This occurs when sendpartial=true. If sendpartial=false, none of the recipients of such domains will receive the message since James will retry until maxretries is reached and will always receive a 452. 

> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[jira] Commented: (JAMES-881) ValidSentAddresses not removed from recipients list on SendFailedException

Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
    [ https://issues.apache.org/jira/browse/JAMES-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648545#action_12648545 ] 

Stefano Bagnara commented on JAMES-881:
---------------------------------------

Are you aware of the "sendpartial" configuration for the RemoteDelivery and its meaning?
Are you describing the behaviour for sendpartial=false or sendpartial=true ?

> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org