> 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.
I reopened the JIRA issue so we know that there is a possible problem. We
better should dow
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
> 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.
Shoul
