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 "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2005/09/08 15:14:37 UTC
[jira] Reopened: (JAMES-416) Upgrade to javamail-1.3.3
[ http://issues.apache.org/jira/browse/JAMES-416?page=all ]
Stefano Bagnara reopened JAMES-416:
-----------------------------------
I'm reopening this because we should downgrade to 1.3.2 before an official release.
------------------------------------------------------------------------------
Well good questions, I read your entry on the upgrade, wher you state:
"Probably only performance improvement on base64 encoding/decoding.
Most of the other changes are around IMAP (client) and we don't use it. "
So our main reason is the performance improvement in base64 handling, and this is exactly what seams broken. So I suggest reverting to JavaMail 1.3.2 until a bugfix-release from Sun is available.
--Søren
On Thursday 08 September 2005 11:25, Stefano Bagnara wrote:
> > Just saw this on the BouncyCastle mailinglist, as we provide mailets
> > using BouncyCastle we should perhaps revise upgrading to JavaMail
> > 1.3.3.
> >
> > --Søren
>
> Hi Søren,
>
> Thank you for pointing this out. What should we do?
> I haven't tested S/MIME stuff since the upgrade to javamail 1.3.3.
> Should I revert the upgrade to mail-1.3.3? Should we add a FAQ?
> Should we add a note in the config.xml just before the SMIME stuff?
>
> Stefano
>
> > Subject: [dev-crypto] warning about JavaMail 1.3.3
> > Date: Thursday 08 September 2005 00:25
> > From: David Hook <dg...@bund.com.au>
> > To: dev-crypto@bouncycastle.org
> >
> > We're not sure exactly what's happening still, but it appears that
> > on some platforms, under some circumstances, Base64 decoding, or
> > something underlying it, in JavaMail 1.3.3 breaks horribly and
> > produces data with lots of extra bytes of the value 0x00 and 0xff.
> > The upshot of this is that messages containing Base64 encoded data,
> > such as S/MIME messages will no longer work as the data stream
> > containing the encoded message has become corrupted.
> >
> > If S/MIME starts causing exceptions we recommend moving back to 1.3.2.
> Upgrade to javamail-1.3.3
> -------------------------
>
> Key: JAMES-416
> URL: http://issues.apache.org/jira/browse/JAMES-416
> Project: James
> Type: Task
> Versions: 2.3.0
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Priority: Minor
> Fix For: 2.3.0
>
> Probably only performance improvement on base64 encoding/decoding.
> Most of the other changes are around IMAP (client) and we don't use it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org