First, it doesn't do case-independent matching on SASL authenticator types (e.g. "auth plain" does not work but "auth PLAIN" does).
Second, it does not issue proper empty challenges. It issues "334 =" instead of the correct "334 ".
Basically, it's a variant of the problem described in:
http://www.washington.edu/imap/IMAP-FAQs/index.html#7.47
Please contact Google and report the problem.
On Tue, 22 Feb 2005, Akmal Khodjanov wrote:
Has anybody experienced problems using c-client on Google's SMTP server? I'm trying to send a message using c-client, and that's what I get: Log: SMTP SERVER BUG (invalid challenge): = Log: Can not authenticate to SMTP server: 334 = The hostlist I'm passing to smtp_open looks like this: smtp.gmail.com/ssl/[EMAIL PROTECTED]/smtp
-- Mark --
http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
