Keeping settings between PC's

Greenman

posted Feb 7 '08 at 10:29 am

Fixed it (hooray!)

The problem was that although I had created the new synonyms file with the changed address, and had copied it to the root of the PMAIL folder containing the mailboxes, I had not copied it to the default ..\Mercury\Mercury folder. Also, I had to stop and restart Mercury before the synonyms file was read properly. So it all works fine now.

Thanks, Thomas for your patience and help [Y]

Fixed it (hooray!) The problem was that although I had created the new synonyms file with the changed address, and had copied it to the root of the PMAIL folder containing the mailboxes, I had not copied it to the default ..\Mercury\Mercury folder. Also, I had to stop and restart Mercury before the synonyms file was read properly. So it all works fine now. Thanks, Thomas for your patience and help [Y]

Greenman

posted Jan 29 '08 at 4:50 pm

Hello folks

We use Pegasus Mail with Mercury/32. All mail accounts are located on a server in a Windows Server 2003 Active Directory environment. The accounts are accessed by Windows clients.

In our office we have a situation where staff sometimes have to use different PC's. What we find is that if the Pegasus Mail account is accessed from a different PC, when that account is accessed from the original PC again, all Pegasus settings are lost - account name, new mail settings, reader settings etc etc.

As all user accounts are centrally located on a server, I was hoping that each account's settings would be stored there too. So, is there a setting in Pegasus that tells it to store mail account preferences with the mail account, rather than locally? Or, can anyone tell me the name of the files that need to be backed up to allow restoration of the original settings please?

Thanks

Hello folks We use Pegasus Mail with Mercury/32. All&nbsp;mail accounts are located on a server in a Windows Server 2003&nbsp;Active Directory environment. The accounts are accessed by Windows clients. In our office we have a situation where staff sometimes&nbsp;have to&nbsp;use different PC's. What we find is that if the Pegasus Mail account&nbsp;is accessed from a different PC, when that account is accessed from the original PC again, all Pegasus&nbsp;settings are lost - account name, new mail settings, reader settings etc etc. As all user accounts are centrally&nbsp;located on a server, I was hoping that each account's settings would be stored there too. So, is there a setting in Pegasus that tells it to store mail account preferences with the mail account, rather than locally? Or, can anyone tell me the name of the files that need to be backed up to allow restoration of the original settings please? &nbsp; Thanks

Thomas R. Stephenson

posted Jan 29 '08 at 5:14 pm

Looks like you are using different drive mapping on these systems. These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths. I assume that you are using one version of Pegasus mail on the 2003 server that all the users access. Go to the program directory and run PCONFIG.exe. Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation.

Looks like you are using different drive mapping on these systems.&nbsp; These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths.&nbsp; I assume that you are using&nbsp; one version of Pegasus mail on the 2003 server that all the users access.&nbsp; Go to the program directory and run PCONFIG.exe.&nbsp; Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation.&nbsp;

Greenman

posted Jan 30 '08 at 10:58 am

[quote user="Thomas R. Stephenson"]

Looks like you are using different drive mapping on these systems. These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths. I assume that you are using one version of Pegasus mail on the 2003 server that all the users access. Go to the program directory and run PCONFIG.exe. Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation.

[/quote]

Thomas, thanks for the reply.

All the clients use the UNC path to the mailbox location: \\servername\pmail\

However, I cannot (and have not) seen any reference to HOME and NEW mail within pconfig.exe

any other suggestions?

Thanks

[quote user="Thomas R. Stephenson"] Looks like you are using different drive mapping on these systems.&nbsp; These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths.&nbsp; I assume that you are using&nbsp; one version of Pegasus mail on the 2003 server that all the users access.&nbsp; Go to the program directory and run PCONFIG.exe.&nbsp; Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation. &nbsp; [/quote] Thomas, thanks for the reply. All the clients use the UNC path to the mailbox location: <A href="file://servername/pmail/" mce_href="file://servername/pmail/">\\servername\pmail\</A> However, I cannot (and have not) seen any reference to HOME and NEW mail within pconfig.exe any other suggestions? Thanks

Thomas R. Stephenson

posted Jan 30 '08 at 4:49 pm

[quote user="Greenman"][quote user="Thomas R. Stephenson"]

Looks like you are using different drive mapping on these systems. These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths. I assume that you are using one version of Pegasus mail on the 2003 server that all the users access. Go to the program directory and run PCONFIG.exe. Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation.

[/quote]

Thomas, thanks for the reply.

All the clients use the UNC path to the mailbox location: \\servername\pmail\

However, I cannot (and have not) seen any reference to HOME and NEW mail within pconfig.exe

any other suggestions?

Thanks

[/quote]

Are you running pconfig.exe from the program directory? It's reading the file pmail.cfg in the same directory as winpm-32.exe and that file must exist when using Pegasus Mail in the standalone (i.e. non-Netware) mode. Other than that I have no other suggestions. When one system works differently than the others with the same user then there is something different about that system, not the common program or the server. Again, this is assuming you are running WinPMail as a client/server application with everything on the server. Here's a sample of the setup.

