Should I use the same "new StringBuffer(256).append().." mechanism
found everywhere else in RemoteDelivery? I guess it's only about the
initial size of 256 characters?

And where do I have to commit the patch? james/server/branches/v2.3/
and james/server/trunk/mailets-function/?

Or does someone else want to commit?

Markus

On Tue, Apr 21, 2009 at 5:13 PM, Markus Wiederkehr (JIRA)
<[email protected]> wrote:
>
>    [ 
> https://issues.apache.org/jira/browse/JAMES-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701174#action_12701174
>  ]
>
> Markus Wiederkehr commented on JAMES-899:
> -----------------------------------------
>
> Updated patch to include the mail recipients and the detail message of the 
> MessagingException in the log message.
>
>> RemoteDelivery sends a message again and again if transport.close() throws a 
>> MessagingException
>> -----------------------------------------------------------------------------------------------
>>
>>                 Key: JAMES-899
>>                 URL: https://issues.apache.org/jira/browse/JAMES-899
>>             Project: JAMES Server
>>          Issue Type: Bug
>>    Affects Versions: 2.3.1
>>            Reporter: Markus Wiederkehr
>>            Assignee: Markus Wiederkehr
>>             Fix For: 2.3.2
>>
>>         Attachments: james-889.patch
>>
>>
>> Some mail servers close the TCP connection as soon as they have received and 
>> responded to the terminating dot of the DATA command. As a consequence 
>> JavaMail throws a MessagingException in SMTPTransport.close() and 
>> RemoteDelivery thinks it has to send the message again (and again).
>> Even though the server's behaviour is not standard compliant (see RFC 5321 
>> section 4.1.1.10.) the message should still be considered to be delivered 
>> successfully because the error occurred after the mail transaction has been 
>> completed (RFC 5321 section 3.3).
>
> --
> 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]

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

Reply via email to