In that case you would normally get a rejection message from the server, but from your description it appears that the connection is blocked at networking level. But it could be that gmx are a bit over-ambitious in their anti-spam measures. Try contacting them about it, it might work.

/Rolf 

Hey Folks,

I'm very sorry rolling up again a connection post,

but I ran into some trouble setting up mercury/32 properly for sending

mails to external.

I am using the dyndns.com-service for

providing a static hostname to my dynamic ip. This has been configured

in the M32-setup as shown here:
http://www.tech2all.com/2006/03/12/how-to-setup-your-own-e-mail-server/
as well as in my router's configuration tabs. Also I forwarded the ports 25 and 110.

Mercury has been setup with the modules "MercuryS SMTP Server", "MercuryP POP3 Server" and "MercuryE SMTP Client". So after

figuring out how to resolve the "temporary error 249" (by adding my

router's gateway address to MercuryE Name Servers field), the target

address is resolved as following:

Connection error during handshake with 213.165.64.100.

0:17:59: processing job MO0014C8
Resolved MX for 'gmx.net' to 213.165.64.100
Connecting to 213.165.64.100
Connection error.
Attempting connection to alternate, 213.165.64.100
Connection error on alternate.

As you can see, the connection cannot be established for sending the mail. So where is the devil inside, did I miss a special config ?

I appreciate any advice or help, atm i don't see the wood for the trees...

Best

SnakeByte

Turn on session logging in MercuryE to check the detail of the response you get. (Don't forget to turn it off afterwards to save space.)  gmx may be objecting to your connection from a dynamic IP.  If that's the case, you may have to use MercuryC and relay through a host.

Hey PaulW,

 Thanks for your answer. So far I still have had activated session logging, but log's does not tell me any more information:

 General.log:

T 20081104 182128 49108458 Begin processing job MO001310 from postmaster@specops.game-server.cc
W 20081104 182229 49108458 Error connecting to primary server '213.165.64.100'.

W 20081104 182230 49108458 Error connecting to alternate server '213.165.64.100'.

E 20081104 182230 49108458 Processing of job MO001310 incomplete or failed.

Session log TCP0000.ME:

18:22:28.011: --- Tue Nov 04 18:22:28 2008 ---
18:22:28.011: Connect to '213.165.64.100', timeout 60.
18:22:29.009: --- Connection closed normally at Tue Nov 04 18:22:29 2008. ---
18:22:29.009:
18:22:29.009: --- Tue Nov 04 18:22:29 2008 ---
18:22:29.009: Connect to '213.165.64.100', timeout 60.
18:22:30.007: --- Connection closed normally at Tue Nov 04 18:22:30 2008. ---
18:22:30.007:

Well, I already tried using "MercuryC SMTP relaying client", but unless I use my registered email address @ gmx in the FROM it does not work. Setting in the From the accounted gmx-adress, mails will be relayed. But in fact that's not the goal I wanted to achieve.

Could it be that your Internet provider is blocking outgoing traffic on port 25? A lot of ISPs do that these days to stop spam. Open a command window and test connecting with Telnet to one of the mail servers in your example (telnet 213.165.64.100 25) to see what happens.

/Rolf 

Hi Rolf,

 no my provider does not block outgoing traffic on 25. It really seems it is gmx, that is objecting my traffic due to my dynamic ip. For now I am forced using the SMTP relaying client.But thanks anyway so far.

 SnakeByte