┌───────────────── Standalone Configuration ──────────────────┐
│                                                                                                                     │
│ Home mailbox :    [\\tstephenson\c_drive\PMAIL\MAIL\~n ]    │
│ New mailbox :     \\tstephenson\c_drive\PMAIL\MAIL\~n                                  │
│ Asynch gateway? : N                                                                                   │

[quote user="Greenman"][quote user="Thomas R. Stephenson"] Looks like you are using different drive mapping on these systems.&nbsp; These settings are stored in the pmail.ini file located in the new mail directory and should be no problem as long as all systems are accessing the mailstore using the same paths.&nbsp; I assume that you are using&nbsp; one version of Pegasus mail on the 2003 server that all the users access.&nbsp; Go to the program directory and run PCONFIG.exe.&nbsp; Set the HOME and NEW mail directory spec to the UNC format so that the drive letter mapping is removed from the equation. &nbsp; [/quote] Thomas, thanks for the reply. All the clients use the UNC path to the mailbox location: <a href="file://servername/pmail/" mce_href="file://servername/pmail/">\\servername\pmail\</a> However, I cannot (and have not) seen any reference to HOME and NEW mail within pconfig.exe any other suggestions? Thanks[/quote]&nbsp;Are you running pconfig.exe from the program directory?&nbsp; It's reading the file pmail.cfg in the same directory as winpm-32.exe and that file must exist&nbsp; when using Pegasus Mail in the standalone (i.e. non-Netware) mode.&nbsp; Other than that I have no other suggestions.&nbsp; When one system works differently than the others with the same user then there is something different about that system, not the common program or the server.&nbsp; Again, this is assuming you are running WinPMail as a client/server application with everything on the server.&nbsp; Here's a sample of the setup. ┌───────────────── Standalone Configuration ──────────────────┐ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; Home mailbox :&nbsp;&nbsp;&nbsp; [\\tstephenson\c_drive\PMAIL\MAIL\~n&nbsp; ] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; │ │&nbsp; New mailbox&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; \\tstephenson\c_drive\PMAIL\MAIL\~n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; Asynch gateway? :&nbsp; N&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │

Greenman

posted Jan 30 '08 at 5:35 pm

This is how our gateway is setup from the client when running pconfig.exe:

The user accounts on the server are just folders which have been copied from our old server.

When we update or install pmail on a PC we always use a UNC path to point the program to the server that contains the accounts.

