I was trying to diagnose a potential problem with an IMAP account that has lost all its INBOX. emails twice within a few days and I needed to have a log of commands from the clients so that I can rule-out the possibility of a user deleting the messages.
With the help of the list I learned about the IMAPDEBUGFILE directive and I used it to have more info about what's happening. The problem is that IMAPDEBUGFILE is on one hand too verbose (to the extend that it is even writting to the log whole copies of emails transmitted) and on the other hand it is missing timestamps. So my plan of letting it log until mails get lost again and then examining the logs around the time the user noticed the fact is not practical. What would you propose to diagnose such a problem? The only work around I can think of is to refresh my programming skills and write a small python script that will periodicaly (say every 15min) parse the output log of IMAPDEBUGFILE, keeping only delete commands and writing the result with a time stamp. Any other ideas are welcome (also any link to a page explaining the contents of IMAPDEBUGFILE could be helpfull since it will save me a lot of time in testing) Nick Demou ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
