E.S. Rosenberg via Courier-imap writes:
Thanks I hope you can make more of these errors than me... Attached the log, am excerpt: WRITE: 29 OK LSUB completed READ: NUMBER: 30 READ: ATOM: LIST READ: QUOTED_STRING: READ: QUOTED_STRING: INBOX READ: EOL WRITE: * LIST (\Marked \HasChildren) "." "INBOX" 30 OK LIST completed WRITE: 15 OK LOGIN Ok. READ: NUMBER: 16 READ: ATOM: CAPABILITY READ: EOLWRITE: * CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION ENABLE UTF8=ACCEPT16 OK CAPABILITY completed READ: NUMBER: 17 READ: ATOM: ENABLE READ: ATOM: UTF8=ACCEPT READ: EOL WRITE: * ENABLED UTF8=ACCEPT 17 OK Options enabled READ: NUMBER: 18 READ: ATOM: SELECT READ: QUOTED_STRING: INBOX READ: EOL WRITE: 18 NO Unable to open this mailbox.
There's nothing in the IMAP command log that points to an issue. But it does show that the server did log in and cd to the appropriate directory, and the error is in response to an actual attempt to read the mailbox, so this is back to a filesystem permissions issue.
As a measure of last resort, strace the IMAP process. Find the pid of the process that's listening on the IMAP port, port 143 (fuser -n tcp 143). If using imaps that's port 993. Then, attach strace to the process:
strace -s 256 -f -o /tmp/strace.log -p {pid}
You'll need to manually CTRL-C this after a failed login attempt, to stop
it. This is likely to create a large log file, but you can grep for the
error message, and then inspect what the process was doing just before
emitting the error.
pgpqFuJxEn6OZ.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