This is how our gateway is setup from the client when running pconfig.exe: [URL=http://img177.imageshack.us/my.php?image=gateway2ka9.jpg][IMG]http://img177.imageshack.us/img177/1577/gateway2ka9.th.jpg[/IMG][/URL] The user accounts on the server are just folders which have been copied from our old server. When we update or install pmail on a PC we always use a UNC path to point the program to the server that contains the accounts.

Thomas R. Stephenson

posted Jan 30 '08 at 8:20 pm

This is not showing the paths to the mailboxes, this is only showing the UDG. FWIW, I do not like using long filenames for the directory paths in either the mailbox setup or queue. If you must use long filenames convert them to a MSDOS format for this setup.

Please don't use a graphic when a text copy is available. Just copy the text from the application. This is a whole lot easier to read as well

Gateway name : MERCURY
 *New mail path :
 Is ↑ a program to run? : [N ]
 *New mail search mask :
 *Outgoing mail path : \\tstephenson\c_drive\mercury\queue
 *Run for outgoing mail :
 *Filename format : ~d~d.101
Run to validate address :
 *Reply address format : "~o" <~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

Set to 'Y' if the value you have entered in 'New Mail Path' is a
program which should be run, rather than a directory to search.

This is not showing the paths to the mailboxes, this is only showing the UDG.&nbsp;&nbsp;&nbsp; FWIW, I do not like using long filenames for the directory paths in either the mailbox setup or queue.&nbsp; If you must use long filenames convert them to a MSDOS format for this setup.&nbsp; &nbsp;Please don't use a graphic when a text copy is available.&nbsp; Just copy the text from the application.&nbsp; This is a whole lot easier to read as well &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Gateway name :&nbsp; MERCURY &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *New mail path : &nbsp;&nbsp; Is ↑ a program to run? : [N ] &nbsp;&nbsp;&nbsp; *New mail search mask : &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *Outgoing mail path :&nbsp; \\tstephenson\c_drive\mercury\queue &nbsp;&nbsp; *Run for outgoing mail : &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *Filename format :&nbsp; ~d~d.101 &nbsp; Run to validate address : &nbsp;&nbsp;&nbsp; *Reply address format :&nbsp; "~o" &lt;~r&gt; &nbsp; Accepts SMTP addresses? :&nbsp; Y &nbsp; Simple message headers? :&nbsp; 'Glue' headers &nbsp;&nbsp;&nbsp; UUEncode attachments? :&nbsp; Y &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Burst messages? :&nbsp; N&nbsp;&nbsp;&nbsp; Gateway processes BCC? : N &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Strip gateway name? :&nbsp; Y &nbsp; Force all mail through? :&nbsp; Y &nbsp;Set to 'Y' if the value you have entered in 'New Mail Path' is a &nbsp;program which should be run, rather than a directory to search.&nbsp;

Greenman

posted Jan 31 '08 at 9:58 am

[quote user="Thomas R. Stephenson"]

This is not showing the paths to the mailboxes, this is only showing the UDG. FWIW, I do not like using long filenames for the directory paths in either the mailbox setup or queue. If you must use long filenames convert them to a MSDOS format for this setup.

Please don't use a graphic when a text copy is available. Just copy the text from the application. This is a whole lot easier to read as well

Gateway name : MERCURY
 *New mail path :
 Is ↑ a program to run? : [N ]
 *New mail search mask :
 *Outgoing mail path : \\tstephenson\c_drive\mercury\queue
 *Run for outgoing mail :
 *Filename format : ~d~d.101
Run to validate address :
 *Reply address format : "~o" <~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

Set to 'Y' if the value you have entered in 'New Mail Path' is a
program which should be run, rather than a directory to search.

[/quote]

Thanks for your reply, Thomas

The user mailboxes information is thus:

┌───────────────── Standalone Configuration ──────────────────┐
│                                                             │
│ Home mailbox :    [\\ORION\PMAIL\~8                     ] │
│ New mailbox :     \\ORION\PMAIL\~8                        │
│ Asynch gateway? : Y                                       │
│                                                             │
│                                                             │
│ Where your mail folders, address books, distribution       │
│ lists and other associated mail files should be stored.    │
│                                                             │
│                                                             │
└─────────────────────────────────────────────────────────────┘

We have never filled in this information via this interface, hence my earlier confusion. We usually fill in the mailbox location when Pegasus Mail is installed - it asks for the location of the mailboxes when it is first run. I will, and you may not be happy with this, also update this path using a DFS path as seen above. This results in far less maintenance - if mailboxes or the location of the Mercury installation is moved, I just need to undertake a single 30 second edit to update the path at the DFS root, then all clients are instantly updated.

P.S.

Out of curiosity, why do you prefer to see text and not the original context of the information you requested?

[quote user="Thomas R. Stephenson"] This is not showing the paths to the mailboxes, this is only showing the UDG.&nbsp;&nbsp;&nbsp; FWIW, I do not like using long filenames for the directory paths in either the mailbox setup or queue.&nbsp; If you must use long filenames convert them to a MSDOS format for this setup.&nbsp; &nbsp; Please don't use a graphic when a text copy is available.&nbsp; Just copy the text from the application.&nbsp; This is a whole lot easier to read as well &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Gateway name :&nbsp; MERCURY &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *New mail path : &nbsp;&nbsp; Is ↑ a program to run? : [N ] &nbsp;&nbsp;&nbsp; *New mail search mask : &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *Outgoing mail path :&nbsp; \\tstephenson\c_drive\mercury\queue &nbsp;&nbsp; *Run for outgoing mail : &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *Filename format :&nbsp; ~d~d.101 &nbsp; Run to validate address : &nbsp;&nbsp;&nbsp; *Reply address format :&nbsp; "~o" &lt;~r&gt; &nbsp; Accepts SMTP addresses? :&nbsp; Y &nbsp; Simple message headers? :&nbsp; 'Glue' headers &nbsp;&nbsp;&nbsp; UUEncode attachments? :&nbsp; Y &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Burst messages? :&nbsp; N&nbsp;&nbsp;&nbsp; Gateway processes BCC? : N &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Strip gateway name? :&nbsp; Y &nbsp; Force all mail through? :&nbsp; Y &nbsp;Set to 'Y' if the value you have entered in 'New Mail Path' is a &nbsp;program which should be run, rather than a directory to search. &nbsp; [/quote] Thanks for your reply, Thomas The user mailboxes information is thus: ┌───────────────── Standalone Configuration ──────────────────┐ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; Home mailbox :&nbsp;&nbsp;&nbsp; [\\ORION\PMAIL\~8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]&nbsp; │ │&nbsp; New mailbox&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; <A href="file://orion/PMAIL/~8">\\ORION\PMAIL\~8</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; Asynch gateway? :&nbsp; Y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; Where your mail folders, address books, distribution&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp; lists and other associated mail files should be stored.&nbsp;&nbsp;&nbsp; │ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ │&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; │ └─────────────────────────────────────────────────────────────┘ We&nbsp;have never&nbsp;filled in this information via this interface, hence my earlier&nbsp;confusion. We&nbsp;usually fill in the mailbox location when Pegasus Mail is installed - it asks for the location of the mailboxes when it is first run. I will, and you&nbsp;may not be happy with this, also update this path using a DFS path as seen above. This results in far less maintenance - if mailboxes or the location of the Mercury installation is moved, I just need to undertake a single&nbsp;30 second edit to update the path at the DFS root, then all clients are instantly updated. P.S. Out of curiosity, why do you prefer to see&nbsp;text and not the original context of the information you requested?

Thomas R. Stephenson

posted Jan 31 '08 at 5:06 pm

>
> Thanks for your reply, Thomas
>
> The user mailboxes information is thus:
>
> +----------------- Standalone Configuration ------------------+
> ¦                                                             ¦
> ¦ Home mailbox :    [\\ORION\PMAIL\~8                     ] ¦
> ¦ New mailbox :     \\ORION\PMAIL\~8                        ¦
> ¦ Asynch gateway? : Y                                       ¦
> ¦                                                             ¦
> ¦                                                             ¦
> ¦ Where your mail folders, address books, distribution       ¦
> ¦ lists and other associated mail files should be stored.    ¦
> ¦                                                             ¦
> ¦                                                             ¦
> +-------------------------------------------------------------+
>
> We have never filled in this information via this interface, hence
> my earlier confusion. We usually fill in the mailbox location when
> Pegasus Mail is installed - it asks for the location of the
> mailboxes when it is first run. I will, and you may not be happy
> with this, also update this path using a DFS path as seen above.
> This results in far less maintenance - if mailboxes or the location
> of the Mercury installation is moved, I just need to undertake a
> single 30 second edit to update the path at the DFS root, then all
> clients are instantly updated.

That works, especially when Pegasus Mail is run from the server and all the clients are running shortcuts to the WinPMail version on the server. This would require that you make sure all users are off the system when you make the changes. Actually this method is quite common when running a client/server type setup.

>
> P.S.
>
> Out of curiosity, why do you prefer to see text and not the original
> context of the information you requested?

1.   The graphic as posted was so small even on my 19" monitor is was almost impossible to read.

2.   None of the graphics in any post are sent via e-mail and that's how I work this forum.

3.   The graphic takes over ten times the bandwidth of the ASCII text.

4.   There is nothing in the graphic that is not presented in the ASCII text.

&gt; &gt; Thanks for your reply, Thomas &gt; &gt; The user mailboxes information is thus: &gt; &gt; +----------------- Standalone Configuration ------------------+ &gt; ¦&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp; Home mailbox :&nbsp;&nbsp;&nbsp; [\\ORION\PMAIL\~8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]&nbsp; ¦ &gt; ¦&nbsp; New mailbox&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; \\ORION\PMAIL\~8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp; Asynch gateway? :&nbsp; Y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp; Where your mail folders, address books, distribution&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp; lists and other associated mail files should be stored.&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; ¦&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ¦ &gt; +-------------------------------------------------------------+ &gt; &gt; We&nbsp;have never&nbsp;filled in this information via this interface, hence &gt; my earlier&nbsp;confusion. We&nbsp;usually fill in the mailbox location when &gt; Pegasus Mail is installed - it asks for the location of the &gt; mailboxes when it is first run. I will, and you&nbsp;may not be happy &gt; with this, also update this path using a DFS path as seen above. &gt; This results in far less maintenance - if mailboxes or the location &gt; of the Mercury installation is moved, I just need to undertake a &gt; single&nbsp;30 second edit to update the path at the DFS root, then all &gt; clients are instantly updated. That works, especially when Pegasus Mail is run from the server and all the clients are running shortcuts to the WinPMail version on the server.&nbsp; This would require that you make sure all users are off the system when you make the changes.&nbsp; Actually this method is quite common when running a client/server type setup. &gt; &gt; P.S. &gt; &gt; Out of curiosity, why do you prefer to see&nbsp;text and not the original &gt; context of the information you requested? 1.&nbsp;&nbsp; &nbsp;The graphic as posted was so small even on my 19" monitor is was almost impossible to read. 2.&nbsp;&nbsp; &nbsp;None of the graphics in any post are sent via e-mail and that's how I work this forum. 3.&nbsp;&nbsp; &nbsp;The graphic takes over ten times the bandwidth of the ASCII text. 4.&nbsp;&nbsp; &nbsp;There is nothing in the graphic that is not presented in the ASCII text.

Greenman

posted Jan 31 '08 at 5:35 pm

Thanks for the reply, Thomas.

So, is there anything we can do to preserve settings?

You also mention 'clients running shortcuts to the WinPMail version on the server'. What do you mean by this? Do you mean that the client starts Pegasus Mail from a server? We've never done this, so if that is what you mean, I'm interested to find out what the correct procedure is for doing that, especially if it will help eliminate this problem.

Regarding the graphic - I'm sorry, I'm used to broadband connections and forget this is not standard in many places. I'm surprised you had difficulty reading it, I had no problems reading it when I clicked the thumbnail on a 19" monitor here. However, I'll post ASCII text from now on :)

