You could also try an IMAP connection leaving messages in place and only downloading the ones you select. Open Pegasus Mail's help via the respective menu, then the Index tab and type in "i" for jumping to the respective section, see below:
I suspect that you have a heirarchical folder system and that there are sub folders located off different trays that use the same folder name.
2017 | Accounts
2018 | Accounts
You will find that copying messages into accounts will not necessarily end up in the folder you thought it would go to. You need to eliminate duplicates (even though they are child items off different parents).
To fix it you would need to rename the above to Accounts 2017 and Accounts 2018.
I'm sure your messages are there. You just need to look in all the child folders that may have the same name.
For those veterans of Pegasus Mail still using MLTPOP32 I have updated the HLP file so it will run in both 32-bit and 64-bit modes, and it can be downloaded from http://www3.telus.net/public/irelam/mltpop32.zip
I'll access my backups and see what I can recover otherwise I'll just have to wrack my brains and try and recreate whatever it was I originally noted in the various annotations. Lesson learned, store nothing too important in the annotations.
I am very pleased to say that I now have my data back, at least for my user, "kenneth" in the I:\PMAIL directory.
I copied the contents (files only) from the backup of two nights ago, and then the contents of the "kenneth" directory, and Pegasus started normally. So it must have been some sort of corruption of the file contents of I:\PMAIL and/or I:\PMAIL\kenneth. And it seems that Pegasus behaves better if a backup is not copied to a new directory, but rather into a directory in an identical location to the original, after renaming the original. This relates to your earlier comment.
Now I have carefully to examine the most recent version of the "kenneth" directory mail message and folder files collected today and hopefully restore them by copying them into the now usable "kenneth" directory.
I shall use your helpful comments in your recent post to help me to do that.
Just to let you know I have downloaded this document set already. The format is extremely complex, and I really don't think I can cope with fathoming out what Microsoft is trying to achieve. I have obtained the pointers to the various sections of a DOCX file and I know the headers for PDF and ZIP files, as well as standard *.doc files. So I will try an experimental version of Mapipm to extract these files programatically.
I have located the blocks that contain the email message header lines and body content as well, so I may be able to re-constitute the original email message, or close to it.
That being said this will likely take some time.
Martin
If that works to satisfactions I will then work on other filetypes like *.XLS etc
Noticeboards are a really useful feature in a shared network environment. In my case, before I retired, in my office environment, a user could get a mail from an external company, and a copy of that message would be put in the relevant folder (eg;Company name) for everyone authorised to see the message, and act on it. Where it differs from regular folders is that the feature requires that permissions be set up by the administrator for people (P.M userid) to be able to access a particular folder structure for read and/or write access. This allows for temporary access to others while a person is absent from work due to illness or vacation etc.
It is the same kind of thing as OS file access control on a network drive. The only real difference IMHO is that granting and removing access is a simple text file rather than the insanely complex system dreamed up by Microsoft.
For single users like myself at present it becomes a simple filing system to access messages quickly. The only real difference between regular messages and noticeboard messages is that for noticeboards the messages remain individually kept as *.CNB rather than *.CNM in a folder. This is just like viewing messages in a NewMail display. No compressing/indexing folders is ever required.
All that being said, I have not tested it out in Windows 10 32/64 bit modes.
That .PMM file is a folder file. You indicated earlier that you found message files (.CNM) there as well. The existence of both makes me wonder if it's a mailbox directory. What does your Help > About Pegasus Mail > Info show for paths to the home and new mailbox?
Might D:\PMAIL CURRENT be an added mailbox to your folder list that you are filtering to?
When did this start for you? Are freezes occurring at the same time as the temporary hangs just worse?
I updated my Win10 machine just prior to seeing your post so am curious if it is this update that has caused the issue. I'll certainly post again if my hangs are worse.
Thanks Brian. As with most computer issues, a reboot seems to have done the trick. But I'll keep your advice in the back pocket for the next time this happens!
Unfortunately not in headers, only in the body (as noted previously in this discussion). The headers use fixed fonts hardcoded in the program. Fixed fonts are also used in a number of other places (configuration windows come immediately to mind).
Workarounds to the small fixed font size on hi-res monitors are to increase screen resolution or use a magnifier app.
You configured (or it's default) Pegasus to apply timezone correction to the maillist so that Pegasus shows all mails with date converted to your timezone. Hmm - translated directly from german Pegasus if a message marked in mailölist:
Message - > [x] Apply timezone corretion
If you open the mail or print it, Pegasus shows the real date-header (with local time of the sender), but that should be "March 14, 2018, 03:44 +0400"