AFAIK, TIdIMAP
SASL is now working fine (considering I'm the one who implemented it). I don't have access to any IMAP servers that use SASL so I couldn't actually test it myself, but this is the first time I have heard of any problems with it in the past several months that the fixed implementation has existed.
However, without seeing the actual socket traffic, there is no way to know if the server is sending any reply back at all, or if TIdIMAP
is just not reading the reply correctly. Can you provide an actual log of the commands/responses? Either use a packet sniffer, like Wireshark, or attach one of Indy's own TIdLog...
components to the TIdIMAP.Intercept
property.
Update: It is a bug in TIdIMAP4.GetInternalResponse()
. It is not handling the +
line correctly. I have checked in a fix to Indy's SVN.