Is there anyway I can call you...trying to understand your language is very difficult. You can send me your phone via 2001@VINEYARD.NET
Sorry @papazulu, I won't do that.
Since my last post I have received a response from David Harris, the developer of Pegasus Mail, about your multiple "e-mail received" issue. Below is his response. It reinforces my suspicion that active scanning of the mailbox directory by your anti-virus product could be the problem. Excluding the directory C:\PMAIL\MAIL\ADMIN from active scanning should be your next step.
From David Harris:
Just a thought... If he has a slow or poorly-written A/V package, it may be blocking access to the file any time something is written to it. Pegasus Mail sees the blockage as "folder doesn't exist or is damaged", so it creates a new one.
This is pure speculation - I haven't made any attempt to look through the code to see if it's what's happening, but it's certainly plausible. Ask him to disable his A/V package for a while, or to exclude his mailbox directory from its depredations, and see if that changes the behaviour.
Bizarre, unpredictable and unrepeatable problems in this category frequently come down to interference from A/V systems, so it's always worth checking that any time you see a strange-looking file-related problem.
[quote="pid:59123, uid:38672"]Is there anyway I can call you...trying to understand your language is very difficult. You can send me your phone via 2001@VINEYARD.NET[/quote]
Sorry @papazulu, I won't do that.
Since my last post I have received a response from David Harris, the developer of Pegasus Mail, about your multiple "e-mail received" issue. Below is his response. It reinforces my suspicion that active scanning of the mailbox directory by your anti-virus product could be the problem. Excluding the directory C:\PMAIL\MAIL\ADMIN from active scanning should be your next step.
From David Harris:
_Just a thought... If he has a slow or poorly-written A/V package, it may be blocking access to the file any time something is written to it. Pegasus Mail sees the blockage as "folder doesn't exist or is damaged", so it creates a new one._
_This is pure speculation - I haven't made any attempt to look through the code to see if it's what's happening, but it's certainly plausible. Ask him to disable his A/V package for a while, or to exclude his mailbox directory from its depredations, and see if that changes the behaviour._
_Bizarre, unpredictable and unrepeatable problems in this category *frequently* come down to interference from A/V systems, so it's always worth checking that any time you see a strange-looking file-related problem._