This content has been marked as final. Show 5 replies
What does the protocol trace show?
Thanks for your quick reply.
Here's the trace:
It's Greek to me, but it appears everything is kosher until C:STAT S:EOF
DEBUG: setDebug: JavaMail version 1.4.5 DEBUG: getProvider() returning javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc] DEBUG POP3: mail.pop3.rsetbeforequit: false DEBUG POP3: mail.pop3.disabletop: false DEBUG POP3: mail.pop3.forgettopheaders: false DEBUG POP3: mail.pop3.cachewriteto: false DEBUG POP3: mail.pop3.filecache.enable: false DEBUG POP3: mail.pop3.keepmessagecontent: false DEBUG POP3: mail.pop3.starttls.enable: false DEBUG POP3: mail.pop3.starttls.required: false DEBUG POP3: mail.pop3.apop.enable: false DEBUG POP3: mail.pop3.disablecapa: false DEBUG POP3: connecting to host "mail.myDomain.com", port 110, isSSL false S: +OK Dovecot ready. C: CAPA S: +OK CAPA TOP UIDL RESP-CODES PIPELINING STLS USER SASL PLAIN . DEBUG POP3: PIPELINING enabled DEBUG POP3: authentication command trace suppressed DEBUG POP3: authentication command succeeded C: STAT S: EOF C: QUIT S: EOF Exception in thread "main" javax.mail.MessagingException: Open failed; nested exception is: java.io.EOFException: EOF on socket at com.sun.mail.pop3.POP3Folder.open(POP3Folder.java:228) at com.myTest.TestOpenInbox.execute(TestOpenInbox.java:26) at com.myTest.TestOpenInbox.main(TestOpenInbox.java:13) Caused by: java.io.EOFException: EOF on socket at com.sun.mail.pop3.Protocol.readResponse(Protocol.java:742) at com.sun.mail.pop3.Protocol.simpleCommand(Protocol.java:687) at com.sun.mail.pop3.Protocol.stat(Protocol.java:354) at com.sun.mail.pop3.POP3Folder.open(POP3Folder.java:203) ... 2 more
I strongly suspect it's an authentication or authorization problem, even though1 person found this helpful
the server isn't reporting an authentication failure. Try setting the session property
"mail.debug.auth" to "true". You should get all the details of the authentication
exchange, which might provide a clue as to what's wrong. (Just be careful when
posting those details here so as not to expose your password.)
It looks to me that the server is completing the authentication exchange and then
closing the connection. You should probably look in the server log files as well.
I'm logging in ok:
I should have mentioned though opening the inbox fails, it clears all the messages--Maildir/new is empty when it had messages before the attempt to open the inbox.
DEBUG POP3: PIPELINING enabled C: USER my.user S: +OK C: PASS myPassword S: +OK Logged in. C: STAT S: EOF C: QUIT S: EOF
I'll have to dig into the server logs.
Found and corrected the problem. The maillog had this:
This was a strange error because I know there was plenty of memory on the system. Did some googling and found that an index file may have been corrupted and the remedy was to delete the file. I deleted the user's Maildir directory and now it's working fine. The cur directory was huge so I'm wondering if it was just that the inbox was full.
Aug 12 01:01:13 279153-web1 dovecot: child 9328 (pop3) returned error 83 (Out of memory)