TLS connect failed; connected to [IP ADDRESS] - EXCHANGE SERVER 2003

About Certificates:
Our server certificates issued a certificate to the second connector specially.
Two things about certificates:
One. In the virtual server that have enabled TLS in the Access tab button in communication, it has unmarked secure channel required. We come on mark it now.
Two. We are not paying for a third license as the only possible error is the Root Certificate Authority is not an internet company (like Verisign for example).
You can see one of them: Webmail certificate: https://webmail.btsystems.com/exchange/

Any opinion more?

Then wouldn't you need your TLS 'partner' to reload your certificate.. Or maybe they have an issue with their own TLS.
Are you comfortable with checking the logs to verify?

Thanks for your interest Debuggerau:,

The virtual SMTP with TLS, not it´s making logs. (Could be here the problem?)

Other thing: the mail ponderation (into connector with TLS) it´s in 90, to any messagge will choose the option SMTP without TLS first. (maybe we have changes in ponderation)

In the queue view, you can see the smtp and connector are working, both, cause all lines are in green (with "V"), one are generated trafic (smtp without TLS), the other, the one with the TLS enabled, not.

Best regards
Scoo

A log of 2009 oct 2, in SMTP without TLS:

89.17.221.102, mail.forodigital.es, 02/10/2009, 0:01:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 16, 24, 337, 250, 0, EHLO, -,  mail.forodigital.es,
89.17.221.102, mail.forodigital.es, 02/10/2009, 0:01:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 0, 8, 0, 220, 0, STARTTLS, -, -,
89.17.221.102, mail.forodigital.es, 02/10/2009, 0:01:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 0, 8, 29, 220, 0, STARTTLS, -, -,
89.17.221.102, mail.forodigital.es, 02/10/2009, 0:01:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 16, 8, 29, 503, 997, STARTTLS, -, mail.forodigital.es,
89.17.221.102, mail.forodigital.es, 02/10/2009, 0:01:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 16, 8, 29, 240, 62, QUIT, -, mail.forodigital.es,

No worries,

It looks like it is actually making logs..

Your sending out TLS requests, but getting nothing back, did you verify that particular partner supports TLS?

Remember that Exchange 2003 is not opportunistic, and needs you to configure each partner.

Hello debuggerau,
I was waiting to my clients ask me about the problem keep on. And yesterday, and today I can confirmate the problem persist.

I have configured each domain in the connector (with TLS)

the error it´s the same of the beggining:

Hi. This is the qmail-send program at mail.forodigital.es.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<xxxxxxxx@xxxxxxxxxxx.xxx>:
TLS connect failed; connected to 62.43.192.68.
I'm not going to try again; this message has been in the queue too long.


Any idea? or how to I can marked the problem to you?

so you have the messages waiting in the queue for some time, are you able to check their status while they are still in the queue?
Cause it sounds like that SMTP host might not support your TLS..

Onething, we must solved this problems, there is not another way.
So, I can give you more information about logs.

We I have talk with the other hosting that try send us message without success, it´s the same case, not "forodigital.es", now we tested with "digitalcreativos.com" hosting company.

This hosting company have decicated servers, not can see phisical server like us. And they have given us this "error message" from his dedicated servers:
">> dig gruponicolasmercader.com MX +short
10 webmail.btsystems.com.
10 btsystem-madrid.btsystems.com.
>> dig btsystems.com MX +short
10 btsystem-madrid.btsystems.com.
10 webmail.btsystems.com.

Y el error es el siguiente: (and the error it´s the next)

Nov  5 17:07:24 hs-858 qmail: 1257437244.167954 delivery 146: deferral: TLS_connect_failed;_connected_to_62.43.192.68./

And by other part, our part, when the problem turn up we dont received any logs, BUT, we have find a log of a "SUCCESS comunication to send from his server", It´s just the fail, (SERVER EXTERNAL BTSYSTEMS TO BTSYSTEMS):
82.194.80.171, relayout02-q02.dns-servicios.com, 06/11/2009, 9:14:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 282, 37, 337, 250, 0, EHLO, -,  relayout02-q02.dns-servicios.com,
82.194.80.171, relayout02-q02.dns-servicios.com, 06/11/2009, 9:14:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 0, 50, 51, 250, 0, MAIL, -,  FROM:<administracion3@apelsl.com>,
82.194.80.171, relayout02-q02.dns-servicios.com, 06/11/2009, 9:14:52, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 390, 90, 0, 250, 0, RCPT, -,  TO:<quesosdemurcia@quesosdemurcia.com>,
82.194.80.171, relayout02-q02.dns-servicios.com, 06/11/2009, 9:14:55, SMTPSVC1, BTSYSTEM-MADRID, 62.43.192.68, 0, 4, 70, 240, 3141, QUIT, -, relayout02-q02.dns-servicios.com


*.dns-servicios.com it´s the dedicated mail server of DIGITALCREATIVOS.COM,

Please ask me any information that you need to solved, or give me any check-list that I should check.

Best regads,

Francisco G. Manchón

Sorry for "grammatical error" in the verbal time in the last post, too many tasks at once along with it is not my mother tongue cause this.

Other error from another hosting company that no could send us:
Reporting-MTA: dns; mascarat.dragonet.es
Arrival-Date: Tue, 10 Nov 2009 09:53:51 +0100

Final-Recipient: RFC822; sofia@detalles3.com
Action: failed
Status: 4.4.7
Diagnostic-Code: SMTP; 403 4.7.0 TLS handshake failed.
Last-Attempt-Date: Tue, 10 Nov 2009 10:25:01 +0100

-----------------------------------
Best regards

Estimated debuggerau, and Expert exchange Team,
I find a question with a error that it´s seem like ours, in this question (from expert-exchange):
"403 4.7.0 TLS Handshake Failed--exchange 2003 server error"
The solution it´s this:
michaellundgren:This can happend if you have a certificate installed on your default SMTP server.
To resolve this you can remove thee certificate on the SMTP virtual server. (you can still use the certificate on your HTTP virtual server to secure OWA.)

Regards,
Michael Lundgren
--------------------------------------------------
I can not understand the solution:  If We remove thee certificate on the SMTP virtual server, the owa could no work, is´nt It?
You  give me a hand, the time resolution of this incidence is exhausting me. I think, but google search it´s a common problem: TLS, receiveing email problems, 403 4.7.0 TLS Handshake Failed--exchange 2003 server error... It must be localizated the generic problem, or We must be near of solution.

Best Regards and sorry if the last comment I post very hard, but my only objetive it´s find the solution and post it.
Francisco

Francisco