Moved:

http://community.pmail.com/forums/13101/ShowThread.aspx#13101

I am running a web design developing machine on WinXP sp3, connected with a U.S. Robotics Maxg router, also installed Zone Alarm Pro (as firewall) and have installed Mercury/32 v. 4.62 along with Mozilla Thunderbird v. 2.0.0.16, in order to test email transactions in my local machine. I have added the 'example.com' domain name in my server (i.e. I see it as www.example.com), I have created some local users accounts in Mercury, and when I try to send an email from Thunderbird, the email is sent but is not delivered to the other end. The MercuryE SMTP client reports every once in a while:
"Resolves MX for 'example.com' to 208.77.188.166
Connecting to 208.77.188.166
Connection error"
so I guess that's the root of the problem. I have checked telnet to localhost 25 and to localhost 110 and both are ok.

My configuration parameters are:
MercuryE SMTP Client>>Identify myself box: empty, Name servers: 192.168.1.1 (this is the IP address of my router)
MercuryS SMTP Server>>have uncheched the box "Do not permit SMTP relaying of non-local mail" in Connection Control tab, and Announce myself box: empty. (all the rest settings have been left default)

I have searched a lot in the web but still I haven't found any clue. I appreciate any help.

example.com is a real domain that resolves to that IP address (but it won't accept mail).

For your test, try putting example.com in the local domains section, or use your own domain or ip address - like [127.0.0.1]

Actually what I forgot to say in my initial post is that I am also running WAMP server (Apache/mysql/php) and I have already set up a local domain (example.com) by editing the file 'C: \WINDOWS\system32\dr ivers\etc\hosts' and adding the following lines:

127.0.0.1 www.example.com # For browser access
127.0.0.1 mail.example.com # For email access
127.0.0.1 example.com # For mercury mail server

Also I configured Apache to accept connections for any requests to the domain - http://www.example.com, instead of allowing such connections to go through the Internet . Finally, I configured Mercury mail server to use the new domain (by renaming the 'myname' parameter from 'localhost' to 'example.com' in the mercury.ini file (following instructions for setting up an open source e-commerce system / Zen cart). Through a browser, when I hit www.example.com it gets me to the wamp server welcome screen. Nevertheless, I get the above connection error with MercuryE SMTP client module.

So I guess I have done the step that you recommended to me, unless I miss something.

Below I pasted some log files info:

log from MercuryS:

T 20080913 170259 48cbec95 Connection from 127.0.0.1
T 20080913 170259 48cbec95 EHLO [127.0.0.1]
T 20080913 170259 48cbec95 MAIL FROM:<storekeeper@example.com> SIZE=1281
T 20080913 170259 48cbec95 RCPT TO:<alan@example.com>
T 20080913 170259 48cbec95 DATA
T 20080913 170259 48cbec95 DATA - 39 lines, 1281 bytes.
T 20080913 170259 48cbec95 QUIT
T 20080913 170259 48cbec95 Connection closed with 127.0.0.1, 0 sec. elapsed.

 and log from MercuryE:

W 20080913 171439 48cbc29b Error connecting to primary server '208.77.188.166'.
E 20080913 171439 48cbc29b Processing of job MO000002 incomplete or failed.
T 20080913 171439 48cbc29b Job MO000002 processing complete.

the Mercury Core Process window gave me :

Sat 13, 17:02:59. Job MG001C0B: from storekeeper@example.com (non-local)
Created outgoing job with ID MO001C0C
To : alan@example.com (non-local) -OK

I wonder if that "(non-local)" is the culprit.... and why is it considered as non-local since I added it as a local domain?

Mail for example.com should not be going to the outbound queue.  Show us the {domains] section of the mercury.ini file.  It should look something like

[Domains]
# NetWare Server           Domain name
[192  :  [192
[192  :  [192.168.1.2]

( 192.168.1.2 is my local host)

[Domains]
# NetWare Server           Domain name
[192  :  [192
[192  :  [192.168.1.2]

( 192.168.1.2 is my local host)

I assume you are trying to deliver mail to a local user called Alan on the Mercury/32 server to be picked up by T-bird using POP3 or IMAP4.  Try sending mail to Alan@[192.168.1.2] and you will find it is delivered to the local user Alan.  You really should put 192 : example.com here as well since example.com is a real domain but it does not accept mail.   Personally with this setup I would use something other than example.com for testing.

I added the line "192 : example.com" below the [Domains] section in mercury.ini but I get the same error. Excuse me for my unfamiliarity with the emailing "mechanics", I just dont understand why 'example.com' should be a problem since it is declared as local domain in the windows hosts file. Below are the lines from the windows hosts file.

127.0.0.1       localhost
127.0.0.1 www.example.com # For browser access
127.0.0.1 mail.example.com # For email access
127.0.0.1 example.com # For mercury mail server

Besides, I have been following the Zen cart book instructions in order to setup a local email server that will be working along with zen cart. Why do the instructions use the 'example.com' domain? So, do you suggest that I replace 'example.com' with another domain name? And what would that be? Anything I can think of, given that it does not exist?

Mercury won't check the Windows hosts file to determine what domains are local, you have to specify that in Mercury core configuration. To make it simple, why not use "server" as server name, as in Thomas' example? "[192" seems confusing.

My guess is that "example.com" is intended as an example, not a suggestion for something to actually use. So until you have a real domain name you could try with something like "test.local".

/Rolf

ok, thanks everybody for your help. I'll try it out as you suggested and let you know...

so.....I changed the example.com to test.local in the following steps (excuse me if I have not understood something): 

In the Windows host file:
127.0.0.1       localhost
127.0.0.1 www.test.local # For browser access
127.0.0.1 mail.test.local # For email access
127.0.0.1 test.local # For mercury mail server

In the Apache httpd.conf file:
ServerName www.test.local:80
(so, when I input the www.test.local address in my browser, it takes me indeed to the WAMP server welcome screen, again)

and in the Mercury.ini file:
in the section [General]
myname:          test.local    # Canonical name for this server
and in the section [Domains]

[192  :  [192
[192  :  [192.168.1.2]
server : server
server : [192.168.1.2]
server : test.local

I also created new email accounts in Thunderbird (e.g. alan@test.local, storekeeper@test.local, etc) and tried to send email from storekeeper@test.local to alan@test.local. I got a "Permanent error 11001 (non-existent host or domain) resolving "test.local" in the SMTP client and in the SMTP server log :
T 20080913 200158 48cc1b0e Connection from 127.0.0.1
T 20080913 200158 48cc1b0e EHLO [127.0.0.1]
T 20080913 200158 48cc1b0e MAIL FROM:<storekeeper@test.local> SIZE=336
T 20080913 200158 48cc1b0e RCPT TO:<alan@test.local>
T 20080913 200158 48cc1b0e DATA
T 20080913 200158 48cc1b0e DATA - 11 lines, 336 bytes.
T 20080913 200158 48cc1b0e QUIT
T 20080913 200158 48cc1b0e Connection closed with 127.0.0.1, 0 sec. elapsed.

(The "funny" thing is that SMTP Client continues trying to access example.com domain, reporting a connection error (have I forgotten to delete it from somewhere?)  )

I am not sure if I have the things right in the [Domains] section of the mercury.ini file.

[192  :  [192
[192  :  [192.168.1.2]
server : server
server : [192.168.1.2]
server : test.local

I would make this  simply

server : server
server : [192.168.1.2]
server : test.local

 I also created new email accounts in Thunderbird (e.g. alan@test.local,

storekeeper@test.local, etc) and tried to send email from

storekeeper@test.local to alan@test.local. I got a "Permanent error

11001 (non-existent host or domain) resolving "test.local" in the SMTP

client

Use 192.168.1.2 for the host name in T-bird and it will not have a problem.

and in the SMTP server log :
T 20080913 200158 48cc1b0e Connection from 127.0.0.1
T 20080913 200158 48cc1b0e EHLO [127.0.0.1]
T 20080913 200158 48cc1b0e MAIL FROM:<storekeeper@test.local> SIZE=336
T 20080913 200158 48cc1b0e RCPT TO:<alan@test.local>
T 20080913 200158 48cc1b0e DATA
T 20080913 200158 48cc1b0e DATA - 11 lines, 336 bytes.
T 20080913 200158 48cc1b0e QUIT
T 20080913 200158 48cc1b0e Connection closed with 127.0.0.1, 0 sec. elapsed.

This is a normal delivery via SMTP 

 (The "funny" thing is that SMTP Client continues trying to access

example.com domain, reporting a connection error (have I forgotten to

delete it from somewhere?)  )

It's still trying to deliver to the example.com address.  You need to remove the MO*.QCF/QDF files from the queue directory.

There could still be messages for example.com in queue in Mercury, check the QUEUE directory and delete everything in it.

Remove the "[192" stuff from the [Domains] section, and restart Mercury. Then test.local should be recognized as a local address.

/Rolf 

ok, guys, thanks a lot for your help. Everything is working ok.

We are getting that too:

*** removed@domain.com
  Permanent error 11001 (non-existent host or domain) resolving 'domain.com'.

 This just started in the last day. Ideas?

Not sure if you are suggesting that this is a local domain issue as well? It looks more to me like a DNS problem. Can you ping www.domain.com from the server? If there is a problem with domain name resolution in Windows you can enter external name servers (the ones provided by your Internet Service Provider, usually)  by selecting Configuration / MercuryE SMTP client. If you already have name servers listed there, check that all of them still work.

/Rolf 

[quote user="Rolf Lindby"]

Not sure if you are suggesting that this is a local domain issue as well? It looks more to me like a DNS problem. Can you ping www.domain.com from the server? If there is a problem with domain name resolution in Windows you can enter external name servers (the ones provided by your Internet Service Provider, usually)  by selecting Configuration / MercuryE SMTP client. If you already have name servers listed there, check that all of them still work.

/Rolf 

[/quote]

Thanks. You are right. That machine can't get to those domains...