Indy 10.2.3 - problem with SASL

Giganews Newsgroups
Subject: Indy 10.2.3 - problem with SASL
Posted by:  Philip von Melle (philip.vonmel…@globetrotter.de)
Date: Wed, 15 Aug 2007

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.

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).

:7c812a5b kernel32.RaiseException + 0x52
:20006c24 NotifyNonDelphiException + $1C
:7c91378b ntdll.RtlConvertUlongToLargeInteger + 0x46
IndyCore100.IdReply.TIdReply.Clear
IndyCore100.IdReply.TIdReply.SetCode(...)
IndyProtocols100.IdReplySMTP.TIdReplySMTP.AssignTo(???)
:00505245 TIdReplySMTP.AssignTo + $21
IndyProtocols100.IdSASLCollection.TIdSASLEntries.LoginSASL('AUTH',(...),
(...),$CDD250,$D20F80,'AUTH')
IndyProtocols100.IdSMTP.TIdSMTP.Authenticate
IndyProtocols100.IdSMTP.TIdSMTP.Send($CE4650,$D5C960)
IndyProtocols100.IdSMTPBase.TIdSMTPBase.Send($507D9C)

Philip

Replies