[quote user="kaspencer"]

Thanks Brian, but yes indeed the mapped drive is absolutely fine and working.

And the entry in the PMAIL.CFG file is exactly the same as in other Windows PCs, and it works on those. Are you also using Windows 8.1?  I ask because I want to exclude Windows 8.1 as the cause of the issue.

 Kenneth Spencer

[/quote]

If you are receiving this message and you have a local installation of Pegasus Mail (i.e. it is installed on the client and you are not running a single exe from a server) you can easily fix this.

Open This PC, type the server name in the address bar \\servername and then double-click the PMAIL share and then double-click the MAIL folder (or wherever your mail folders are stored). Click once in the white space at the end of the address bar so the full path is shown \\server\PMAIL\MAIL and copy it.

Open the folder containing the Pegasus Mail programs e.g. C:\PMAIL\Programs within that folder backup and then delete the pmail.cfg file. Run winpm-32.exe and a dialog will appear asking you where the mail boxes are stored. 

Click the bottom entry and paste the path in the dialog that appears. Click OK. A new window will appear showing you a list of the users on your server. Click Close.

Fire up Pegasus Mail and type the name of the user mail box you wish to access and you should be OK.

Greetings all ...

 I have run Pagasus Mail since about 1996 on every version of Windows since then. Now I have just installed it on my Windows 8.1 tablet.

My installation is a local drive (C:\PMAIL) installation of the software, and a LAN (I:\pmail\[usernames]) for the mail data. The installation proceeded normally, and I selected the mail data location at first run on the new tablet. However, when I atept to loogin (with a valid account name), Pegasus informs me that the user does not exist or cannot be found. I have checked the PMAIL.CFG file and it's content is identical to that in my Windows Vista, Windows 7 and Windows Server 2003 machines.

 So: has anyone else expeorinced this issue, and what can I/should I do about it?

Many thanks in advance,

Kenneth Spencer

A failed or incorrect drive mapping comes to my mind so verify that you can navigate to I:\pmail and make sure I:\ is mapped appropriately.  If the path in PMAIL.CFG is I:\pmail\~N then you want to make sure that you didn't map I: to \\servername\path\pmail as that will result in Pegasus looking for mailbox directories in I:\pmail\pmail.

FWIW, I use UNC paths rather than relying on mapped drives (eg: \\server01\mail\~N).  I also share a single install of Pegasus Mail which is located on the same server as the mailboxes.

Thanks Brian, but yes indeed the mapped drive is absolutely fine and working.

And the entry in the PMAIL.CFG file is exactly the same as in other Windows PCs, and it works on those. Are you also using Windows 8.1?  I ask because I want to exclude Windows 8.1 as the cause of the issue.

 Kenneth Spencer

[quote user="kaspencer"]And the entry in the PMAIL.CFG file is exactly the same as in other Windows PCs, and it works on those. Are you also using Windows 8.1?  I ask because I want to exclude Windows 8.1 as the cause of the issue.[/quote]

I'm not.  I have a Surface Pro 3 on the LAN but have not run Pegasus Mail on it.  I haven't worked with it much but I know I would have heard about odd experiences with accessing server based files.  If I find some free time I'll attempt to run Pegasus on it and see how it behaves.

I just spent my first half hour at the office working with Pegasus Mail on the Surface Pro 3 running Win 8.1.  Did spam folder cleanup, read new mail, sent a couple of replies and test messages with a Pegasus Mail restart in between.  All behaved as expected.

Configuration is Pmail and mailboxes are on a Server 2003 machine.  Mapped drive to the \SHARED_APPS directory in which \PMAIL executables reside (not mailboxes).  UNC paths within Pegasus Mail to mailboxes.  Ran as a network admin because of limited user configurations on the Surface Pro.  I used both the -I <user> and -ID <identity> command line options when starting Pmail from a command prompt.

Kenneth, sorry that I am not able to help identify your problem.