[Kolab-devel] Ingo states 'Failed to establish TLS connection'

[Marcus Hüwe]

Am Mon, 26 Jun 2006 23:02:41 +0200
schrieb Richard Bos <radoeka at xs4all.nl>:

> Hello Kolab-bers,
> 
> last weekend I succesfully installed the horde modules: Ingo and
> IMP.  This is all suse based, and most of the things just work :)
> 
> There is an issue with Ingo however, perhaps someone is able to point
> in the right direction.  Short problem description: filter rules are
> not executed. I think this is dues to the filter script not being
> written to the server. The cause could be a TLS problem.
> 
/var/log/messages:

Jun 26 23:26:41 linux master[4645]: about to
exec /usr/lib/cyrus/bin/timsieved
Jun 26 23:26:41 linux sieve[4645]: executed
Jun 26 23:26:41 linux sieve[4645]: accepted connection
Jun 26 23:26:41 linux sieve[4645]: TLS server engine: cannot load CA
data
Jun 26 23:26:41 linux sieve[4645]: STARTTLS failed:
linux.linux-network.tld[127.0.0.1]
Jun 26 23:26:41 linux sieve[4645]: DBERROR 0U\uffff: db4
Jun 26 23:26:41 linux sieve[4645]: DBERROR 0U\uffff: db4
Jun 26 23:26:41 linux sieve[4645]: DBERROR: error exiting application:
Invalid argument
Jun 26 23:26:41 linux master[4387]: process 4645 exited, status 0


The question is why is ingo trying to login via tls?
The ingo/config/backends.php looks like the following:

##################
<?php
/* Kolab Example (using Sieve) */
    $backends['kolab'] = array(
        'driver' => 'timsieved',
        'preferred' => '',
        'hordeauth' => 'full',
        'params' => array(
            'hostspec' => $GLOBALS['conf']['kolab']['imap']['server'],
            'logintype' => 'PLAIN',
            'port' =>
$GLOBALS['conf']['kolab']['imap']['sieveport'],            'scriptname'
=> 'kmail-vacation.siv' ), 'script' => 'sieve',
        'scriptparams' => array()
    );
#################

'logintype' => 'PLAIN',

So normally a plain login should be used?!
Or am i totally wrong? 


Marcus