On Fri, 2014-04-18 at 14:47 +0200, Milan Crha wrote: > On Thu, 2014-04-17 at 10:12 -0400, dfc wrote: > > [imapx:A] Starting command (active=1,) A00000 LOGIN... > > [imapx:A] camel_imapx_write: 'LOGIN...' > > [imapx:A] camel_imapx_read: buffer is 'A00000 NO failed: Could not > > connect to server' > > Hi, > interesting, at least to me, from the above snippet I'd say that > evolution successfully connected to the server (you've received some > capabilities and so on), and then evolution issued a "LOGIN" command, > which includes your credentials. The server responded with "NO". Though > I cannot tell for sure whether the actual error message comes from the > server, or from the imapx code. > > Try to cleanup your certificates, as Pete said, and then it might start > working. Make sure evo will be down when you'll play with them. > Bye, > Milan
It was a server-side configuration problem. I ended up using openssl s_client -connect imap.cornell.edu:993 and monitored the entire SSL interaction; it was fine. The CAMEL_DEBUG imapx error message was the server's verbatim response to the login attempt NO failed: Could not connect to server Eventually, they fixed the problem and all is well. Thanks all around. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
