On Sat, May 14, 2011 at 02:03:56PM -0700, Earl Killian wrote: > Thanks for the suggestion. I tried it, and this looks relevant: > WRITE: + entering idle mode > READ: NUMBER: 8 > READ: ATOM: STATUS > READ: QUOTED_STRING: INBOX.Notes > READ: LPAREN > READ: ATOM: UIDNEXT > READ: ATOM: MESSAGES > READ: ATOM: UNSEEN > READ: ATOM: RECENT > READ: RPAREN > READ: EOL > WRITE: 8 NO [ALERT] STATUS failed > READ: NUMBER: 9 > READ: ATOM: STATUS > READ: QUOTED_STRING: INBOX.Archives > READ: LPAREN > READ: ATOM: UIDNEXT > READ: ATOM: MESSAGES > READ: ATOM: UNSEEN > READ: ATOM: RECENT > READ: RPAREN > READ: EOL > WRITE: 9 NO [ALERT] STATUS failed > (repeated many times)
Judging by the above, it does it once for each mailbox? I have (a long time ago) modified the couriertcpd command line so that it starts imapd under strace, and redirects strace's output to a file. Sorry I can't give you an exact recipe for that. But it would show you exactly what I/O the process is doing, and exactly which operation fails. If you can replicate the above error manually, i.e. by telnetting to port 143 (*) and issuing the same commands as your client and getting the same error responses, then you can open a new connection, find the imapd pid using ps, attach strace to it (strace -p <pid>), and then issue the commands. Regards, Brian. (*) or: openssl s_client -connect x.x.x.x:993 ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
