MailStore – Archiving from MDaemon mail server returns error message “Unable to parse server response”
Summary
Cause
Resolution
- Open the MDaemon user interface > Accounts > User > Note the path to the user’s mailbox.
- Open Windows Explorer to the path identified above.
- Navigate into the folder structure to find the folder in question. Folders will be shown on disk with a .IMAP extension.
- Rename or remove the IMAP.MRK file.
MailStore will now be able to archive messages from this folder, and IMAP clients will re-download the contents with all messages flag reset as noted above.
Create a new folder and move all messages. This approach requires more manual steps, but preserves flags on messages. Note that while you can perform these steps using an IMAP client, it is best to close all IMAP clients and use MDaemon’s webmail interface to avoid conflicts.
- Login to the user’s mailbox using MDaemon’s webmail interface.
- Open Options > Folders, find the problematic folder.
- Create a new temporary folder to replace the original folder.
- Move any subfolders from below the problematic folder to be subfolders of the temporary folder.
- Return to the message list.
- Move all messages from the problem folder to the temporary folder.
- Go to Options > Folders.
- Delete “problemfolder”, and rename “problemfolder-new” back to “problemfolder”.
- MailStore will now be able to archive messages from the folder in question.
Additional Information
MDaemon Email Server already resolved the bug that caused the incorrect UID value to be set on newly created folders, but if an existing folder has UID 0 it must be corrected manually.
Even on versions of MDaemon where it is possible to create folders with UID 0, the steps described in this article will resolve the issue.
To confirm if you are experiencing this issue, review either MDaemon’s IMAP log or MailStore’s IMAP connection log for the string “UID 0”.
MDaemon will not return a UID starting with zero, so it is not necessary to understand the IMAP protocol, simply finding the string “UID 0” is sufficient to confirm if you are experiencing this issue.