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

[Marcus Hüwe]

Am Tue, 27 Jun 2006 09:26:55 +0200
schrieb radoeka <radoeka at xs4all.nl>:

> On Tue, Jun 27, 2006 at 02:16:41AM +0200, Marcus H??we wrote:
> > Am Mon, 26 Jun 2006 23:36:17 +0200
> > > The question is why is ingo trying to login via tls?
> > Ah got it!
> > It's a "problem" (ok not really a problem ;) ) with the Sieve.php
> > script (http://pear.php.net/package/Net_Sieve)
> > Have a look at the attached diff.
> 
> Works like a charm!  Very well done Marcus and very swift!
> 
> > Maybe it's possible to write a patch (which can be accepted
> > upstream)
> 
> What do you mean with upstream, is that kolab or pear?
PEAR.

> I ask as kolab seems to use an copy of the PEAR/Net/Sieve.php script,
> I would think that an include of this library would be better, than an
> old copy......
> 
No. Using the "old kolab file" is the wrong way IMHO because kolab
already uses a number of patched applications (postfix, cyrus-imapd...).

I attached two patches: one for Net_Sieve and the other one for ingo.
Can someone comment on this?


Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ingo_timsieved.php.diff
Type: text/x-patch
Size: 535 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20060627/c276b428/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: net_sieve-no_tls.diff
Type: text/x-patch
Size: 2343 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20060627/c276b428/attachment-0001.bin>