Thanks for the reply, Thomas. So, is there anything we can do to preserve settings? You also mention 'clients&nbsp;running shortcuts to the WinPMail version on the server'. What do you mean by this? Do you mean that the client starts Pegasus Mail from a server? We've never done this, so if that is what you mean, I'm interested to find out what the correct procedure is for doing that, especially if it will help eliminate this problem. &nbsp; Regarding the graphic - I'm sorry, I'm used to broadband connections and forget this is not standard in many places. I'm surprised you&nbsp;had difficulty reading it, I had no problems reading it when I clicked the thumbnail&nbsp;on a 19" monitor here. However,&nbsp;I'll post&nbsp;ASCII text from now on :)

Thomas R. Stephenson

posted Jan 31 '08 at 6:05 pm

> Thanks for the reply, Thomas.
>
> So, is there anything we can do to preserve settings?

Make sure that all users have full rights to their HOME and NEW mail directory and make sure you change nothing at the server level when WinPMail is running. The configuration file is saved at closing and if you make a change it will probably be lost.

>
> You also mention 'clients running shortcuts to the WinPMail version
> on the server'. What do you mean by this? Do you mean that the
> client starts Pegasus Mail from a server? We've never done this, so
> if that is what you mean, I'm interested to find out what the
> correct procedure is for doing that, especially if it will help
> eliminate this problem.

