I moved the Pegasus mailbox to a local drive (actually in the same

directory structure) so that it was no longer over a network mount -

now deletes work fine!

This does suggest, though, that this problem might crop up should someone have a mailbox on a network disk under Windows 7.

 I do run WinPMail on Win7 with the data files on a network server connected via wireless.  I do not see any delay like this so this is probably one of two thing:

1.  There is some drive that is not available and the system is going through a timeout before continuing.  I saw this one on WinXP with a bad CDROM drive. 

2.  Win7 does not like the way you are doing the mapping of the network drives.

When I delete an email message, Pegasus goes unresponsive for 30-40 seconds.  Something similar happens when I move a message from one folder to another.  It has gotten so annoying I've begun to consider changing email clients (though I've used Pegasus since at least 1996).  My Pegasus version is 4.52 (Win32), Jan 13 2010.

I'm running Windows 7, 64-bit, Ultimate Edition, on a system with 12 GB of memory, lots of disk space, an Intel i7 9.75 CPU at 3.33 GHz, and basically no significant load.  The anti-virus tool is Avira Antivir Personal, which certainly didn't cause any problems when I ran it under XP and Vista.  (My first guess was that perhaps Pegasus was moving files about, and that something related to the filesystem, e.g. antivirus, might be slowing it down).  Nothing else I do on the system, e.g. copying or moving files by hand, has any sign of delay.

Of course I'd love it if someone had an answer for this, either involving a Pegasus setting of a Windows 7 setting, but absent that I'm willing to try to analyze it further.  For developers: is there any 'instrumented' version of Pegasus that might help isolate the problem? 

I suspect that you have installed Pegasus in c:\program files. See http://community.pmail.com/forums/thread/21561.aspx.

Cheers!
Steffan

No, it's elsewhere; N:\mail\pegasus, with N a network drive. 

 It's simpler than that, really; on all of my machines I set up virtual disks U: (for user files), N: (for network-related stuff), and some others, so that scripts, explicit paths, etc. don't change when I move between machines.  These virtual disks are either done with SUBST or by network mounting them (on the same machine). 

That has never been an issue before now; might be worth testing it now.

 I'll have to give it some thought - maybe moving Pegasus is worth a test, but I'll have to do it so as to not lose what I've got, and I'd like to be able to stick with N: if it's not the issue.

I moved the Pegasus mailbox to a local drive (actually in the same directory structure) so that it was no longer over a network mount - now deletes work fine!

This does suggest, though, that this problem might crop up should someone have a mailbox on a network disk under Windows 7.