Continuation...

I have noticed on Task Manager on the PC that sends the faulty email "Unknown "From" and "None" Subject that there were TWO winpm-32 processes running with different PID's.

Closing Pegasus only resulted in ONE of the processes shutting down... was forced to kill the other.... maybe this is involved somehow. The server is the PC that receives the problem emails.

Don.

Don, you need to help us out here by describing your installation and usage of Pegasus Mail. You've said "server", "no internet", and "TWO winpm-32 processes", all of which need more explanation.
What do you mean by "server" and how does that fit into your Pegasus Mail?
Is D: a network share on a server?
How is mail getting into your mailbox?
There should never be two instances of Pegasus Mail running that access the same mailbox. An open Help window will appear in task manage but is clearly labeled with reference to the help system so I don't think is what you are talking about. So the question then is whether there are indeed two instances of Pegasus Mail running that are accessing the same mailbox. If there are, that is a problem that needs to be figured out.

FWIW - I have two Pegasus processes running, but the second is the Print driver host for applications and there is only one Pegasus process PID listed under Task Manager's Details tab.

Question #1 - If you aren't using internet email, then, what WAN/LAN are you running (i.e. Novell?), and are you running Mercury Mail transport System?

Question #2 - After boot up, and without launching Pegasus manually, is there a WinPM-32/Pegasus (or Mercury) application listed under start-up, and if so, what is its enabled/disabled status? (I imply no consequence here, just gathering clues).
Depending on the answer to these questions, I'll install Pegasus on one of my legacy WinXP laptops (and maybe AV) for further assistance.. However, if Mercury is involved, I'll just go to lurk as I have no experience or knowledge of that mail processing environment.

The "Print driver host for applications" is the description for splwow64.exe which is a Windows process for connecting 32 bit printer drivers on a 64 bit OS. I had never noticed that Pegasus Mail loads it. I just learned something. Thanks!

This is a windows peer to peer intranet.
The initial installation is on a VirtualBox XP VM (on W10 host) with IP address 192.168.0.14 and folder Pmail -- I refer to this as the 'server' - I used wssetup.exe to install the program on the workstations
P: is mapped to 192.168.0.14\pmail
The problem appears to arise from a pure windows XP PC (old but works for our management software) which maps to 192.168.0.14\pmail too.
We do not use pegasus to connect to the internet (for internet mail we use Outlook)

Hope this helps
Don

OK. So it is an installation shared by an XP VM and an XP PC. The program files and the mailbox directories are on mapped drive P: which is physically located on the VM.

I am not officially out of my depth here, knowing nothing of VMs nor the current limitations/issues with Pegasus Mail and its extensions like IERenderer on XP.

Is it a safe assumption that the VM and XP PC run Pegasus Mail as different Pegasus Mail users, or if not, never run simultaneously?

IER's limitations on XP are the IE modules installed: If there are only the IE 6 modules available (the default it came with) there's no guarantee it'll work properly which is why current IER versions switch to BearHtml if detecting IE versions below v8 - which is the final one supported by XP SP2 and SP3 .

Okay,,, report back on the problem which is now solved.

It seems the problem was related to the PC itself. I noticed a low memory available to DOS (mem /c) which cause intermittent errors with another program we use regularly. Due to a LPT port failure I was forced to replace the PC with a W10 host and VirtualBox VM XP guest. No more problems.

It's been interesting.

Thanks to all the guru's.

Don.

(I applaud your optimism.. I hope you're right..)

In a "Chinese Curse" sort of way..