Roundcube Community Forum

Release Support => Pending Issues => Topic started by: qwerk on July 28, 2015, 05:03:22 PM

Title: debian courier starttls and roundcube
Post by: qwerk on July 28, 2015, 05:03:22 PM
hello,
all works fine with my old configuration debian jessie courier and ssl.
roundcube, thunderbird and k9mail...
after thunderbird throw the message ssl is bad, i swap to starttls.
k9mail is now working but with roundcube i ve several problems:
i want to sign in but i get allways the error message:
Code: [Select]
[28-Jul-2015 23:24:02 +0200]: <ku5db4ld> IMAP Error: Login failed for ranger from 1.2.3.4. Unable to negotiate TLS in /usr/share/roundcube/program/lib/Roundcube/rcube_imap.php on line 198 (POST /rc/?_task=login?_task=login&_action=login)
[28-Jul-2015 23:24:04 Europe/Berlin] PHP Warning:  failed loading cafile stream: `/etc/ssl/private/imapd.pem' in /usr/share/roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 915
[28-Jul-2015 23:24:04 +0200]: <ku5db4ld> IMAP Error: Login failed for ranger from 1.2.3.4. Unable to negotiate TLS in /usr/share/roundcube/program/lib/Roundcube/rcube_imap.php on line 198 (POST /rc/?_task=login?_task=login&_action=login)
[28-Jul-2015 23:24:07 Europe/Berlin] PHP Warning:  failed loading cafile stream: `/etc/ssl/private/imapd.pem' in /usr/share/roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 915
[28-Jul-2015 23:24:07 +0200]: <ku5db4ld> IMAP Error: Login failed for ranger from 1.2.3.4. Unable to negotiate TLS in /usr/share/roundcube/program/lib/Roundcube/rcube_imap.php on line 198 (POST /rc/?_task=login?_task=login&_action=login)

i ve add these lines to the config:
Code: [Select]

$config['default_host'] = 'tls://localhost:143';

$config['imap_conn_options'] = array(
    'ssl' => array(
        'verify_peer'       => true,
        'allow_self_signed' => true,
        'verify_depth' => 3,
        'cafile'  => '/etc/courier/imapd.pem',
    ),
);

thanks for the help
Title: Re: debian courier starttls and roundcube
Post by: SKaero on July 28, 2015, 05:56:07 PM
You may not be using the correct port.