[quote user="jonathan"]
First of all, i don't understand or know, all i need to know about networking, etc. BUT the majority of us have our own IP addresses which are provided by our broadband ISPs. I have a home network with a few extra computers and i have always wondered... "How, do i process my own email?". Why can't i send an email to "blah@myipaddress.com" and retrieve a test email?
I challenge anyone out there to provide a guide... a "dummy" guide... which instructs the normal user on how to install Mercury/pickup email, etc.
I am lost... and this Mercury for Dummies might just sell a few more licenses!
I've really tried but there are way too many options and configurations that means that it's not all that simple. The dummy setup would be using a fixed IP address with your own domain name and DNS entry MX host entry pointing to your system running Mercury/32 and I've probably already use 2-3 terms that are not familar to you.
1. To receive mail from a single POP3 account with many users takes some knowledge as to the headers provided by the ISP. Without that your are dependend on the addresses in the body of the message and in many cases the users email address is not there.
2. To receive mail via SMTP really requires a fixed IP address but it can be done with a random IP address when using a domain from something like http://dyndns.cog.
3. To send mail via MercuryE requires both a fixed IP address and no port 25 blocking. To send via MercuryC requires a relay host that allows relaying. There are ways to get around many of these things but it does take a lot of knowledge of the SMTP mail system to make this work
That said there are a number of entries at http://kbase.pmail.gen.nz/mercury32.cfm that do provide a lot of information about the basic operation and setup of Mercury/32. You might want to check it out.
And finally here is the basic setup local lan setup for Mercury/32 and Pegasus Mail:
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.
[/quote]
[quote user="jonathan"]<blockquote><p>First of all, i don't understand or know, all i need to know about networking, etc. BUT the majority of us have our own IP addresses which are provided by our broadband ISPs. I have a home network with a few extra computers and i have always wondered... "How, do i process my own email?". Why can't i send an email to "blah@myipaddress.com" and retrieve a test email?
</p><p>I challenge anyone out there to provide a guide... a "dummy" guide... which instructs the normal user on how to install Mercury/pickup email, etc.</p><p>I am lost... and this Mercury for Dummies might just sell a few more licenses!</p></blockquote><p>I've really tried but there are way too many options and configurations that means that it's not all that simple. The dummy setup would be using a fixed IP address with your own domain name and DNS entry MX host entry pointing to your system running Mercury/32 and I've probably already use 2-3 terms that are not familar to you.
</p><p>1.&nbsp; To receive mail from a single POP3 account with many users takes some knowledge as to the headers provided by the ISP.&nbsp; Without that your are dependend on the addresses in the body of the message and in many cases the users email address is not there.
</p><p>2.&nbsp; To receive mail via SMTP really requires a fixed IP address but it can be done with a random IP address when using a domain from something like http://dyndns.cog.</p><p>3.&nbsp; To send mail via MercuryE&nbsp; requires both a fixed IP address and no port 25 blocking.&nbsp; To send via MercuryC requires a relay host that allows relaying.&nbsp; There are ways to get around many of these things but it does take a lot of knowledge of the SMTP mail system to make this work
</p><p>That said there are a number of entries at http://kbase.pmail.gen.nz/mercury32.cfm that do provide a lot of information about the basic operation and setup of Mercury/32.&nbsp; You might want to check it out.
</p><p>And finally here is the basic setup local lan setup for Mercury/32 and Pegasus Mail:</p><p>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 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 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.
</p><p>&nbsp;[/quote]</p>
