The problem is that Pegasus Mail updates configuration files each time it is opened and closed.  Those configuration files reside inside of the mailbox directory.  Because of this, the mailbox directory can not be accessed by two instances of Pegasus Mail at the same time.  This is key:  two instance of Pegasus Mail can not access the same mailbox at the same time.  The result often is corruption of one or more files in the mailbox directory.

If the mailboxes are on one machine then the devices must always have access to this machine in order to do email.  There is a concept of New mail mailbox and Home mailbox  whereby new mail is stored locally until moved to a folder at which time it is moved to the home mailbox.  This might work for you but requires that users keep their new mail folder empty in order for all mail to be accessible by other devices.  The limitation of two instances simultaneously accessing a mailbox remains. 

Finally, Pegasus Mail is multi-user capability meaning that a single installation can be run by multiple users.  In my office I have a single instance of Pegasus Mail installed on a server with 13 users running that instance on their desktop PCs.  Each user can run their configuration from whatever office PC they need to but the caveat remains that they can run only one instance at a time.  The problem with this setup is that laptops, tablets, and smartphones need access to the mail when not connected to the office LAN (that's where running an IMAP capable mail server comes in).  If all of your family devices will only access mail when connected to the home LAN then the multi-user approach would work except for devices that can not run an app like Pegasus Mail (eg;  smartphones and iDevices).

If I open Peg last, after all other programs are up and running, looks like the problem disappears.

Thanks Brian, that did the trick!

[quote user="Brian Fluet"]My experience was that the RO flag was removed when I moved RO flagged messages out of the NMF, marked them as unread, then reindexed the containing folder.[/quote]

It might only work the way I said if not set manually.

You don't HAVE to reconfigure the default identity.  You can add the -id option to the command line in the shortcuts which tells Pegasus Mail what ID to start up as.  An example command line to start Pegasus Mail as USER1 and identity ID1 would be: 

C:\Pmail\Programs\winpm-32.exe -A -i USER1 -id ID1

If you choose to reconfigure the default identity some important configurations settings that come to mind for change consideration are your personal name, your internet email address, and which POP3 and SMTP hosts are enabled and the associated settings.

Read the help file about that function of moving the home mailbox location.  What is happening should then make sense.

Just to be clear, the messages that are not going to the copies to self folder are only the ones being sent as the problem gmail account?

If this is correct, I would enable the option to ask at send time whether to make a copy to self and test that functionality.  Keep in mind that these settings are identity specific so if you are using a unique identity for the gmail account be sure to check/change the configuration setting while as that identity.

As for messages not appearing in the new mail folder, if coming down via POP3 then they only way they don't appear is if they are diverted by a filter.  So either they are not being retrieved or there is a filter that is diverting them.

To test I would create create a new folder called GMAIL_TEST.  I would then make the first rule in the new mail folder open filter list one that checks the To: header for "gmail" and moves those messages to the GMAIL_TEST folder.  New mail filters are not identity specific so this rule should insure that any message coming down from a gmail server will be moved to the GMAIL_TEST folder.  An autofilter may override this rule but you have checked for those so this test should confirm whether messages are coming down.

Once you have accumulated a few messages in the GMAIL_TEST folder I would disable the test rule then move the messages to the new mail folder to see what happens.  If they don't appear, or disappear after closing and reopening the new mail folder, then you know you have a filter somewhere that is moving them.

Reindexing will only do it, if the problem is in indexfile of folder. If the problem is in file holding the mails of folder (the bigger one), that wont do it. You may try to free the space used by the empty folder (sorry - have german Pegasus, don't know exact text of menuepoint in contextmenue in english). But if that doesn't do it, deleting the folderfiles on closed Pegasus is the only but successful way.

Olaf

[quote user="chriswjdh"]

Problem solved by clever fellow at ZEN. Various addresses needed changing following my broadband switch.  Thanks.[/quote]

Glad you got it sorted.  I've used Zen for many years and found their support to be very good.

Look at this for starters:

 http://community.pmail.com/forums/thread/25933.aspx

Danke, übersetzt und kopiert. Kannst Du mir sagen, ob ich irgendwo in pmail einstellen kann, mit welchem program files geöffnet werden?

Wow! Thanks a lot. My mistake: I have to get used to IMAP.

Apparently I looked at the mails in Thunderbird and assumed that Thunderbird would mark them as read just privately. But instead it seems they were marked as read on the server. Pegasus honours the flag and downloads unread messages as unread and read messages as read.

Oskar

Thanks for a hint. It suddenly started to work. Next time I will try to set a font, now I have selected "Arial CE" 20.

[quote user="alkemyst"]if I highlight 20-30+ emails and delete them Pegasus takes a long time as the deleted items fill up. [/quote]

I run across that behavior occasionally, it can get excruciatingly slow to delete even one email. Most of the time deletions occur almost instantly, dunno what causes the slowdowns.

That fixed it; I just needed to identify a default browser - thanks.

[quote user="Invictus"][quote user="petersumm"]

Hi, Invictus

Did you ever find a solution?  We're having the same sort of issues with networked Pegasus and Windows 10 here.  It works fine on the Windows 7 machines.

Thanks,

Peter 

[/quote]

Hello Peter,

No I never got a solution.

I only have 2 clients running win 10 & as human beings we have got used to it.....but I really would like to get to the bottom of it.

[/quote]

Try running in compatibility mode.

Our configuration:

-WinPMail version: Version 4.63 (Win32), Dec 22 2011, build ID 325

(I plan to upgrade to the latest version of Pmail sometime soon).

-Program files installed in shared folder on Windows Server 2012 R2.

-Domain users granted all permissions EXCEPT Full control & Special permissions.

-Clients run the executable from a shortcut pointed to a mapped

drive for the shared folder.

Windows 7 Pro clients were working fine.

Recently I setup some Windows 10 Pro version 1709 machines.

Pegasus Mail crashes after around 5 minutes on Win10Pro.

I configured the shortcut to run in Windows 7 compatibility mode - same problem.

Then I changed to Windows XP SP3 compatibility mode, and no more crashes. 

Thank you to each of you who responded to my post.  I plan to check out each of your suggestions - including one I never thought of (and have never used) - mail merge.   Thanks again.

Thank you. Perfect!

Haha - OK, thanks :)

Gmail uses a system of labels rather than folders. When you open a "folder" you are actually conducting a search for mail with a particular label.

When you move mail you are actually manipulating labels.

Historically most mail clients have had problems with the Gmail "system" to a greater or lesser extent.

Reportedly the client that deals with it best is Thunderbird.