james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara" <apa...@bago.org>
Subject Re: [dev-crypto] warning about JavaMail 1.3.3
Date Thu, 08 Sep 2005 09:25:57 GMT
> 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?


> Subject: [dev-crypto] warning about JavaMail 1.3.3
> Date: Thursday 08 September 2005 00:25
> From: David Hook <dgh@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.

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message