I have run into this a few times:
- - try to migrate a user from another mail client
used the common .mbx (unix mailbox) format to move the mailboxes to something Pegasus will read
- - copy the file into the Pegasus mail directory, restart Pegasus
- - the exported mail box is there
message counts are higher than what was exported
- - open the folder and find a number of messages with blank sender & blank subjects
open any the improper emails and find they are snippets from other emails
Now to test I would copy the orginal .mbx file to either:
Mulberry - native support for .mbx, no issues with mail count or emails contained
Becky! - import into the client via builtin tool for import, no problems with emails.
So now I am thinking that it is with the import filter. So I do the same procedure from Pegasus. Create a new folder formatted as Unix mbx. Copya few hundred emails (created last month) to this directory. Shutdown Pegasus, locate and move the UNIX box from the mail directory.
Now import into the above mail clients - bad count and emails are split -- failure.
If I copy the emails to an IMAP mailserver and then download into Pegasus no problem via IMAP account.
This tells me the import/export has problems with some emails. Not sure if it is due to html formatting from whatever client generated. Seems strange that other mail clients can read the .mbx properly but Pegasus fails. If this was improved I think that more people would try and stay with Pegasus.