Help → IMAP Folder Problem
On repeated occasions, we've discovered that moving or renaming a folder in Lotus Notes causes POPFile to no longer be able to see that folder. It tries to classify as normal and move appropriate email messages into the folder in question, but it can't find the folder.
In the case of renaming a folder, POPFile is simply no longer able to connect to the IMAP server at all, despite the information being correct. Below is a dump of the log file, with server names removed for security.
2008/10/6 07:46:49 200: imap: 1522: Could not copy message (0)! 2008/10/6 07:46:49 200: imap: 703: Message was classified as issues. 2008/10/6 07:47:19 200: imap: 932: Connection timed out for xxxxxxxxxx.xx.xxxx.xxx:993 2008/10/6 07:47:19 200: imap: 451: Could not CONNECT for folder CURRENT INCOMING. 2008/10/6 07:47:49 200: imap: 932: Connection timed out for xxxxxxxxxx.xx.xxxx.xxx:993 (above two messages repeat several times) 2008/10/6 07:56:19 200: imap: 932: Connection timed out for xxxxxxxxxx.xx.xxxx.xxx:993 2008/10/6 07:56:19 200: imap: 451: Could not CONNECT for folder CURRENT INCOMING. 2008/10/6 08:00:11 3428: bayes: 733: Attempting to connect to dbi:SQLite:dbname=C:\DOCUME~1\popfile\APPLIC~1\POPFile/popfile.db (1) 2008/10/6 08:00:11 3428: bayes: 739: Using SQLite library version 2.8.12 2008/10/6 08:00:14 3428: imap: 936: Connected to xxxxxxxxxx.xx.xxxx.xxx:993 timeout 90 2008/10/6 08:00:15 3428: imap: 936: Connected to xxxxxxxxxx.xx.xxxx.xxx:993 timeout 90 2008/10/6 08:00:15 3428: imap: 1191: >> A00001 NO SELECT failure, cannot select mailbox: Invalid or nonexistent document[0d][0a] 2008/10/6 08:00:15 3428: imap: 433: Could not SELECT folder CURRENT INCOMING. 2008/10/6 08:00:15 3428: imap: 936: Connected to xxxxxxxxxx.xx.xxxx.xxx:993 timeout 90 (above message repeats several times) 2008/10/6 08:00:48 3428: imap: 1191: >> A00001 NO SELECT failure, cannot select mailbox: Invalid or nonexistent document[0d][0a] 2008/10/6 08:00:48 3428: imap: 433: Could not SELECT folder CURRENT INCOMING. 2008/10/6 08:01:18 3428: imap: 936: Connected to xxxxxxxxxx.xx.xxxx.xxx:993 timeout 90 (above three messages repeat several times)
-
Message #538
Thank you. This is very nice test case for our test suite. I never thought too much about what happens when people rename their IMAP folders.
What version of POPFile are you using? From the log snippet it seems that it's not the most recent one?
Manni
manni10/06/08 15:27:39 -
-
Message #539
The problem with moving folders occurs in version v0.22.4. The renaming problem occurs in v1.0.1.
We're presently running v0.22.4 in production, though we're in the process of upgrading to v1.0.1 in an attempt to solve this very problem. However, as there is still a similar folder issue in v1.0.1, I doubt the upgrade will solve the problem.
I can provide a more detailed log if necessary.
Riceman10/06/08 15:43:40 -
-
Message #540
I also doubt that upgrading now will solve the issue. This is clearly a bug in POPFile that I hope I will be able to fix soon.
I'll post here when I have a fix.
manni10/06/08 15:50:35 -
-
Message #558
Any word on the status of the fix?
Riceman10/28/08 16:39:55 -
-
Message #567
Sorry, but I was quite busy in the recent weeks.
I have now tested what the current version of POPFile will do when an IMAP folder is renamed. I have to admit that I was a bit too sceptical about POPFile's error handling. Of course, when a folder is renamed, POPFile is no longer able to check the folder and you have to re-configure the IMAP module. But the error is handled gracefuly and you can re-configure POPFile without any trouble or having to restart it.
The same can be said about a situation in which POPFile tries to move a message to a folder that was just renamed.
So, in short, I cannot see any problems here. Sorry
Manni
manni11/02/08 13:13:10
-
-
Message #541
Thank you, I appreciate it greatly!
Riceman10/06/08 15:51:49
-
-
-