Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
I updated my AV software and the problem disappeared! Looking back, it may have started after the last AV update. Excellent, although I'm surprised anti-virus software is monitoring port 25 for outgoing email, and worse corrupting it. What make? I've had AV software corrupt FTP transfers in the past, sometimes accidentally, sometimes deliberately. The most annoying was my attempt to download a 6 gig Virtual Machine image which my hardware firewall stopped at 4 gigs when it found a development tool many AV packages consider a hacking tool. My FTP application kept repeating the download for 12 hours until I stopped it manually. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
Hi Angus, On Thu, 6 Sep 2012 08:13 +0100 (BST), you wrote: I updated my AV software and the problem disappeared! Looking back, it may have started after the last AV update. Excellent, although I'm surprised anti-virus software is monitoring port 25 for outgoing email, and worse corrupting it. What make? I've got AdAware. I was a little surprised myself. I didn't even have email checking enabled. I have to say though, it was likely my fault. The previous update that caused the problem I had trouble installing and reinstalled 3 times. It didn't really need reinstalling. I just thought it did. I've had AV software corrupt FTP transfers in the past, sometimes accidentally, sometimes deliberately. The most annoying was my attempt to download a 6 gig Virtual Machine image which my hardware firewall stopped at 4 gigs when it found a development tool many AV packages consider a hacking tool. My FTP application kept repeating the download for 12 hours until I stopped it manually. I don't run into these things often. That leaves me rather clueless when I do. Thanks so much. This was very bothersome to me. Now I can forget it :) George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
Hi Angus, On Mon, 3 Sep 2012 09:42 +0100 (BST), you wrote: Here's the problem, there's nothing more received but a connection close after around 10 seconds? Ok, now we know, how do I fix it? I have no idea. This is unlikely to be specifically an ICS issue since there is no problem on ports other than 25, you need to find out why no further data is being received. It could be firewall/anti-spam software or appliances, a router, your ISP, etc. Does it fail on multiple PCs, with different internet connections and ISPs? Thanks for the suggestions. I know from my own experience, when you can't reproduce something like this, it makes determining the problem so much more difficult, but your suggestions came at the right time. All I was looking for was a clue :) I updated my AV software and the problem disappeared! Looking back, it may have started after the last AV update. Sorry we can not be more specific, but until an issue such as this can be reliably reproduced, it can not fixed. Understandable. I very much appreciate your willingness to at least make suggestions. The only odd thing I've seen is you are using OpenSSL 1.0.0d, whereas I still use v0.9.8r which has a much longer stable history. I actually tried nearly ever version available and had the problem. I just went with the newest because it was the newest. It's fixed! Thanks so much for your reply, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
On Wed, 29 Aug 2012 17:14:21 +0200, you wrote: gjohn...@mixnym.net wrote: If it does work with port 587 it should work with port 25 the same way since both support the STARTTLS command. I've no idea why it doesn't work for you? That's been the mystery for me, Arno! Same for me, especially since both port numbers do work for me and my customers. 01:58:30:254 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [23] 02:08:29:657 022C2400 TCustomSslWSocket.Do_FD_CLOSE error #0 556 Here's the problem, there's nothing more received but a connection close after around 10 seconds? Ok, now we know, how do I fix it? I have no idea. Thanks, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
Here's the problem, there's nothing more received but a connection close after around 10 seconds? Ok, now we know, how do I fix it? I have no idea. This is unlikely to be specifically an ICS issue since there is no problem on ports other than 25, you need to find out why no further data is being received. It could be firewall/anti-spam software or appliances, a router, your ISP, etc. Does it fail on multiple PCs, with different internet connections and ISPs? Sorry we can not be more specific, but until an issue such as this can be reliably reproduced, it can not fixed. The only odd thing I've seen is you are using OpenSSL 1.0.0d, whereas I still use v0.9.8r which has a much longer stable history. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
gjohn...@mixnym.net wrote: If it does work with port 587 it should work with port 25 the same way since both support the STARTTLS command. I've no idea why it doesn't work for you? That's been the mystery for me, Arno! Same for me, especially since both port numbers do work for me and my customers. 01:58:30:254 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [23] 02:08:29:657 022C2400 TCustomSslWSocket.Do_FD_CLOSE error #0 556 Here's the problem, there's nothing more received but a connection close after around 10 seconds? -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
On Wed, 29 Aug 2012 17:14:21 +0200, you wrote: gjohn...@mixnym.net wrote: If it does work with port 587 it should work with port 25 the same way since both support the STARTTLS command. I've no idea why it doesn't work for you? That's been the mystery for me, Arno! Same for me, especially since both port numbers do work for me and my customers. 01:58:30:254 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [23] 02:08:29:657 022C2400 TCustomSslWSocket.Do_FD_CLOSE error #0 556 Here's the problem, there's nothing more received but a connection close after around 10 seconds? Ok, now we know, how do I fix it? I have no idea. Thanks, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
On Tue, 28 Aug 2012 07:18:03 +0200, you wrote: gjohn...@mixnym.net wrote: On Sun, 26 Aug 2012 09:52:14 +0200, you wrote: gjohn...@mixnym.net wrote: Demo settings: smtp.gmail.com:25 SslVerifyPeer = unchecked SSL type = Explicit(StartSssl) Hi Arno, I'm sorry to say, I couldn't run the demo in cbuilder 2007. But I put together a quick demo based on the SslMailSnd project to test for the problem. It's a very small project _only_ intended to test for failed handshake--nothing more. My demo resulted in the same problem that my program has. It fails the handshake. Here are my results. Make sure that property TSslContext-SslVersionMethod is set to sslV23_CLIENT and that you use recent SSL libraries from here ( supported version depends on the version of your source code): http://wiki.overbyte.be/wiki/index.php/ICS_Download Gee, I had hopes for that! But it still fails the handshake. Just as a test I set the port to 587 in my little demo and then the handshake succeeded. But on port 25, fails. If it does work with port 587 it should work with port 25 the same way since both support the STARTTLS command. I've no idea why it doesn't work for you? That's been the mystery for me, Arno! If the handshake still fails drop a TIcsLogger onto the form, tick all options and log the failure, post the log to this list. Well, I didn't get much: 12:51:02:198 InitCtx OpenSSL version: OpenSSL 1.0.0d 8 Feb 2011 That's it. Sorry for my bad advise. The TSslContext has a published property IcsLogger, simply assign it in object inspector. Also assign TSslSmtpClient-CtrlSocket-IcsLogger the same IcsLogger instance at runtime. I was aware I needed to assign the logger to the sslcontext, but not the ctrlsocket. When I added it to the CtrlSocket, I got a lot more: 01:58:28:984 022C2400 Socket handle created 556 01:58:28:984 TWSocket will connect to 173.194.69.108:25 01:58:29:176 022C2400 TryToSend 556 01:58:29:176 022C2400 TriggerDataSent 556 01:58:29:370 022C2400 PutDataInSendBuffer 556 len 15 [1] 01:58:29:370 022C2400 TryToSend 556 01:58:29:370 022C2400 TryToSend 556 01:58:29:370 022C2400 TriggerDataSent 556 01:58:29:567 022C2400 PutDataInSendBuffer 556 len 10 [2] 01:58:29:567 022C2400 TryToSend 556 01:58:29:567 022C2400 TryToSend 556 01:58:29:567 022C2400 TriggerDataSent 556 01:58:29:761 022C2400 StartSslHandshake 556 01:58:29:764 InitCtx OpenSSL version: OpenSSL 1.0.0d 8 Feb 2011 01:58:30:253 022C2400 InitSSLConnection 556 01:58:30:253 022C2400 BIO_ctrl(sslbio, BIO_C_SET_SSL, BIO_NOCLOSE, 0x36C6E90) = 1 [3] 01:58:30:253 022C2400 ICB SSL_CB_HANDSHAKE_START 01:58:30:253 022C2400 ICB SSL_connect: before/connect initialization 01:58:30:253 022C2400 ICB SSL_connect: SSLv2/v3 write client hello A 01:58:30:253 022C2400 ICB SSL_connect: error in SSLv2/v3 read server hello A 01:58:30:253 022C2400 BIO_read(sslbio, 0x17D42B, 0) = -1 [4] 01:58:30:253 022C2400 BIO_should_retry(sslbio) = 1 [5] 01:58:30:253 022C2400 TriggerEvent sslFdRead 556 01:58:30:253 022C2400 TriggerEvent sslFdWrite 556 01:58:30:253 022C2400 SslAsyncSelect 556, 1 FD_READ 01:58:30:253 022C2400 TCustomSslWSocket.Do_FD_READ 556 01:58:30:253 022C2400 BIO_ctrl_get_read_request(nbio) = 7 [6] 01:58:30:253 022C2400 Winsock recv( 556, 0x17DC63, 7, 0) = -1 [7] 01:58:30:253 022C2400 TriggerEvents 556 SslState: SSL_ST_INIT // MayFD_Read=0 MayDoRecv=-1 MayFD_Write=-1 MaySslTryToSend=-1 bSslAllSent=0 bAllSent=-1 01:58:30:253 022C2400 BIO_ctrl_pending(nbio) = 214 [8] 01:58:30:253 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [9] 01:58:30:253 022C2400 SslAsyncSelect 556, 2 FD_WRITE 01:58:30:253 022C2400 TCustomSslWSocket.Do_FD_WRITE 556 01:58:30:253 022C2400 BIO_ctrl_pending(nbio) = 214 [10] 01:58:30:254 022C2400 BIO_read(nbio, 0x17BC84, 214) = 214 [11] 01:58:30:254 022C2400 my_RealSend (0x22C, 188, 214) = 214 [12] 01:58:30:254 022C2400 BIO_ctrl_pending(nbio) = 0 [13] 01:58:30:254 022C2400 TriggerEvents 556 SslState: SSL_ST_INIT // MayFD_Read=0 MayDoRecv=-1 MayFD_Write=-1 MaySslTryToSend=-1 bSslAllSent=0 bAllSent=-1 01:58:30:254 022C2400 BIO_ctrl_pending(nbio) = 0 [14] 01:58:30:254 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [15] 01:58:30:254 022C2400 TCustomSslWSocket.Do_FD_WRITE 556 01:58:30:254 022C2400 BIO_ctrl_pending(nbio) = 0 [16] 01:58:30:254 022C2400 BIO_read(nbio, 0x17BC6C, 0) = 0 [17] 01:58:30:254 022C2400 TriggerEvents 556 SslState: SSL_ST_INIT // MayFD_Read=0 MayDoRecv=-1 MayFD_Write=-1 MaySslTryToSend=-1 bSslAllSent=0 bAllSent=-1 01:58:30:254 022C2400 BIO_ctrl_pending(nbio) = 0 [18] 01:58:30:254 022C2400 BIO_ctrl_get_write_guarantee(nbio) = 4096 [19] 01:58:30:254 022C2400 TCustomSslWSocket.Do_FD_WRITE 556 01:58:30:254 022C2400 BIO_ctrl_pending(nbio) = 0 [20] 01:58:30:254 022C2400 BIO_read(nbio, 0x17BC6C, 0) = 0 [21] 01:58:30:254 022C2400 TriggerEvents 556 SslState: SSL_ST_INIT // MayFD_Read=0 MayDoRecv=-1 MayFD_Write=-1
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
On Sun, 26 Aug 2012 09:52:14 +0200, you wrote: gjohn...@mixnym.net wrote: Demo settings: smtp.gmail.com:25 SslVerifyPeer = unchecked SSL type = Explicit(StartSssl) Hi Arno, I'm sorry to say, I couldn't run the demo in cbuilder 2007. But I put together a quick demo based on the SslMailSnd project to test for the problem. It's a very small project _only_ intended to test for failed handshake--nothing more. My demo resulted in the same problem that my program has. It fails the handshake. Here are my results. Make sure that property TSslContext-SslVersionMethod is set to sslV23_CLIENT and that you use recent SSL libraries from here ( supported version depends on the version of your source code): http://wiki.overbyte.be/wiki/index.php/ICS_Download Gee, I had hopes for that! But it still fails the handshake. Just as a test I set the port to 587 in my little demo and then the handshake succeeded. But on port 25, fails. If the handshake still fails drop a TIcsLogger onto the form, tick all options and log the failure, post the log to this list. Well, I didn't get much: 12:51:02:198 InitCtx OpenSSL version: OpenSSL 1.0.0d 8 Feb 2011 That's it. I enabled all log options and that's all I get. I was thinking this might be all there was to log since the handshake was failing, but when I tried it with port 587 and it succeeded, the log still had only the 1 line. I must be doing something wrong. The time on the line changes with each test. I'm sorry, I guess I need a bit more guidance. Thanks -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
gjohn...@mixnym.net wrote: On Sun, 26 Aug 2012 09:52:14 +0200, you wrote: gjohn...@mixnym.net wrote: Demo settings: smtp.gmail.com:25 SslVerifyPeer = unchecked SSL type = Explicit(StartSssl) Hi Arno, I'm sorry to say, I couldn't run the demo in cbuilder 2007. But I put together a quick demo based on the SslMailSnd project to test for the problem. It's a very small project _only_ intended to test for failed handshake--nothing more. My demo resulted in the same problem that my program has. It fails the handshake. Here are my results. Make sure that property TSslContext-SslVersionMethod is set to sslV23_CLIENT and that you use recent SSL libraries from here ( supported version depends on the version of your source code): http://wiki.overbyte.be/wiki/index.php/ICS_Download Gee, I had hopes for that! But it still fails the handshake. Just as a test I set the port to 587 in my little demo and then the handshake succeeded. But on port 25, fails. If it does work with port 587 it should work with port 25 the same way since both support the STARTTLS command. I've no idea why it doesn't work for you? If the handshake still fails drop a TIcsLogger onto the form, tick all options and log the failure, post the log to this list. Well, I didn't get much: 12:51:02:198 InitCtx OpenSSL version: OpenSSL 1.0.0d 8 Feb 2011 That's it. Sorry for my bad advise. The TSslContext has a published property IcsLogger, simply assign it in object inspector. Also assign TSslSmtpClient-CtrlSocket-IcsLogger the same IcsLogger instance at runtime. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
gjohn...@mixnym.net wrote: Demo settings: smtp.gmail.com:25 SslVerifyPeer = unchecked SSL type = Explicit(StartSssl) Hi Arno, I'm sorry to say, I couldn't run the demo in cbuilder 2007. But I put together a quick demo based on the SslMailSnd project to test for the problem. It's a very small project _only_ intended to test for failed handshake--nothing more. My demo resulted in the same problem that my program has. It fails the handshake. Here are my results. Make sure that property TSslContext-SslVersionMethod is set to sslV23_CLIENT and that you use recent SSL libraries from here ( supported version depends on the version of your source code): http://wiki.overbyte.be/wiki/index.php/ICS_Download If the handshake still fails drop a TIcsLogger onto the form, tick all options and log the failure, post the log to this list. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
On Fri, 24 Aug 2012 07:04:39 +0200, you wrote:
[snip]
Give the SslMailSnd demo a trial, it works:
220 mx.google.com ESMTP fu8sm2298248wib.5
RequestDone Rq=0 Error=0
EHLO your_name
250-mx.google.com at your service, [77.184.1.222]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
RequestDone Rq=10 Error=0
STARTTLS
220 2.0.0 Ready to start TLS
Starting SSL handshake
Secure connection with TLSv1, cipher ECDHE-RSA-RC4-SHA, 128 secret bits (128
total)
RequestDone Rq=12 Error=0
Demo settings:
smtp.gmail.com:25
SslVerifyPeer = unchecked
SSL type = Explicit(StartSssl)
Hi Arno,
I'm sorry to say, I couldn't run the demo in cbuilder 2007. But I put
together a quick demo based on the SslMailSnd project to test for the
problem. It's a very small project _only_ intended to test for failed
handshake--nothing more.
My demo resulted in the same problem that my program has. It fails
the handshake. Here are my results.
16:24:12 220 mx.google.com ESMTP gq2sm7031513bkc.13
16:24:12 RequestDone Rq=0 Error=0
16:24:12 EHLO CADILLAC
16:24:12 250-mx.google.com at your service, [72.160.14.31]
16:24:12 250-SIZE 35882577
16:24:12 250-8BITMIME
16:24:12 250-STARTTLS
16:24:12 250 ENHANCEDSTATUSCODES
16:24:12 RequestDone Rq=10 Error=0
16:24:12 STARTTLS
16:24:13 220 2.0.0 Ready to start TLS
16:24:13 Starting SSL handshake
16:34:12 Handshake done!
16:34:12 SSL Handshake failed
16:34:12 RequestDone Rq=12 Error=500
Thanks for any help you can provide.
George
I'm pasting my cbuilder mainform unit below:
//
---
#ifndef mainformH
#define mainformH
//
---
#include Classes.hpp
#include Controls.hpp
#include StdCtrls.hpp
#include Forms.hpp
#include OverbyteIcsSmtpProt.hpp
#include OverbyteIcsWndControl.hpp
#include OverbyteIcsWSocket.hpp
#include ComCtrls.hpp
//
---
class TForm1 : public TForm
{
__published:// IDE-managed Components
TButton *ConnectButton;
TSslSmtpCli *SslSmtpCli1;
TSslContext *SslContext1;
TRichEdit *DisplayMemo;
void __fastcall SslSmtpCli1RequestDone(TObject *Sender, TSmtpRequest
RqType,
WORD ErrorCode);
void __fastcall ConnectButtonClick(TObject *Sender);
void __fastcall SslSmtpCli1Display(TObject *Sender, AnsiString Msg);
void __fastcall SslSmtpCli1SslHandshakeDone(TObject *Sender, WORD
ErrCode,
TX509Base *PeerCert, bool Disconnect);
private:// User declarations
public: // User declarations
int FEhloCount;
__fastcall TForm1(TComponent* Owner);
void __fastcall Display(const AnsiString Msg);
};
//
---
extern PACKAGE TForm1 *Form1;
//
---
#endif
//
---
#include vcl.h
#pragma hdrstop
#include mainform.h
//
---
#pragma package(smart_init)
#pragma link OverbyteIcsSmtpProt
#pragma link OverbyteIcsWndControl
#pragma link OverbyteIcsWSocket
#pragma resource *.dfm
TForm1 *Form1;
//
---
__fastcall TForm1::TForm1(TComponent* Owner)
: TForm(Owner)
{
FEhloCount = 0;
SslSmtpCli1-Host = smtp.gmail.com;
SslSmtpCli1-Port = 25;
SslContext1-SslVerifyPeer = false;
SslSmtpCli1-SslType = smtpTlsExplicit;
DisplayMemo-Clear();
}
//
---
void __fastcall TForm1::SslSmtpCli1RequestDone(TObject *Sender,
TSmtpRequest RqType, WORD ErrorCode)
{
// For every operation, we display the status }
Display(RequestDone Rq= + IntToStr(RqType) + Error= +
IntToStr(ErrorCode));
switch (RqType)
{
case smtpConnect:
SslSmtpCli1-Ehlo();
break;
case smtpEhlo:
if (SslSmtpCli1-SslType == smtpTlsExplicit)
{
FEhloCount++;
if (FEhloCount == 1)
SslSmtpCli1-StartTls();
}
break;
case smtpStartTls:
SslSmtpCli1-Ehlo(); // We need to re-issue Ehlo
break;
}
}
//
---
void __fastcall TForm1::Display(const AnsiString Msg)
{
AnsiString time = FormatDateTime(hh:nn:ss , Now());
DisplayMemo-Lines-BeginUpdate();
try
{
DisplayMemo-Lines-Add(time+Msg);
}
__finally
{
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
I'm having a problem with TSslSmtpCli. It won't complete a TLS connection on port 25. This happens regardless of the server. How many different SMTP servers? I use STARTTLS with smtp.gmail.com on port 25 without any problems, try it. If it fails, it's probably your ISP doing strange things with port 25, like redirecting it their own SMTP server that does not support SSL. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
Hi Angus, On Thu, 23 Aug 2012 10:19 +0100 (BST), you wrote: I'm having a problem with TSslSmtpCli. It won't complete a TLS connection on port 25. This happens regardless of the server. How many different SMTP servers? 6 or 8 probably--every one I try. I use STARTTLS with smtp.gmail.com on port 25 without any problems, try it. I have a gmail account too. Yep, it fails. If it fails, it's probably your ISP doing strange things with port 25, like redirecting it their own SMTP server that does not support SSL. Ok, this could be something, but it only started after upgrading to the v7gold. I guess that could be coincidental. I have my own website and my own smtp server. I've had that since 2003. Never a problem like this. When sending without TLS, it uses my server as expected. The fact is, the banner I receive on connection is the banner of the server I'm trying to connect with. In the case of gmail, I get this: Connected to smtp.gmail.com:25 220 mx.google.com ESMTP ht18sm5248094bkc.16 250-mx.google.com at your service, [xx.xxx.xx.xx] 250-SIZE 35882577 250-8BITMIME 250-STARTTLS 250 ENHANCEDSTATUSCODES 220 2.0.0 Ready to start TLS Connection closed! ERROR: 500 SSL Handshake failed Error at Request Done Failed Do you still believe this is my ISP? Thanks, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
Don't think Google works with port 25 . I remember setting it to a different port Perry On Thu, Aug 23, 2012 at 3:11 PM, gjohn...@mixnym.net wrote: Hi Angus, On Thu, 23 Aug 2012 10:19 +0100 (BST), you wrote: I'm having a problem with TSslSmtpCli. It won't complete a TLS connection on port 25. This happens regardless of the server. How many different SMTP servers? 6 or 8 probably--every one I try. I use STARTTLS with smtp.gmail.com on port 25 without any problems, try it. I have a gmail account too. Yep, it fails. If it fails, it's probably your ISP doing strange things with port 25, like redirecting it their own SMTP server that does not support SSL. Ok, this could be something, but it only started after upgrading to the v7gold. I guess that could be coincidental. I have my own website and my own smtp server. I've had that since 2003. Never a problem like this. When sending without TLS, it uses my server as expected. The fact is, the banner I receive on connection is the banner of the server I'm trying to connect with. In the case of gmail, I get this: Connected to smtp.gmail.com:25 220 mx.google.com ESMTP ht18sm5248094bkc.16 250-mx.google.com at your service, [xx.xxx.xx.xx] 250-SIZE 35882577 250-8BITMIME 250-STARTTLS 250 ENHANCEDSTATUSCODES 220 2.0.0 Ready to start TLS Connection closed! ERROR: 500 SSL Handshake failed Error at Request Done Failed Do you still believe this is my ISP? Thanks, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TSslSmtpCli won't complete TLS on port 25
gjohn...@mixnym.net wrote: Hi Angus, On Thu, 23 Aug 2012 10:19 +0100 (BST), you wrote: I'm having a problem with TSslSmtpCli. It won't complete a TLS connection on port 25. This happens regardless of the server. How many different SMTP servers? 6 or 8 probably--every one I try. I use STARTTLS with smtp.gmail.com on port 25 without any problems, try it. I have a gmail account too. Yep, it fails. Give the SslMailSnd demo a trial, it works: 220 mx.google.com ESMTP fu8sm2298248wib.5 RequestDone Rq=0 Error=0 EHLO your_name 250-mx.google.com at your service, [77.184.1.222] 250-SIZE 35882577 250-8BITMIME 250-STARTTLS 250 ENHANCEDSTATUSCODES RequestDone Rq=10 Error=0 STARTTLS 220 2.0.0 Ready to start TLS Starting SSL handshake Secure connection with TLSv1, cipher ECDHE-RSA-RC4-SHA, 128 secret bits (128 total) RequestDone Rq=12 Error=0 Demo settings: smtp.gmail.com:25 SslVerifyPeer = unchecked SSL type = Explicit(StartSssl) -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] TSslSmtpCli won't complete TLS on port 25
Hi, I'm having a problem with TSslSmtpCli. It won't complete a TLS connection on port 25. I'm speaking of SMTP servers that advertise STARTTLS on that port. After I call StartTls(), I get this: 220 TLS go ahead Then after a very, very, long wait, I get this: 500 SSL Handshake failed This happens regardless of the server. On other ports all is well, both implicit and explicit. I need to get this fixed. What could be the problem? Thanks, George -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
