OK - sorry folks I think this was a red herring. I had a single Android phone with two mail clients polling simultaniously (Vanilla Android and K9) stopped one and crashing stopped now stable again

I'll run Mbxmaint and the  tip is useful thanks - I wondered before why mbxmaint could run with no apparent success

thanks

Ron

I've run mercury for over a decade at home with no problems. On install of 4.73 I've found it restarts repeatedly. Anyone else? My gut feeling is it may be the IMAP bit. Any logs I should look at?

Previous editions did no exhibit this behaviour

> I've run mercury for over a decade at home with no problems. On install of 4.73 I've found it restarts repeatedly. Anyone else? My gut
> feeling is it may be the IMAP bit. Any logs I should look at?

Could be but if it is crashing there should be a directory with the messages in the queue at the time of the crash.

Mercury 4.73 is in my experience actually more stable in IMAP handling than previous versions. You could try to remove all files with the extension .cac from the mailbox folders to clear IMAP and POP3 caches, though (with Mercury closed down while doing it).

Other than that you may need to update daemons to newer version if you use any.

/Rolf  

Mercury IMAP is not very forgiving of corrupt mailboxes, if it tries to access a corrupt mailbox file (PMM or PMI), Mercury often crashes. Alas, it is also not very forthcoming to tell which mailbox operation caused the crash, i.e. you usually don't even know which user was active at the time of the crash.

A first step to find and fix the corrupted entries would be to run mbxmaint.exe on all mailboxes to check for index corruption. This does not find certain errors, namely corrupted header in the PMM file. You have to find them yourself, probably using a hex editor. But a good place to look if something is fishy is the HIERARCH.PM file: This is a list of all folders in the mailbox. There should be one line per folder, if you see strange multiline entries and/or gibberish, you have a PMM file with a corrupt header (i.e. the first 128 bytes). You have to first remove this file and then try to salvage the contents, for example by reconstructing the header with a hex editor. I can give you some tips for this if you like. And you have to remove the gibberish from the HIERARCH.PM file.

Greetings

Markus