| Summary | Net_Sieve call parameters |
| Queue | Ingo |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | martin (at) gamigo (dot) de |
| Created | 09/12/2006 (6892 days ago) |
| Due | |
| Updated | 10/09/2006 (6865 days ago) |
| Assigned | |
| Resolved | 10/09/2006 (6865 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
ticket #4496.Queue ⇒ Ingo
State ⇒ Accepted
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Queue ⇒ Kolab
Version ⇒
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Net_Sieve call parameters
Queue ⇒ Ingo
State ⇒ Unconfirmed
it's impossible to add/change/delete rules in a standard kolab-horde scenario.
lib/Driver/timesieved.php creates Net_Sieve with 6 parameters, but the
9th one determines if the connection will be encrypted with TLS or
not. The standard kolab installation does not allow TLS encrypted
connections to the sieve-daemon. The default value of the 9th param is
to use TLS.
But after I added three more constructor parameters (false, false,
false) to the creation of Net_Sieve another error appeared:
There's an error in the the newest pear Net_Sieve class (I know this
is not your fault - but I think you want to know this too :)). The
function _handleConnectAndLogin calls connect with three parameters.
The third parameter is $this->_useTLS. But connect excpects four
parameters - and $useTLS has to be the forth. Because the default
value for the forth parameter is true the connection still get's
encrypted. To solve this I use null as the third and $this->_useTLS as
the fourth parameter.
I didn't looked in older sources of Net_Sieve, but for me it seems
like they tried to add TLS support and not only coded the described
error but also use TLS as default.
So I just write this ticket to let you know it was nice if you could
add a config option useTLS as I saw this isn't yet done CVS
Greets,
Martin