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 "Oleg Kalnichevski (JIRA)" <se...@james.apache.org> on 2008/11/04 15:10:44 UTC

[jira] Commented: (MIME4J-84) Base64OutputStream and trailing CRLFs

    [ https://issues.apache.org/jira/browse/MIME4J-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644969#action_12644969 ] 

Oleg Kalnichevski commented on MIME4J-84:
-----------------------------------------

The patch looks good to me. I'll go ahead and commit it if I hear no complaints.

Oleg

> Base64OutputStream and trailing CRLFs
> -------------------------------------
>
>                 Key: MIME4J-84
>                 URL: https://issues.apache.org/jira/browse/MIME4J-84
>             Project: JAMES Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Stefano Bagnara
>             Fix For: 0.6
>
>         Attachments: mime4j-base64-one-lf-testmsgs.zip, mime4j-base64-one-lf.patch
>
>
> Markus said:
> ----
> the current implementation adds two line feed at the end of a
> base64 encoded block. In a multipart/mixed message this leads to two
> empty lines between a base64 block and the following boundary string.
> This is only a minor issue but it is not the way it should be.
> Here is a patch that would resolve the issue.
> ----
> PS: Markus discussed this issue with me via email. I don't have time to check it now, so I create this JIRA to not loose it.

-- 
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