Been away for a while but decided I would continue to use drive mapping as it works.

Thanks for any help & suggestions.

RogerD 

Hi
Using Pegasus 4.63 on Windows 7 Pro 32bit. The configuration files are not on the system drive and I am running as Administrator.

The settings in the Pconfig.cfg read   **PCONFIG  - this should say PMAIL.CFG
Home Mailbox Location \\Giga\Public\MailHome\All
New Mailbox Location \\Giga\Public\MailNew\All

When I open Pegasus I am told the Home Mailbox doesn't exist, however if use a mapped drive for the Home mailbox it works.
Home Mailbox Location Z:\MailHome\All
New Mailbox Location \\Giga\Public\MailNew\All

The UNC paths are seen through Explorer correctly and obviously both Mailboxes exist.

Any thoughts would be welcomed.

Thank you

RogerD 

You mention the paths are in pconfig.cfg which sounds familiar but not a file I have seen recently.  Are you running Netware?  Here's what I know from running a multi-user Pegasus Mail install with both the executables and mailboxes on a Server2003 box.  UNC paths work.  Pmail.cfg is the file that holds the paths.  It is created/maintained by running pconfig.exe.  If I had your problem I would create a new pmail.cfg file by renaming the existing one then running pconfig.exe and entering the Home and New mailbox paths from scratch.

It is common to use a command substitution in place of the username (mailbox directory name) in the paths.  For instance, my UNC paths look like \\server01\mail\~8.  The ~8 is the command substition for the first 8 characters of the Pegasus Mail username.  I believe ~N also works (command substitution for the entire username).  This is how Pegasus Mail routes users to their mailboxes in multi-user environments.  All bets are off if running Netware because I don't know if this is pertinent.  Be advised that these command substitutions do not work in paths that are in .ini files.

Thanks for your response, typo on my side Pconfig.cfg should have read  Pmail.cfg.

No not running Netware just a multi-User set up with executables on Desktops & Mailboxes on Server. Just strange New Mailbox will use UNC path but seems Home Mailbox will only use Mapped drive. 

Now I have just noticed, and keep in mind the pmail.cfg has no Z: in it the Help info reads

 WINPMAIL.EXE directory: I:\PMAIL\Programs
Home mailbox location: Z:\mailhome\all
New mailbox location: \\GIGA\PUBLIC\MAILNEW\ALL
TMP environment variable: C:\Users\TESTAC~1\AppData\Local\Temp
TEMP environment variable: C:\Users\TESTAC~1\AppData\Local\Temp

Where is it picking up Z:  ?

[quote user="Comedians"]Where is it picking up Z:  ?[/quote]

Those paths come from pmail.cfg but you say pmail.cfg has no Z: in it.  Did you determine that by running pconfig?  If so, I wonder if you have a second configuration file

From the Command line options section of the help file:

-E <filename>
Instructs Pegasus Mail to use an alternate standalone configuration file: by default, Pegasus Mail looks for a configuration file called PMAIL.CFG in the directory where it is installed to find its standalone configuration information. This option allows you tell it to use an alternative filename, although the filename you give must have no path attached to it and the file must still reside in the same directory as WINPM-32.EXE. This option is ignored in NetWare mode.

BTW, pmail.cfg is one of the few configuration files that can not be modified with a text editor.  It requires running pconfig to modify settings.

I ran Pconfig.exe around 5 times and opened pmail.cfg in a text editor to see if had the correct paths, didn't edit it from there.

When I open Pegsus mail the first message is
"Pegasus Mail has detected that the directory which it has been told to use as your home mailbox is invalid"
The 2nd message is
"SpamHalter cannot initialize database. Failed to open database Z:\mailhome\all\words4.db3"   

Ah the registry HKCU has entries for Mailbox and Newmail. Newmail was correct path but Mailbox had the mapped drive Z: path. Thought that was it but the change has made no difference.

Only thoughts I have reiterate what I think you have already looked at:

• Confirm that you are running pconfig.exe from I:\PMAIL\Programs.
• Confirm that pmail.cfg is in I:\PMAIL\Programs.
• Confirm that you have full permissions to all files in  I:\PMAIL\Programs.
• Confirm that no -E switch is being used in the shortcut command line.

I am leaving on vacation shortly so hope someone will pick this up with additional suggestions.