Here's the basic process. The programs are only installed once on the server. The users just run a shortcut. Makes this very easy to maintain. I've used the default directories for Pegasus Mail here, you can change them but I would recommend maintaining the 8 character limit.

1. Install WinPmail in the multiuser mode on the "server". Use
    c:\pmail for the program; c:\pmail\mail for the mail
    directories.

2. Run PCONFIG.exe from the program directory and change the
    HOME and NEW mail directory specification to the
    \\server\vol\pmail\mail\~8 format.

3. Go to the remote workstations and install a shortcut to the
    common program.

Ok, now you have the basic mail system setup. You can send mail to
each other using Pegasus Mail.

4. Install Mercury/32 on this same server pointing to the Pegasus
    Mail directory structure. Use MercuryD, MercuryS, MercuryC at
    least. Use \\server\vol\mercury\queue for the mail spool directory.

5. Point MercuryD at all of your POP3 mailboxes to download the mail
    to your Pegasus Mail user directories.

You now can send and receive Internet mail via Pegasus Mail. The mail is delivered to the Pegasus Mail directories automatically. You send mail simply but putting the output files into the Mercury/32 mail spool directory. This is accomplished automatically with a Pegasus Mail User Defined Gateway.

6. If you want to use other POP3/IMAP4 clients like Outlook,
    OE, Thunderbird, point the client at the at your Mercury/32
    host as a POP3/IMAP4 and SMTP host using the Pegasus Mail username
    and password to pickup the mail.

You can do a complete inbound and outbound mail archive with this setup using a simple Mercury/32 "Always" filter that put a copy in a users mail directory.

>
>
>
> Regarding the graphic - I'm sorry, I'm used to broadband connections
> and forget this is not standard in many places. I'm surprised
> you had difficulty reading it, I had no problems reading it when I
> clicked the thumbnail on a 19" monitor here. However, I'll
> post ASCII text from now on :)

But that's the point, you had to click on it and open it someplace else. The ASCII text requires nothing and it's in the e-mail as well. ;-)

>
>

&gt; Thanks for the reply, Thomas. &gt; &gt; So, is there anything we can do to preserve settings?Make sure that all users have full rights to their HOME and NEW mail directory and make sure you change nothing at the server level when WinPMail is running.&nbsp; The configuration file is saved at closing and if you make a change it will probably be lost. &gt; &gt; You also mention 'clients&nbsp;running shortcuts to the WinPMail version &gt; on the server'. What do you mean by this? Do you mean that the &gt; client starts Pegasus Mail from a server? We've never done this, so &gt; if that is what you mean, I'm interested to find out what the &gt; correct procedure is for doing that, especially if it will help &gt; eliminate this problem. Here's the basic process.&nbsp; The programs are only installed once on the server.&nbsp; The users just run a shortcut.&nbsp; Makes this very easy to maintain.&nbsp; I've used the default directories for Pegasus Mail here, you can change them but I would recommend maintaining the 8 character limit. 1.&nbsp; Install WinPmail in the multiuser mode on the "server".&nbsp; Use &nbsp;&nbsp;&nbsp; c:\pmail for the program; c:\pmail\mail for the mail &nbsp;&nbsp;&nbsp; directories. 2.&nbsp; Run PCONFIG.exe from the program directory and change the &nbsp;&nbsp;&nbsp; HOME and NEW mail directory specification to the &nbsp;&nbsp;&nbsp; \\server\vol\pmail\mail\~8 format. 3.&nbsp; Go to the remote workstations and install a shortcut to the &nbsp;&nbsp;&nbsp; common program. Ok, now you have the basic mail system setup.&nbsp; You can send mail to each other using Pegasus Mail. 4.&nbsp; Install Mercury/32 on this same server pointing to the Pegasus &nbsp;&nbsp;&nbsp; Mail directory structure.&nbsp; Use MercuryD, MercuryS, MercuryC at &nbsp;&nbsp;&nbsp; least. Use \\server\vol\mercury\queue for the mail spool directory. 5.&nbsp; Point MercuryD at all of your POP3 mailboxes to download the mail &nbsp;&nbsp;&nbsp; to your Pegasus Mail user directories. You now can send and receive Internet mail via Pegasus Mail.&nbsp; The mail is delivered to the Pegasus Mail directories automatically.&nbsp; You send mail simply but putting the output files into the Mercury/32 mail spool directory.&nbsp; This is accomplished automatically with a Pegasus Mail User Defined Gateway. &nbsp; 6.&nbsp; If you want to use other POP3/IMAP4 clients like Outlook, &nbsp;&nbsp;&nbsp; OE, Thunderbird, point the client at the at your Mercury/32 &nbsp;&nbsp;&nbsp; host as a POP3/IMAP4 and SMTP host using the Pegasus Mail username &nbsp;&nbsp;&nbsp; and password to pickup the mail. You can do a complete inbound and outbound mail archive with this setup using a simple Mercury/32 "Always" filter that put a copy in a users mail directory. &nbsp; &gt; &gt; &nbsp; &gt; &gt; Regarding the graphic - I'm sorry, I'm used to broadband connections &gt; and forget this is not standard in many places. I'm surprised &gt; you&nbsp;had difficulty reading it, I had no problems reading it when I &gt; clicked the thumbnail&nbsp;on a 19" monitor here. However,&nbsp;I'll &gt; post&nbsp;ASCII text from now on :) But that's the point, you had to click on it and open it someplace else.&nbsp; The ASCII text requires nothing and it's in the e-mail as well.&nbsp; ;-) &gt; &gt;

