IMAP4 isOpen and POP3 ERR

Question

Hi,
I was checking the isOpen method of the IMAPFolder and I saw that the method return the opened field whatever happen during the keepConnectionAlive method. Is this an expected behavior since this method may return true even if the server side socket has been closed? For example, a successful connection has been done and the server closes the connection for any reason, the client calls the isOpen method and the noop method throws an exception.
Another thing, what is the reason behind hiding the POP3 errors? The server can return ERR but the API simply ignore them and return the default value. This is quite unexpected since the IMAP4 does throw exceptions. Sorry if this has already been asked but I could not find the response using the search function.
One last thing, I've seen several mail bugged which are told to be encoded in ISO-8859-1 but are encoded in Cp1252. I've used the javamail.charset.map to work around those mails but I was wondering if this should be not added by default.
Thanks,
Sylvain

Answer 1

I was checking the isOpen method of the IMAPFolder and I saw that the method return the opened field whatever happen during the keepConnectionAlive method. Is this an expected behavior since this method may return true even if the server side socket has been closed? For example, a successful connection has been done and the server closes the connection for any reason, the client calls the isOpen method and the noop method throws an exception.The callback method that processes the response from the server will clear the open flag if the connection fails.
Another thing, what is the reason behind hiding the POP3 errors? The server can return ERR but the API simply ignore them and return the default value. This is quite unexpected since the IMAP4 does throw exceptions. Sorry if this has already been asked but I could not find the response using the search function.Most of the POP3 commands are so simple that they don't typically return ERR. If the server is working properly
it will return the correct result to a valid command. Still, there's at least one place where an error should be
reflected to the caller, and I'll fix that. In what specific cases are you seeing ERR returned?
One last thing, I've seen several mail bugged which are told to be encoded in ISO-8859-1 but are encoded in Cp1252. I've used the javamail.charset.map to work around those mails but I was wondering if this should be not added by default.javamail.charset was created to work around the fact that old versions of the JDK didn't know all the standard
MIME charset names. "cp1252" doesn't seem to be a standard [MIME charset|http://www.iana.org/assignments/character-sets] name. If the message lists the
charset as "cp1252", use the technique in the [JavaMail FAQ|http://java.sun.com/products/javamail/FAQ.html#unsupen] to handle it. If the message lists the charset as
iso-8859-1 but really is encoded in cp1252 format (whatever that is), please report that bug to the owner of the
program that created the message. How you detect and handle incorrectly encoded data is up to you.