Hi! I run PMail since the very beginning therefore many many folders are to be openend whilst every start.

Therefore every start takes so many time, up to 10 minutes, even on a top speed windows office computer.

The folders are saved on my network server, it's 1GBit network so also quite fast.

Any idea how to speed up the start?

Bye

Andy

Slowdowns like you describe are more likely due to a high number of unread messages in the new mail folder in conjunction with filtering rules. We also know that a system without a default printer can cause slowness in Pegasus Mail. What makes you think the slow startup is due to the number of folders?

Also, you stated "many many folders are to be opened whilst every start". Do you have a large number of folder windows opening during a startup or are you referring to a high number of folders in the folder list? If just a high number of folder is the list, that should not noticeably affect startup time unless Pegasus Mail is unable to update HIERARCH.PM during shutdown, or, it is detecting a change in the folder files since the last shutdown.

Hi Brian,

thanks for your reply!
Neither a high number of unread messages (less than 10-15) nor filtering rules (only 1). Default printer set.

I mean a high number of folders in folder list. To be exact the high number of folders are public folders on a remote computer (with designated drive letter).

Maybe the fact also a second user (my wife) works with same public folders causes the slow start? It's likely that folder files are changed after shutdown through her use and vice versa.

Andy

I have worked with public folders but the largest number I ever had was three. Regrettably, I don't know how Pegasus Mail goes about updating the folder and message lists of public folders during startup. The only thing I can think of to suggest is to test a startup without public folders. This could identify the problem as being specific to the public folders.

Also worthy of mention here is that Pegasus Mail can support a maximum of 15 public folder trees.

Hi Andy,
Different of my users in our multi-user Mercury/Pmail network installation are maintaining also a lot of subfolders. Some of them have up to 1000 subfolders. And of course, this leads to an increased startup time of Pmail where all folders will be read. But often only for the first startup of a day. A second start is much faster.
But anyway, also with 1000 subfolders Pmail takes not more that 1 or 2 minutes. 10 minutes is too much.

Following recommendations:
reduce the number of messages in your inbox and sort them into folders when read
reduce the number of messages in recycle bin and release unused space
check all folders for corruptness (folder consistency check) and repair them (if any)
check the physical folder sizes at the server share is less than 2 GB in size
try to exclude Pmail folders from permanent A/V scanning (nevertheless A/V scanning of emails is still important!)

Are you talking about folders or messages in new mail folder.
Since new mail message *.CNM files are individual files large numbers of them can greatly slow down Pegasus Startup.
Then is some limit to the number of messages in new mail folder that cause a slow down or stop to processing.

Know that if one opens a folder that has a large number of messages, it will take some time, but that is on opening the individual folders.

Hi!

Tried everything and thanks to your hints I found it's the number of subfolders in public folder tree. It's one tree but with hundreds of folders. After reducing it the startup is much faster.

Now I think about how to handle, because even if some folders are older they're still in use.

Maybe run 2 instances of PMail, one for the new and often used, another with all. Does it work to run 2 instances on 1 machine?

Yes, as a new Pegasus Mail user. I is imperative that multiple instances do not access the same mailbox at the same time hence the need for the different user. You must also add the -MS commandline option to your shortcut. This tell Pegasus Mail that you are intentionally running Multiple Sessions.

Perhaps a better option would be to put the less used public folders in a different tree and then add that tree when you need it and remove it when done. I have never done this but I think it should work. I would test it first by putting a copy of one of the folders in a separate tree and then seeing how the add tree and remove tree process works.