Greenman

posted Jan 31 '08 at 6:35 pm

Thomas, that is a very useful post. We have always installed PM locally, so I'll follow your instructions, and hopefully (I'm sure) this will eliminate the problem.

Thanks![Y]

Thomas, that is a very useful post. We have always installed PM locally, so I'll follow your instructions, and hopefully (I'm sure) this will eliminate the problem. Thanks![Y]

Greenman

posted Feb 1 '08 at 11:27 am

Additional info:

The reason we installed locally was because we have two email domains. This means that when running pconfig.exe we had to define a different gateway on two sets of computers (the two sets of staff who use the different domains do not use the other domain users PC's). Also, we first started using Pegasus in the mid 90's and serving applications across the network were generally avoided to minimise network congestion (we used to use 10Mb BNC cabling). Even though our network is now using CAT5 100Mb cables, I guess we just got into the habit of persisting with a local installation, especially as we have two domains.

So, if I may, I would like to run our proposed setup by you and see if you or anyone else have any recommendations.

All mailboxes are located on one server. This server also hosts the company data, and is accessed all day by up to 30 clients. The mailboxes have been copied between servers several times over the years, but Pegasus Mail has not been installed on the present server.

Located on the same server is Mercury32. This uses SMTP only (POP3 is not used). This works fine with everything.

Originally, all mail accounts used the person's first name only. We recently took advantage of Mercury's synonyms file which takes the form 'firstname.lastname@domain.com == firstname' to bring us into the 21st century.

So, as there are two domains we were wondering if we would need to install Pegasus Mail in two locations and run pconfig.exe on each installation to configure the gateway for each domain. Or, will the synonyms file, synonyms.mer, automatically format the gateway each time mail is sent. We do not want greenman@goodguy.com being sent as greenman@badguy.com.

What do you think?

Any suggestions welcome.

Additional info: The reason we installed locally was because we have two email domains. This means that when running pconfig.exe we had to define a different gateway on two sets of computers (the&nbsp;two sets of staff&nbsp;who use the different domains do not use the other domain users PC's).&nbsp;Also, we first started&nbsp;using Pegasus&nbsp;in the&nbsp;mid 90's and&nbsp;serving applications across the network were generally avoided&nbsp;to minimise network congestion (we used to use 10Mb&nbsp;BNC cabling). Even though our network is now using CAT5 100Mb cables, I guess we just got into the habit of persisting with a local installation, especially as we have two domains. So, if I may, I would like to run our proposed setup by you and see if you or anyone else&nbsp;have any recommendations. All mailboxes are located on one server. This server also hosts the company data, and is accessed all day by up to 30 clients. The mailboxes have been copied between servers several times over the years, but Pegasus Mail has not been installed on the present server. Located on the same server is Mercury32. This uses SMTP only (POP3 is not used). This works fine with everything. Originally, all mail accounts used the person's first name only. We recently took advantage of Mercury's synonyms file which takes the form '<A href="mailto:'firstname.lastname@domain.com">firstname.lastname@domain.com</A> == firstname' to bring us into the 21st century. So, as there are two domains we were wondering if we would need to install Pegasus Mail in two locations and run pconfig.exe on each installation to configure the gateway for each domain. Or, will the synonyms file, synonyms.mer, automatically format the gateway each time mail is sent. We do not want <A href="mailto:greenman@goodguy.com">greenman@goodguy.com</A> being sent as <A href="mailto:greenman@badguy.com">greenman@badguy.com</A>. What do you think? Any suggestions welcome.

Thomas R. Stephenson

posted Feb 1 '08 at 4:54 pm

> Additional info:
>
> The reason we installed locally was because we have two email
> domains. This means that when running pconfig.exe we had to define a
> different gateway on two sets of computers (the two sets of
> staff who use the different domains do not use the other domain
> users PC's). Also, we first started using Pegasus in the mid 90's
> and serving applications across the network were generally
> avoided to minimise network congestion (we used to use 10Mb BNC
> cabling). Even though our network is now using CAT5 100Mb cables, I
> guess we just got into the habit of persisting with a local
> installation, especially as we have two domains.

Two network installations of Pegasus mail, each with their own queue would work. Actually you can have two completely separate instances of Mercury/32 and Pegasus Mail running on the server as well. They could even each be running their own IP address with two NICs installed on the system.

>
> So, if I may, I would like to run our proposed setup by you and see
> if you or anyone else have any recommendations.
>
> All mailboxes are located on one server. This server also hosts the
> company data, and is accessed all day by up to 30 clients. The
> mailboxes have been copied between servers several times over the
> years, but Pegasus Mail has not been installed on the present
> server.

Each domain could have their own mailbox structure quite easily. Could be a problem if some people are in both domains.

>
> Located on the same server is Mercury32. This uses SMTP only (POP3
> is not used). This works fine with everything.

I assume here you mean it both sends and receives SMTP. Are both domains hosted at the same IP address?

>
> Originally, all mail accounts used the person's first name only. We
> recently took advantage of Mercury's synonyms file which takes the
> form 'firstname.lastname@domain.com == firstname' to bring us into
> the 21st century.
>
> So, as there are two domains we were wondering if we would need to
> install Pegasus Mail in two locations and run pconfig.exe on each
> installation to configure the gateway for each domain. Or, will the
> synonyms file, synonyms.mer, automatically format the gateway each
> time mail is sent. We do not want greenman@goodguy.com being sent as
> greenman@badguy.com.

The sending address is controlled by the synonyms if you are using the ~L~L~n@domain.com in the UDG setup. The ~L~L says first look for a synonym for this sender. If one is found use it, if none if found use the username@domain. Personally though I use "~p"<~r> in the UDG setup and then set a "Reply to" address for all users and each identity. The ~r says use this reply to address to create the From: field. Works quite well for me.

>
> What do you think?
>
> Any suggestions welcome.

It would help a lot if you were to supply the actual data so we could provide more specific help. For example my primary domain is tstephenson.com and there are a couple of other domains ubunto-tstephenson.com and novelltstephenson.com that share the same IP address. The primary Mercury/32 server receives all mail for each domain but delivers mail for novelltstephenson.com and ubunto-tstephenson.com to "domain" user accounts. The instances of Mercury/32 on the Linux and Netware systems pull the mail via MercuryD and deliver the mailto the users based on the X-Envelope-To: header. Works like a charm.

>

&gt; Additional info: &gt; &gt; The reason we installed locally was because we have two email &gt; domains. This means that when running pconfig.exe we had to define a &gt; different gateway on two sets of computers (the&nbsp;two sets of &gt; staff&nbsp;who use the different domains do not use the other domain &gt; users PC's).&nbsp;Also, we first started&nbsp;using Pegasus&nbsp;in the&nbsp;mid 90's &gt; and&nbsp;serving applications across the network were generally &gt; avoided&nbsp;to minimise network congestion (we used to use 10Mb&nbsp;BNC &gt; cabling). Even though our network is now using CAT5 100Mb cables, I &gt; guess we just got into the habit of persisting with a local &gt; installation, especially as we have two domains. Two network installations of Pegasus mail, each with their own queue would work.&nbsp; Actually you can have two completely separate instances of Mercury/32 and Pegasus Mail running on the server as well.&nbsp; They could even each be running their own IP address with two NICs installed on the system. &gt; &gt; So, if I may, I would like to run our proposed setup by you and see &gt; if you or anyone else&nbsp;have any recommendations. &gt; &gt; All mailboxes are located on one server. This server also hosts the &gt; company data, and is accessed all day by up to 30 clients. The &gt; mailboxes have been copied between servers several times over the &gt; years, but Pegasus Mail has not been installed on the present &gt; server. Each domain could have their own mailbox structure quite easily.&nbsp; Could be a problem if some people are in both domains. &gt; &gt; Located on the same server is Mercury32. This uses SMTP only (POP3 &gt; is not used). This works fine with everything. I assume here you mean it both sends and receives SMTP.&nbsp; Are both domains hosted at the same IP address? &gt; &gt; Originally, all mail accounts used the person's first name only. We &gt; recently took advantage of Mercury's synonyms file which takes the &gt; form 'firstname.lastname@domain.com == firstname' to bring us into &gt; the 21st century. &gt; &gt; So, as there are two domains we were wondering if we would need to &gt; install Pegasus Mail in two locations and run pconfig.exe on each &gt; installation to configure the gateway for each domain. Or, will the &gt; synonyms file, synonyms.mer, automatically format the gateway each &gt; time mail is sent. We do not want greenman@goodguy.com being sent as &gt; greenman@badguy.com. The sending address is controlled by the synonyms if you are using the ~L~L~n@domain.com in the UDG setup.&nbsp; The ~L~L says first look for a synonym for this sender.&nbsp; If one is found use it, if none if found use the username@domain.&nbsp; Personally though I use "~p"&lt;~r&gt; in the UDG setup and then set a "Reply to" address for all users and each identity.&nbsp; The ~r says use this reply to address to create the From: field.&nbsp; Works quite well for me. &gt; &gt; What do you think? &gt; &gt; Any suggestions welcome.&nbsp;It would help a lot if you were to supply the actual data so we could provide more specific help.&nbsp; For example my primary domain is tstephenson.com and there are a couple of other domains ubunto-tstephenson.com and novelltstephenson.com that share the same IP address.&nbsp; The primary Mercury/32 server receives all mail for each domain but delivers mail for novelltstephenson.com and ubunto-tstephenson.com to "domain" user accounts.&nbsp; The instances of Mercury/32 on the Linux and Netware systems pull the mail via MercuryD and deliver the mailto the users based on the X-Envelope-To: header.&nbsp; Works like a charm. &gt;

Greenman

posted Feb 4 '08 at 4:45 pm

Thanks, Thomas.

We do not host the mail domains. We do use POP3, but what happens at present is that we edited the MX records for the two domains so that all mail destined for the POP3 boxes is passed onto MessageLabs' servers. MessageLabs then pass it to our static IP address, where Mercury picks it up. Yes, we use SMTP both ways. Although we have mail arriving that is addressed to two domains, there is just one set of mailboxes. So, we have a PMAIL folder, and off that are the sub-folders (mailboxes) for all staff.

The reason for two domains is that the company is split into two. So, although all the installations of Pegasus Mail point to the same mailbox ..\PMAIL\ the gateways on the two sets of PC's are different.

We have just one public IP address which is assigned to a router. FTP, SMTP, IMAP etc traffic is then forwarded to the appropriate server on the network. The Windows Active Directory domain does not reflect the mail domains at all.

Therefore: Windows Active Directory domain = htlincs.local

Mail domains = apsarchaeology.co.uk and lincsheritage.org

All staff belong to htlincs.local, and it is only in the two separate Pegasus Mail gateways that the distinction is made between apsarchaeology and lincsheritage. The Mercury server announces itself as apsarchaeology.co.uk and we added an A Record to the apsarchaeology.co.uk domain that points to our public IP address to eliminate 550 verification errors.

Thanks, Thomas.&nbsp; We do not host the mail domains. We do use POP3, but what happens at present is that we edited the MX records for the two domains so that&nbsp;all mail destined for the POP3 boxes is passed onto MessageLabs' servers. MessageLabs then pass it to our static IP address, where Mercury picks it up.&nbsp;Yes, we use SMTP both ways.&nbsp;Although we have mail&nbsp;arriving that is addressed&nbsp;to two domains, there is just one set of mailboxes. So, we have a PMAIL folder, and off that are the sub-folders (mailboxes)&nbsp;for all staff. The reason for two domains is that the company is split into two. So, although all the installations of Pegasus Mail point to the same mailbox ..\PMAIL\ the gateways on the two sets of PC's are different. We have just one public&nbsp;IP address which is assigned to a router. FTP, SMTP, IMAP etc traffic is then forwarded to the appropriate server on the network. The Windows Active Directory&nbsp;domain does not reflect the mail domains at all. Therefore: Windows Active Directory domain = htlincs.local Mail domains = apsarchaeology.co.uk and lincsheritage.org All staff belong to htlincs.local, and it is only in the two separate Pegasus Mail gateways that the distinction is made between apsarchaeology and lincsheritage. The Mercury server announces itself as apsarchaeology.co.uk and we added an A Record to the apsarchaeology.co.uk domain that points to our public IP address to eliminate 550&nbsp;verification errors.

Greenman

posted Feb 6 '08 at 4:17 pm

Hi

I installed Pegasus Mail in the pmail folder that contains the user mailboxes on the server. I created a new synonyms file so that my address was changed to the second domain. A copy of the changed synonyms file exists in the PMAIL folder that also contains the mailboxes and in the Mercury folder. I next used pconfig.exe in the PMAIL folder and made sure that the reply address format was set to ~L~L~n@. I setup a shortcut to the winpm-32.exe located in the same PMAIL folder.

I've tried to send mail but it does not get past Mercury32. When the mail is passed onto Mercury, Mercury generates an error:

--- Problems not related to specific addresses in the message:

Job has invalid or illegal from address.

*** greenman@btinternet.com (this is the address to which the mail is being sent)

immediately followed by:

*** "greenman" greenman@lincsheritage.org

User "greenman" greenman@lincsheritage.org not known at this

site.

My normal address is greenman@apsarchaeology.co.uk

Does anyone know what I am doing wrong?

Thanks

Hi I installed Pegasus Mail in the pmail folder that contains the user mailboxes on the server. I created a new synonyms file so that my address was changed to the second domain. A copy of the changed synonyms file exists in the PMAIL folder that also contains the mailboxes and in the Mercury folder. I next used pconfig.exe in the PMAIL folder and made sure that the reply address format was set to ~L~L~n@. I setup a shortcut to the winpm-32.exe located in the same PMAIL folder. I've tried to send mail but it does not get past Mercury32. When the mail is passed onto Mercury, Mercury generates an error: --- Problems not related to specific addresses in the message: Job has invalid or illegal from address. *** <A href="mailto:greenman@btinternet.com">greenman@btinternet.com</A> (this is the address to which the mail is being sent) immediately followed by: &nbsp; *** "greenman" <A href="mailto:greenman@lincsheritage.org">greenman@lincsheritage.org</A> User "greenman" <A href="mailto:greenman@lincsheritage.org">greenman@lincsheritage.org</A> not known at this site. &nbsp; My normal address is <A href="mailto:greenman@apsarchaeology.co.uk">greenman@apsarchaeology.co.uk</A> Does anyone know what I am doing wrong? Thanks &nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history