classpath-inetlib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Classpath-inetlib] Re: IMAP and SMTP Issues


From: Chris Burdess
Subject: [Classpath-inetlib] Re: IMAP and SMTP Issues
Date: Fri, 28 May 2004 09:54:46 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry about the delay replying

Phillip Smith wrote:
The debug output shows this:

imap: > A1 CAPABILITY
imap: < * OK [CAPABILITY, IMAP4rev1, UIDPLUS, CHILDREN, NAMESPACE, THREAD=ORDEREDSUBJECT, THREAD=REFERENCES, SORT, QUOTA, AUTH=CRAM-MD5, IDLE] Courier-IMAP ready. Copyright 1998-2003 Double Precision,
 Inc.  See COPYING for distribution information.
imap: < * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 IDLE
imap: < A1 OK CAPABILITY completed

The it.next() processes the first async response which is essentially a duplicate of the second async response. I suppose I should surround it with an if (it.hasNext()) just to be safe. Whether this applies to other configurations, I don't know - but if it already isn't spec I don't know how far you want to take it.

I've had a look at the spec again and it's not particularly clear. I've changed the code to accept either possibility.

You need a very up-to-date version of GNU-Crypto, like current CVS HEAD.
It shouldn't require any configuration as such, you simply ask for a
SASL provider by name (the javamail providers ask for the first
authentication mechanism in the capabilities list).
I notice GNU-Crypto has made another release in the meantime. If it's
failing now we should try to correct it there.

I declaratively added the provider via the
security.provider.1=gnu.crypto.jce.GnuCrypto
property in my java.security file and I also tried programmatically adding it. Nothing seemed to work

I can confirm that it doesn't work for me either now, and wouldn't have worked with other JCA providers in any case. I'm still trying to find out exactly what the correct (generic) JSSE code to use is: currently it fails during the TLS handshake with a "Connection reset" exception using Sun's and IBM's providers. - -- Chris Burdess
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFAtv5W6dl1DEqHgrgRAhuIAJ9+AaurLnxZgn8aX7qKI/1ninEKTACcCnqW
lKRZ9VtFMLb82TpLg5E0U+E=
=cKQJ
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]