🚀 go-pugleaf

I'm having lots of trouble getting Indy SMTP to work reliably for me.  I am 
using 10.1.5, the version that ships with C++ Builder 2007.  One of the 
issues I'm having is the following:

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

/*------------------------------------------------------------*/
//   First, IdSMTP line 416
/*------------------------------------------------------------*/
procedure TIdSMTP.Connect;
begin
  inherited Connect; try
    GetResponse(220);
    SendGreeting;
  except
    Disconnect;
    Raise;
  end;
end;

/*------------------------------------------------------------*/
// Then here...
/*------------------------------------------------------------*/
function TIdTCPConnection.GetResponse(AAllowedResponse: SmallInt): SmallInt;
begin
  Result := GetResponse([AAllowedResponse]);
end;

/*------------------------------------------------------------*/
Then to IdTCPConnection line 547
/*------------------------------------------------------------*/
function TIdTCPConnection.GetResponse(
 const AAllowedResponses: array of SmallInt): SmallInt;
begin
  GetInternalResponse;
  Result := CheckResponse(LastCmdResult.NumericCode, AAllowedResponses);
end;

/*------------------------------------------------------------*/
Then to IdTCPConnection line 674
/*------------------------------------------------------------*/
procedure TIdTCPConnection.GetInternalResponse;
var
  LLine: string;
  LResponse: TIdStringList;
begin
  CheckConnected;
  LResponse := TIdStringList.Create; try
    // Some servers with bugs send blank lines before reply. Dont remember 
which
    // ones, but I do remember we changed this for a reason
    LLine := IOHandler.ReadLnWait;
    LResponse.Add(LLine);
    while not FLastCmdResult.IsEndMarker(LLine) do begin
      LLine := IOHandler.ReadLn;
      LResponse.Add(LLine);
    end;
    //Note that FormattedReply uses an assign in it's property set method.
    FLastCmdResult.FormattedReply := LResponse;
  finally Sys.FreeAndNil(LResponse); end;
end;

/*------------------------------------------------------------*/
and finally to IdIOHandler line 1199
/*------------------------------------------------------------*/
function TIdIOHandler.ReadLnWait(AFailCount: Integer = MaxInt): string;
var
  LAttempts: Integer;
begin
// MtW: this is mostly used when empty lines could be send.
  Result := '';
  LAttempts := 0;
  while (Length(Result) = 0) and (LAttempts < AFailCount) do begin
    Inc(LAttempts);
    Result := Sys.Trim(ReadLn);
  end;
end;

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.

I know this would be an easy fix in Indy, but the problem is that I've only 
spent a little time trying to make Indy work for me, and have hit a few 
pretty major issues like this that seem to be complete show stoppers for 
trying to use this in a commercial app.

Are there other SMTP components out there that are less buggy (but still 
work with SSL), or do I need to give Indy more of a chance?  A lot of the 
stuff Indy does is very impressive, but I have to say, so far it has been 
EXTREMELY frustrating.

Thanks for any advice,
Brian