how to configure in non netware mode

gac

posted Oct 19 '10 at 9:37 am

I assume you found the answer to the first question, if not simply click on help in Manage Local Users

To automatically run Pegassus for a specific user, add -I username to the shortcut

(thats a capital i)

I assume you found the answer to the first question, if not simply click on help in Manage Local UsersTo automatically run Pegassus for a specific user, add -I username to the shortcut (thats a capital i)

bstiefel

posted Oct 15 '10 at 5:04 pm

currently running pegasus from shared directory, in netware native mode, reconfiguring to non netware, with mercury as mail server

I have pegasus running from a shared directory on server, can I still run it that way, or must it be installed on each machine locally.

How do I point the clients to the mail directory located on the server?

currently running pegasus from shared directory, in netware native mode, reconfiguring to non netware, with mercury as mail server &nbsp; &nbsp; I have pegasus running from a shared directory on server, can I still run it that way, or must it be installed on each machine locally. &nbsp; How do I point the clients to the mail directory located on the server? &nbsp;

Thomas R. Stephenson

posted Oct 16 '10 at 1:37 am

> currently running pegasus from shared directory, in netware native mode, reconfiguring to non netware, with mercury as mail server
>
> I have pegasus running from a shared directory on server, can I still run it that way, or must it be installed on each machine
> locally.
>
> How do I point the clients to the mail directory located on the server?

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.

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.

&gt; currently running pegasus from shared directory, in netware native mode, reconfiguring to non netware, with mercury as mail server &gt; &gt; I have pegasus running from a shared directory on server, can I still run it that way, or must it be installed on each machine &gt; locally. &gt; &gt; How do I point the clients to the mail directory located on the server? 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. &nbsp; 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 &nbsp;&nbsp;&nbsp; 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.

bstiefel

posted Oct 18 '10 at 6:36 am

Thanks

definatly got me on the road to getting the system migrated. I think I have one only issue left.

I have to go under user management and add each user manually

is personal supposed to be the internet name of the user?

is there anyway to get around the user being prompted for what there username is when pegasus starts

or do I need to install each user local to the workstation and point it to the users mail home directory

thank you

Thanks definatly got me on the road to getting the system migrated.&nbsp; I think I have one only issue left.&nbsp;&nbsp; &nbsp; I have to &nbsp;go under user management and add each user manually &nbsp;is personal supposed to be the internet name of the user? &nbsp;is there anyway to get around the user being prompted for what there username is when pegasus starts &nbsp; or do I need to install each user local to the workstation and point it to the users mail home directory &nbsp; thank you

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history