[Dovecot] Stuck with dovecot-sieve and horde-ingo ...
Hello, dovecot-users ...
as you may read at
http://lists.horde.org/archives/horde/Week-of-Mon-20090706/037786.html
I am stuck getting dovecot-sieve working with the ingo-application of the horde-framework.
To me it seems as if ingo doesn't even trigger any request/command to managesieve ... I set "mail_debug=yes" in the managesieve-section of dovecot.conf but don't see any errors there, in fact not even loglines in /var/log/mail ... Any way to increase the loglevel here?
Apache also doesn't log any errors. I am able to contact managesieve via telnet or even thunderbird's sieve-plugin.
I edited the relevant backends.php over and over again, substituting, starting from scratch etc ...
Could someone maybe give me some hint on how to proceed?
I don't know if the problem is with dovecot or ingo or the underlying php/perl/something-stuff ...
I currently use these releases:
dovecot-1.2-sieve-0.1.8 dovecot-1.2-managesieve-0.11.7 dovecot-1.2.1
The server is some older Suse 10.1 ...
php5-5.1.2-29.45, apache2-2.2.0-21.7, Horde Groupware Webmail Edition 1.2
# pear5 list Installed packages, channel pear.php.net:
Package Version State Archive_Tar 1.3.1 stable Console_Getopt 1.2 stable DB 1.7.12 stable Date 1.4.7 stable Log 1.9.11 stable Mail 1.1.14 stable Net_Sieve 1.1.6 stable Net_Socket 1.0.9 stable PEAR 1.4.6 stable XML_RPC 1.5.1 stable
I would appreciate any input on this as this issue now already is unsolved for weeks now. And as always that is one of the features the customer wants first ;-)
Aside from this dovecot is working great here, thanks !
Stefan
Stefan G. Weichinger schrieb:
Hello, dovecot-users ...
as you may read at
http://lists.horde.org/archives/horde/Week-of-Mon-20090706/037786.html
I am stuck getting dovecot-sieve working with the ingo-application of the horde-framework.
To me it seems as if ingo doesn't even trigger any request/command to managesieve ... I set "mail_debug=yes" in the managesieve-section of dovecot.conf but don't see any errors there, in fact not even loglines in /var/log/mail ... Any way to increase the loglevel here?
Apache also doesn't log any errors. I am able to contact managesieve via telnet or even thunderbird's sieve-plugin.
I edited the relevant backends.php over and over again, substituting, starting from scratch etc ...
Could someone maybe give me some hint on how to proceed?
I don't know if the problem is with dovecot or ingo or the underlying php/perl/something-stuff ...
I currently use these releases:
dovecot-1.2-sieve-0.1.8 dovecot-1.2-managesieve-0.11.7 dovecot-1.2.1
The server is some older Suse 10.1 ...
php5-5.1.2-29.45, apache2-2.2.0-21.7, Horde Groupware Webmail Edition 1.2
# pear5 list Installed packages, channel pear.php.net:
Package Version State Archive_Tar 1.3.1 stable Console_Getopt 1.2 stable DB 1.7.12 stable Date 1.4.7 stable Log 1.9.11 stable Mail 1.1.14 stable Net_Sieve 1.1.6 stable Net_Socket 1.0.9 stable PEAR 1.4.6 stable XML_RPC 1.5.1 stable
I would appreciate any input on this as this issue now already is unsolved for weeks now. And as always that is one of the features the customer wants first ;-)
Aside from this dovecot is working great here, thanks !
Stefan
Hi Stefan, did you try testing a newer os allready? you shouldnt invest time in suse 10.1 any longer as its outdated
if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/
as i said before i havent any bugs here with ingo on ubuntu hardy and latest dovecot 1.2
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Robert Schetterer schrieb:
if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/
will do asap ... thanks
Robert Schetterer schrieb:
if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/
exactly the same behavior: ingo complains "driver not in transaction state" ...
Seems as if ingo fails to even contact port 2000 ... any idea on how to debug ingo itself?
Stefan
Robert Schetterer schrieb:
if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/
exactly the same behavior: ingo complains "driver not in transaction state" ...
Seems as if ingo fails to even contact port 2000 ... any idea on how to debug ingo itself?
Stefan
Stefan G. Weichinger schrieb: there is somewhere in the horde doku how to setup verbose php debug logging sorry i couldnt remember where , but i used it allready during testing
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
participants (2)
-
Robert Schetterer
-
Stefan G. Weichinger