Maybe the _INBOX_.PNM file got corrupted: We noticed that if this file somehow becomes empty (0-Byte file), Mercury can never recover from it and listing the contents of the inbox gets inconsistent results.

If _INBOX_.PNM is empty, just delete the file, it should be re-created next time you connect to imap.

Same goes for other PNM files for mailfolders. Be careful though to not confuse these with the PMM files: PMMs contain the mails in the mailfolder proper. The PNM only contains a unique identifier for all e-mails in the folder and a flag whether the mails is deleted or not.

Greetings

Markus

Hello All,

    I am trying to move my Pegasus account to a Mercury + Pegasus IMAP account.  I installed Mercury over a copy my Pegasus directory.  But I can't access my mail through IMAP.  It looks like I'm getting stuck on some FETCH commands.  I tried to fetch using telnet to port 143, and the result was inconsistent.  So I created a new account in Mercury called merctest, and copied some email over into it using Pegasus IMAP. Copying into the folder worked OK, and I can see that Mercury has new .CNM files in its merctest directory.  But when I try to open "Inbox", which claims to have the 8 messages, it takes a long time and the folder comes up empty.

I am going to try a clean install of Mercury next.  Any ideas on what else I should do instead?

Here's a trace from Mercury.  

15:00:45.750 >> 0069 * OK testPmail.midlabs.com IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
15:00:45.750 << 0032 A1 LOGIN "merctest" "merctest"\0D\0A
15:00:45.750 >> 0024 A1 OK LOGIN completed.\0D\0A
15:00:45.765 << 0019 A2 SELECT "INBOX"\0D\0A
15:00:45.765 >> 0012 * 8 EXISTS\0D\0A
15:00:45.765 >> 0012 * 0 RECENT\0D\0A
15:00:45.765 >> 0043 * FLAGS (\\Deleted \\Draft \\Seen \\Answered)\0D\0A
15:00:45.765 >> 0044 * OK [UIDVALIDITY 1310735004] UID Validity\0D\0A
15:00:45.765 >> 0037 * OK [UIDNEXT 9] Predicted next UID\0D\0A
15:00:45.765 >> 0080 * OK [PERMANENTFLAGS (\\Deleted \\Draft \\Seen \\Answered)] Settable message flags\0D\0A
15:00:45.765 >> 0038 A2 OK [READ-WRITE] SELECT completed.\0D\0A
15:00:45.781 << 0217 A3 FETCH 1:* (FLAGS UID X-COLOUR RFC822.SIZE BODY.PEEK[HEADER.FIELDS (FROM SUBJECT TO DATE X-PMUUE MIME-VERSION CONTENT-TYPE RESENT-FROM PRIORITY X-PMENC X-CONFIRM-READING-TO X-PM-ENCRYPTOR X-CS X-PM-CIRCULATE-TO)])\0D\0A
15:01:15.781 8: Socket read timeout.
15:01:19.281 << 0010 A4 CLOSE\0D\0A
15:01:19.281 >> 0024 A4 OK CLOSE completed.\0D\0A

 Thanks in advance for any help!!

Andrew

Unless the disk is broken there is very little risk that the Mercury installation is corrupted. You could try to clear the cache files, though: stop Mercury, delete all .cac files in the mailbox folder, and restart Mercury.

Other than that make sure there is nothing that interferes with Mercury's access to mailbox files or intercepts IMAP network traffic (like antivirus programs), and that there is just one user accessing the mailbox.

/Rolf