> Does anyone have a good set of instructions on how to setup Mercury mail and Pagasus mail for an intranet? I want to put it on a Windows
> 2003 server and have about 10 people (each on their own computer with dynamic ip addresses) use it for intranet mail. I hope someone has
> good instructions or has done this and can tell me how to implement this.
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 WinPMail 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 usernames. You can setup the Pegasus Mail POP3/IMAP4 for external 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 maintain other POP3/IMAP4 clients, point the client at the at your Mercury/32 host as a POP3 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.
When I was trying to get it setup, questions that arose.
Core Module:
> - intranet name for server
If none of the mail ever leaves the local internal LAN this can be most anything you want. Mercury.kevin.com will work. If some could ever get to the outside world this need to be a real domain.
> - local domains
There ,must be at least one domain so that Mercury knows what is a local domain. The [Domains] section of the Mercury.ini would look like this.
[Domains]
Mercury : Mercury
Mercury : Mercury.kevin.com
With this setup mail to kevin@mercury.kevin.com would go to the new mail directory of user Kevin.
> Pegasus Mail:
>
> - My Internet email address is?
Kevin@mercury.kevin.com
> - smtp: server host name
The IP address of the Mercury server will work.
> - other setting?
???
<p>&gt; Does anyone have a good set of instructions on how to setup Mercury mail and Pagasus mail for an intranet?&nbsp; I want to put it on a Windows
&gt; 2003 server and have about 10 people (each on their own computer with dynamic ip addresses) use it for intranet mail. I hope someone has
&gt; good instructions or has done this and can tell me how to implement this.
1.&nbsp; Install WinPmail in the multiuser mode on the "server".&nbsp; Use c:\pmail for the program; c:\pmail\mail for the mail directories.
2.&nbsp; Run PCONFIG.exe from the WinPMail program directory and change the HOME and NEW mail directory specification to the \\server\vol\pmail\mail\~8
&nbsp;&nbsp;&nbsp; format.
3.&nbsp; Go to the remote workstations and install a shortcut to the common program.
Ok, now you have the basic mail system setup.&nbsp; You can send mail to each other using Pegasus Mail usernames.&nbsp; You can setup the Pegasus Mail POP3/IMAP4 for external mail.
4.&nbsp; Install Mercury/32 on this same server pointing to the Pegasus Mail directory structure.&nbsp; Use MercuryD, MercuryS, MercuryC at least. Use
&nbsp;&nbsp;&nbsp; \\server\vol\mercury\queue for the mail spool directory.
5.&nbsp; 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.&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 maintain other POP3/IMAP4 clients, point the client at the at your Mercury/32 host as a POP3 and SMTP host using the Pegasus
&nbsp;&nbsp;&nbsp; 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.
When I was trying to get it setup, questions that arose. </p><p>Core Module:
</p><p>&gt;&nbsp; - intranet name for server
If none of the mail ever leaves the local internal LAN this can be most anything you want.&nbsp; Mercury.kevin.com will work.&nbsp; If some could ever get to the outside world this need to be a real domain.
&gt;&nbsp; - local domains
There ,must be at least one domain so that Mercury knows what is a local domain.&nbsp; The [Domains] section of the Mercury.ini would look like this.
[Domains]
Mercury : Mercury
Mercury : Mercury.kevin.com
With this setup mail to kevin@mercury.kevin.com would go to the new mail directory of user Kevin.
&gt;&nbsp; Pegasus Mail:
&gt;
&gt;&nbsp;&nbsp; - My Internet email address is?
Kevin@mercury.kevin.com
&gt;&nbsp; - smtp: server host name
The IP address of the Mercury server will work. &nbsp;
&gt;&nbsp; - other setting?
???
</p>