update this function for the data structure change in eimap 0.2
Description
Description
Details
Details
- Auditors
vanmeeuwen - Provenance
Aaron Seigo <aseigo@kde.org> Authored on Jun 20 2016, 1:31 PM • seigo Pushed on Jun 20 2016, 1:34 PM - Parents
- rGdbb21403a130: 0.8.1
- Branches
- Unknown
- Tags
- Build Status
Buildable 4010 Build 3997: Continuous Integration for Software Development Projects
Event Timeline
Comment Actions
For STARTTLS connections, this now renders:
15:01:30.984 [error] gen_fsm <0.164.0> in state idle terminated with reason: bad argument in call to binary:match([<<"IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxten QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_AT...">>], <<"STARTTLS">>) in eimap:handle_info/3 line 292 15:01:30.984 [error] CRASH REPORT Process <0.164.0> with 0 neighbours exited with reason: bad argument in call to binary:match([<<"IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxten QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_AT...">>], <<"STARTTLS">>) in eimap:handle_info/3 line 292
With the Cyrus IMAP server reporting:
Jun 20 15:02:48 kolab imap[18475]: inittls: Loading hard-coded DH parameters Jun 20 15:02:48 kolab imap[18475]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits reused) no authentication
Implicit SSL connections are OK.
Comment Actions
FWIW, configuring Guam to use IMAPS against the backend server will cause the client to not be presented with a STARTTLS capability:
%% Example configuration for Guam. [ { kolab_guam, [ { imap_servers, [ { imaps, [ { host, "192.168.122.131" }, { port, 993 }, { tls, true } ] } ] }, { listeners, [ { imap, [ { port, 9143 }, { imap_server, imaps }, { rules, [ { filter_groupware, [] } ] }, { tls_config, [ { certfile, "/etc/pki/tls/private/localhost.pem" } ] } ] }, { imaps, [ { port, 9993 }, { implicit_tls, true }, { imap_server, imaps }, { rules, [ { filter_groupware, [] } ] }, { tls_config, [ { certfile, "/etc/pki/tls/private/localhost.pem" } ] } ] } ] } ] },