Re: Indy 10.2.3 - problem with SASL

Giganews Newsgroups
Subject: Re: Indy 10.2.3 - problem with SASL
Posted by:  Remy Lebeau \(Indy Team\) (no.spam@no.spam.com)
Date: Wed, 15 Aug 2007

"Philip von Melle" <philip.vonmel…@globetrotter.de> wrote in message
news:Xns998DAFC7CC08philipvonmelleglo…@87.106.16.84...

> When using TIdSMTP.AuthType := atSASL with TIdSASLCRAMMD5
> or TIdSASLLogin and an assigned TIdUserPassProvider you'll get
> an EAccessViolation upon sending - stack trace below. It occurs in
> line 215 in IdReply.pas.

Looks like LoginSASL() is not constructing its temp TIdReply object
correctly, so the TIdReply constructors are being bypassed and the FText
member is not instantiated.

> Looking at a logfile on the mailserver it appears that the Indy SMTP
> client sends empty responses upon the 334 challenge messages of
> the server (in the place where the client is supposed to send the
> encoded username and password).

Please show that log.

Gambit

Replies

In response to

Indy 10.2.3 - problem with SASL posted by Philip von Melle on Wed, 15 Aug 2007