🚀 go-pugleaf

"BrianV" <bvanmatre_remove_@yahoo.com> wrote in message 
news:47bf9844$1@newsgroups.borland.com...

> I'm having lots of trouble getting Indy SMTP to work reliably for me.

Then you are likely using it wrong to begin with.  TIdSMTP is quite reliable 
when used properly.

> I am using 10.1.5, the version that ships with C++ Builder 2007.

As I told you in the other discussion thread you started, you are using an 
old version of Indy.  The current version is 10.2.3.

> When calling Connect() on a IdSMTP component, the flow
> goes through Indy code like this:
<snip>

The SMTP protocol dictates that the server is required to send a greeting to 
the client upon a successful connection to the server.  That is what 
GetResponse() is reading inside of Connect().

> The neat thing about this last method, is that no matter what
> you set timeouts to, this last method is called without a value
> for AFailCount, and so it loops through MaxInt times.  So if a
> user ever enters an incorrect port for their SMTP connection,
> there doesn't seem to be any straightforward way to avoid an
> interminable timeout where the app just hangs.

If the client connects to the wrong port, there is no way for Indy to detect 
that without reading from the socket.  In this situation, Indy is expecting 
the server to send a line of text.  If the server does not actually do that, 
the only thing Indy can do is wait for a timeout to elapse.  It is your 
responsibility to make sure you connect to the correct port to begin with. 
If you want a timeout to occur, then you will have to set the ReadTimeout 
property before calling Connect().  Otherwise, ReadLn() will use an infinite 
timeout by default and wait forever.


Gambit