Solved.

I set up pmail on another win 7 machine. No problems. So -- not a networking issue as such.

After some faffing, I found that, somehow, and only on the one machine, the shortcut had -roam on the command line! Doh! Remove that -- all is good!!

 Don't know how that got there, I installed with default settings on all, but anyway, good that it's all working!

Hi...

I installed pegasus on my server (win XP). It works fine stand alone.

I need to get it running across the network. I've read all the posts on this I can find and it's set up as below: 

The server email folder is set to:  \\Speedy\c\PMAIL\MAIL\~N  

(the setup adds the \~N  to the path I enter, \\Speedy\c\PMAIL\MAIL)

works fine stand alone.

I installed pegasus on Win7 x64 machine.

email folder is set to:

\\Speedy\c\PMAIL\MAIL\~8

Again, the setup program added the \~8 but I think that is correct.

I can view the contents of \\Speedy\c\PMAIL\MAIL\ and \\Speedy\c\PMAIL\MAIL\ADMIN via cmd.exe on the win 7 machine. 

When I start pegasus on the Win 7 pc it says "Starting up - please wait"  -- and stay there forever...

I'm running it as admin. 

Any ideas what I'm doing wrong?

 Thanks! 

The piece of the puzzle that is missing is that Pegasus Mail on the Win7 machines doesn't know where the mailbox directories are.  It looks to a file called PMAIL.CFG for that information.  PMAIL.CFG is created & modified using PCONFIG.EXE.  This is one place where the age of Pegasus Mail shows.  PCONFIG is a DOS app (16 bit?) that will not run on the Win7 64bit machine without using a DOS emulator like DOSBox.  However, you can run it on the XP machine and then copy the resulting PMAIL.CFG file to the Pegasus Mail programs directory on the Win7 machine.  To do this copy PCONFIG.EXE and PCONFIG.RSC to a temporary directory then run that PCONFIG.EXE.  The resulting PMAIL.CFG file will be created in that directory.

In PCONFIG you need to select the Standalone configuration option then enter the path (\\Speedy\c\PMAIL\MAIL\~8) as the Home and New mailbox locations.  Use ~N instead of ~8 if you use Pegasus Mail usernames longer than 8 characters.  No other settings need to be changed in PCONFIG.

Since the mailbox directories are going to be on the XP machine as a server consider running that installation of Pegasus Mail on the Win7 machine.  Doing this means only one instance of Pegasus Mail to maintain.  Map a drive (say M:) to \\Speedy\c\ then use a command line that would look like M:\Pmail\winpm-32.exe -A -I username.  To get full functionality on the Win7 machine you would normally need to run M:\Pmail\Programs\wssetup.exe (workstation setup) but this should not be necessary in your case because you have already run the Pegasus Mail installer.  Note: the mapped drive is probably not necessary.  I prefer working with drive letters in shortcuts so that is why I suggest it.

Hi..

 Thanks for the reply. 

I do have the new and \\Speedy\c\PMAIL\~8 in both the new and home location set on Win 7 - that's what I tried to describe. You don't need to use pconfig though -- if you delete pmail.cfg then run pegasus again it prompts you for the path to the mailboxes. I checked the pmail.cfg was correct in both setting too (opened in ultraedit).

The user is the default that pegasus sets up: "ADMIN". 

 As a sanity check I also did a setup on XP and copied pmail.cfg over....  Same result ever time, "Starting up, please wait" forever!

 I take your second point, and that works with both drive maps and UNC path...

I'd like to get the network version to work though!! It ought to work....

Thanks! 

That hang means a problem accessing the mailbox directory.  If it were a bad path I believe you would experience a crash on startup so it might be something to do with permissions.  Check both share and ntfs permission.  The Win7 user needs full permissions to the ADMIN mailbox directory and at least read permission to the \MAIL directory.  Might be best to grant full permissions to \MAIL and include all subdirectories to avoid a permissions problem in the future should you add another user.

Yeah, that's what I thought -- but the shares are all "all permissions to all". Somewhere in the help file it suggested testing path access from a command line box on win 7 to the share -- and that works fine.

I'll have another poke at that though. win 7 permissions are a bit of a.........

Thanks! 

So - I reset all the security settings for the pmail folder to allow all on the xp pc. I see the same settings from the win 7 machine if I navigate to \\speedy\c\pmail.... and right click properties from there. I'm at a loss as to what else to try -- I can read, write modify etc files in the pmail folder from win 7 either in windows explorer or a cmd.exe box..... That should be enough to prove access is ok!

The drawback with running the executable over the network is that you can only open it on one machine at a time. 

I'm hoping to replace MailCopa which has serious problems with win 8.1 with Pegasus. 

Only other thing I can think of to try is to map a drive on both machines (say M:) to \\Speedy\c\ and then use M:\Pmail\mail\~8 as the path in PMAIL.CFG and see if that works.  Machine names are better because they don't rely on mapped drives but testing with mapped drives can't hurt.

Someone recently had a similar problem.  The thread is long but is here if you care to read through it: 

http://community.pmail.com/forums/thread/41768.aspx