[quote user="davron"]When I used option one I utilized MercuryE and it worked nicely. The Name servers input was left empty. 

When I wanted to work inside my network, in MercuryE there was an error which said (in general): can not resolve the "domain" (myname@domain), so I cuntinued with your recommendation and I transfered to MercuryC.[/quote]

For sending and delivering mail entirely within your network, neither MercuryE nor MercuryC should normally come into use - Mercury should recognise that it is a local delivery because the domain name is in the list of 'Local domains', and deliver directly to the mailbox.

[quote]In the definition for the Smart host name i entered the mail server IP, and I had to enter my user name and password for authontication. Now MercuryC worked as well.

When I operated MercuryC and left Smart host name empty the program crashed. The site does not permit me to upload the printscreen of the crush, and I did not find any dump file to upload.[/quote]

MercuryC must have a hostname or (IP address) or else it can't operate.

I recently installed xampp on my pc. I opened mercury and from the menu File->Send mail message.. I am trying to send mail. In the window "Main Core Process" the outgoing is on ready.

port 25 is free. What is needed to operate the software correctly.

Any help will be apritiated. 

David

Make sure the local domains section in core configuration is correct. Read the help text about this, if you get it wrong it won't work. Set hostname to something sensible. Make sure DNS resolution works. Switch off modules you don't plan to use. Don't restrict modules to a specific network interface unless you have a good reason to do so. Verify that your Internet provider isn't blocking port 25.

If those general hints don't help we will need more information to know what is happening. If so please post log excerpts and the mercury.ini file.

/Rolf

Hi Rolf,

Thank you for your quick response, i used your hints and made some progress. 

R - Make sure the local domains section in core configuration is correct

D - What you mean by correct. The domain of the xampp is localhost 127.0.0.1. My pc gets its IP by dhcp from the company intranet DNS.

R - Set hostname to something sensible

D - I think the xampp hostname is "localhost". What is something sensible? why does it matter and where should I define it?

R - Make sure DNS resolution works

D - I put the 2 ip's of the 2 DNS servers in MercotyE. the file (TCP0006.ME) says:15:08:17.671: --- Wed Nov 10 15:08:17 2010 ---
15:08:17.671: Connect to '10.7.60.2', timeout 60.
15:08:39.671: 15: Peer connect failure

Now the port is used by Mercurymail, MercuryS recieves the mails, but they are only in pending stage in MercuryE.

David

Thank you for your quick response, i used your hints and made some progress. 

R - Make sure the local domains section in core configuration is correct

D - What you mean by correct. The domain of the xampp is localhost

127.0.0.1. My pc gets its IP by dhcp from the company intranet DNS.

The [Domains] section of the mercury.ini file should look something like this.

[Domains]
Localhost : localhost
Localhost; : [127.0.0.1]

This also means you cannot use MercuryE to send the mail since you do not have a fixed IP address, domain name and PTR record for the system running Mercury.

R - Set hostname to something sensible

D - I think the xampp hostname is "localhost". What is something sensible? why does it matter and where should I define it?

Configuration | Mercury core | Internet name for this system

R - Make sure DNS resolution works

D - I put the 2 ip's of the 2 DNS servers in MercotyE. the file (TCP0006.ME) says:15:08:17.671: --- Wed Nov 10 15:08:17 2010 ---
15:08:17.671: Connect to '10.7.60.2', timeout 60.
15:08:39.671: 15: Peer connect failure

Now the port is used by Mercurymail, MercuryS receives the mails, but they are only in pending stage in MercuryE.

Use Configuration | Protocols modules and change from MercuryE to MercuryC.  Close and reopen Mercury and then use Configuration | MercuryC to configure the SMTP relay host you will be using to send the mail.

Hi Thomas,

Thank you for your help.

First I would like to say that now I can send emails with Mercury.

T - This also means you cannot use MercuryE to send the mail since you do not have a fixed IP address, domain name and PTR record for the system running Mercury.

D - I can use from my PC two options of communication. One through celluar modem to ISP. Second (but not in parallel) is my connection to the local network.

When I used option one I utilized MercuryE and it worked nicely. The Name servers input was left empty. 

When I wanted to work inside my network, in MercuryE there was an error which said (in general): can not resolve the "domain" (myname@domain), so I cuntinued with your recommendation and I transfered to MercuryC.

In the definition for the Smart host name i entered the mail server IP, and I had to enter my user name and password for authontication. Now MercuryC worked as well.

When I operated MercuryC and left Smart host name empty the program crashed. The site does not permit me to upload the printscreen of the crush, and I did not find any dump file to upload.

I think mercury should be notified about the bug (should be easy to correct).

 Thank you agin

David