| Summary: | CRAM-MD5 doesn't work | ||
|---|---|---|---|
| Product: | Claws Mail (Windows) | Reporter: | mlatu <mlatu> |
| Component: | default | Assignee: | users |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mlatu |
| Priority: | P3 | ||
| Version: | 3.10.1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Attachments: | network protocols for 3.11.1 on linux and 3.10.1 on windows | ||
My installation successfully authenticates with the CRAM-MD5 setting, though I can't verify whether it actually uses CRAM-MD5 at the protocol level. Claws 3.13.0 on Windows 7. If there's a relatively easy way to check the protocol, please let me know and I'll try it. Thanks, Phil You can see it in Network log, found in main window's Tools menu. The line should look something like: [14:02:21] IMAP4> Logging username to 11.22.33.44 using CRAM-MD5 This currently doesn't work on Windows for IMAP and NNTP, because our build of libetpan (the middleware library we use for these protocols) does not have SASL support compiled in. Fortunately, I have figured out how to do it, after overcoming the biggest roadblock - building cyrus-sasl and its plugins - so next Windows release will have this working, as well as SCRAM-SHA1 and DIGEST-MD5. See commit http://git.claws-mail.org/?p=claws-win32-installer.git;a=commitdiff;h=0790661d3c25ea558f6f053d343dba158488bcd6 |
Created attachment 1488 [details] network protocols for 3.11.1 on linux and 3.10.1 on windows Tried on a linux box (though that's 3.11.1), works like a charm, see attached file linux-networkprotocol.txt for linux session. On windows (3.10.1) however, i have set the account to the same settings but it immediatly fails authenticating. See attached file windows-networkprotocol.txt