Point taken...I have re-installed with these corrections...now I am working on getting the relay to internet address working.
Thanks.
I have spent a couple of hours trying to get Outlook Express to use Mercury as a mail server. Any help would be appreciated...in advance.
Yesterday (July 5, 2012) I downloaded the latest version for Windows and installed it without incident, but try as I may I have been unable to get past the socket, etc...errors when sending/receiving.
I've read numerous posts that touch on the subject but nothing that seems to address the specifics of the problem or process of basic configuration. I have placed screen shots of the Outlook and Mercury configuration at the following link. ( http://dev.bnibooks.com/mercuryDocument.rtf )
I am running Mercury on an XP Pro SP3 box with 1 Gig of ram at 192.168.1.16. I can ping the Mercury server from other locations on the network and I can telnet into the server but I am missing something obvious.
Thanks.
You haven't explained how you are intending to use the server - internal mail only, or internet, because your configuration won't work properly outside your own network.
Also, on the OE configuration you need to remove both the checkmarks about 'authentication'.
Have you allowed Mercury in the firewall? Check that by using telnet from another machine and type 'telnet 192.168.1.16 110' at the command prompt. If Mercury responds then OE should be able to connect to get mail.
Not sure exactly what you are trying to do here. bnivistalocal.com is as far as I can see not a real domain, and you have only listed the private LAN IP address in local domain configuration. Host names in Core and MercuryS are not domain related either. This means that Mercury will be restricted to work in the local network only. If you ever make the server reachable from the Internet it's critical that you deny SMTP relaying (MercuryS configuration, Relaying control).
In domain configuration just use one name for the server (bnivistalocal or frontdesk).
The connection from Outlook Express is using the POP3 protocol. Is the POP3 server module (MercuryP) activated? If it is you can check the log file to see what is happening server-side when OE tries to connect.
/Rolf
I will be using the server for local and Internet email. I just noticed what may be part of my problem.
There is no window for pop3 server. In the Mercury control windows there are only 3 windows.
I was following the instructions I found at http://www.tech2all.com/2006/03/12/how-to-setup-your-own-e-mail-server/ which seemed to be more comprehensive than the others I've seen...did not say anything about mercury/p. Probably a later version.
I will re-install and report back with the other changes suggested.
Thanks.
It was the absense of the pop3 server. It's working now.
BTW...I did try re-installing with the mercury/p option and that still did not activate the pop3 server. I had to perform a new install and use a different folder to get around it.
Thanks for your help...everyone.
[quote user="ajaxon98"]I was following the instructions I found at http://www.tech2all.com/2006/03/12/how-to-setup-your-own-e-mail-server/ which seemed to be more comprehensive than the others I've seen[/quote]
These instructions date from 2006 and have some fundamental flaws in the set-up paragraphs:
3. Not a good idea to use "c:\progam files\" as the root folder on modern Windows as you may be prevented from writing to the folders - use "c:\Mercury" or similar.
7. MercuryC is usually an easier option than MercuryE these days - use your ISP's relay as so many people block port 25 from standard IP addresses.
9. No! Relaying should be "Strict" - never "None", unless you want to get on an internet block list!
