Excerpts from Maurice McCarthy''s message of Fri May 15 13:37:08 -0400
2009:> The sup log tells me that when I log in to my
> gmail account it ends up logging in using
> plain text.
This is normal and just a part of a standard IMAP connection auth
sequence. Unless you''ve got kerberos enabled/SASL auth stuff in
place, the standard IMAP auth options are all pretty nasty (pop3 is no
better)...
> Fri May 15 17:20:06 +0000 2009: CRAM-MD5 authentication failed:
> Net::IMAP::NoResponseError. Trying LOGIN auth...
> Fri May 15 17:20:06 +0000 2009: LOGIN authentication failed:
> Net::IMAP::NoResponseError. Trying plain-text LOGIN...
> Fri May 15 17:20:06 +0000 2009: Successfully connected to
> imaps://imap.googlemail.com:993/INBOX.
You still connected via an ssl secured connection, so even using
horrible auth mechanisms like this, you''re reasonably protected during
transit.
Looks good from here.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/sup-talk/attachments/20090515/3372a1e8/attachment.bin>