Problem solved, thank you for your help.

It was indeed a question of user rights in "Outgoing mail path" - security setting were allright but those sharing permission were read only -argh!

Thank you for pointing me into right direction - I was somewhat confused about where Pegasus was writing the 101-files, of some mysterious reason I was looking for them under pmail-path not mercury.

New server is up and running.

---

What is the meaning of that last setting "Force all mail through?" ? Where else could the mail possibly go than through Mercury?

Hi,

I'm about to move Pegasus & Mercury to a new server (Win2003 R2).
Paths and drives are identically set up as on old "server" (winXP)
Everything seems to move nicely:
- Mercury starts and Pegasus mailboxes are visible through Mercury
- Clients MercuryD & MercuryC + Core Process looks normal
- Pegasus starts and all user accounts are available
- Using current versions of Pegasus / Mercury32

But...,
I'm facing a strange problem Pegasus mail will not send mail

- Pegasus starts up allright all folder&mail accessible
- When I'm writing a new message and click Send (or Ctrl+Enter) nothing happens - I only get an timeglass on the Message screen - the message window will not close and the message is not sent
- No matter how long I wait the message is not beeing sent. When I manually close the message composing window Pegasus is working normally - no freezing or crashes
- Do not close this window is NOT checked in Message / Special
- In Pegasus system messages there is a line "Message sent to recipient XXXX"
- No trace of message in Mercury
- No trace of message in folders Copies to self
- I'v tried to enable logging in Pegasus but I can not find any logfile - maybe it don't do any logging

I've also tried this setup on another XP-computer - facing same problem - Pegasu will not send mail

Anyone have a clue?

KajMan
Finland - land of F1-champions 

You error indicates to me that the path to the Mercury/32 is wrong and/or the program does not have the rights to create/write the message in the queue.  Run PCONFIG.exe from the WinPMail program directory and verify the MERCURY user defined gateway.  If the path is correct make sure that the user has the proper rights to the queue.  When setting up the queue make sure you are using the \\server\volume\path UNC format so that the program is looking to the correct system and drive when writing the 101 file.

Thank you Thomas for a quick reply.

I'm pretty sure about having those paths right, but of course I'm going to check once more.

Where is Pegasus writing the mail file that is created when i click Send button - obviously that is the place that I've to check those permissions?

[quote user="KajMan"]Thank you Thomas for a quick reply.

I'm pretty sure about having those paths right, but of course I'm going to check once more.

Where is Pegasus writing the mail file that is created when i click Send button - obviously that is the place that I've to check those permissions?


[/quote]

When you have Pegasus Mail integrated with Mercury/32 there is a pmgate.sys file in the WinPMail program directory specifying the mail directory queue via a user defined gateway (UDG).  This is managed via pconfig and here's a sample of the UDG.

              Gateway name :  MERCURY
           *New mail path :
   Is ? a program to run? :  N
    *New mail search mask :
      *Outgoing mail path :  \\thomas\maxtor\MERCURY\QUEUE
   *Run for outgoing mail :
         *Filename format :  ~d~d.101
  Run to validate address :
    *Reply address format : ["~p" <~r>                   ]
  Accepts SMTP addresses? :  Y
  Simple message headers? :  'Glue' headers
    UUEncode attachments? :  Y
          Burst messages? :  N    Gateway processes BCC? : N
      Strip gateway name? :  Y
  Force all mail through? :  Y

 In this case WinPMail in writing the 101 file to the directory specified in the "Outgoing mail path"