One of our servers on which Mercury and Pegasus Mail and the mailboxes are installed (Win2003 32bit) is in poor shape - this morning the RAID array started to fail.
I have moved all the mail boxes to a 64 bit server (Win2008 64bit), and Mercury and Pegasus Mail have been moved there too.
I hit a snag straight away as I was unable to run pconfig.exe to configure the mail paths (it will not run on a 64bit system). So, I copied the program files from the 64bit server to a Win2008 32bit server and ran pconfig.exe, configured it, then copied all the files back.
I've set the path to Pegasus Mail within Mercury and when I open Mercury and use Configure>Manage Local Users I see the list of users.
If I open winpm-32.exe from the server I can access any mailbox and send mail, both to local and external users, which is delivered successfully. Mail sent from outside is delivered by Mercury fine and I can see new mail in the New Mail Folder.
However, when I try to access a mailbox from a client, I get the user does not exist error.
All clients access winpm-32.exe via a shortcut on the desktop that uses a DFS namespace. I have updated the DFS namespace to reflect the new path to the folder containing the mailboxes. The DFS namespace is definitely updated from the client as I can open the namespace in explorer and write to the folder on the 64bit machine. When I log onto the server containing the mail folders I can see the new file.
But, for whatever reason, (I presume) the pmail.usr file is not being read by winpm-32.exe.
The pmail.usr file is correct - I have checked it using notepad, and Mercury can obviously read it too.
Can anyone help me with this, please? I have a whole pile of users waiting to check their email.
Thanks
<p>One of our servers on which Mercury and Pegasus Mail and the mailboxes are installed (Win2003 32bit) is in poor shape - this morning the RAID array started to fail.</p><p>I have moved all the mail boxes to a 64 bit server (Win2008 64bit), and Mercury and Pegasus Mail have been moved there too.</p><p>I hit a snag straight away as I was unable to run pconfig.exe to configure the mail paths (it will not run on a 64bit system). So, I copied the program files from the 64bit server to a Win2008 32bit server and ran pconfig.exe, configured it, then copied all the files back.</p><p>I've set the path to Pegasus Mail within Mercury and when I open Mercury and use Configure&gt;Manage Local Users I see the list of users.</p><p>If I open winpm-32.exe from the server I can access any mailbox and send mail, both to local and external users, which is delivered successfully. Mail sent from outside is delivered by Mercury fine and I can see new mail in the New Mail Folder.&nbsp;</p><p>However, when I try to access a mailbox from a client, I get the user does not exist error.</p><p>All clients access winpm-32.exe via a shortcut on the desktop that uses a DFS namespace. I have updated the DFS namespace to reflect the new path to the folder containing the mailboxes. The DFS namespace is definitely updated from the client as I can open the namespace in explorer and write to the folder on the 64bit machine. When I log onto the server containing the mail folders I can see the new file.</p><p>But, for whatever reason, (I presume) the pmail.usr file is not being read by winpm-32.exe.</p><p>The pmail.usr file is correct - I have checked it using notepad, and Mercury can obviously read it too.&nbsp;</p><p>Can anyone help me with this, please? I have a whole pile of users waiting to check their email.</p><p>Thanks&nbsp;</p>