Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Luca Corti
On Wed, 2009-12-16 at 05:01 +0100, Pascal Volk wrote: service managesieve { inet_listener { port = 2000 } } Are you sure? Or was it: 'service managesieve-login {…}'? Right, stupid typo, in the config is obviously correct. BTW: Use port 4190

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Luca Corti
On Thu, 2009-12-17 at 20:56 +0100, Luca Corti wrote: I could also alter my filters from Horde Ingo, but strangely enough it won't display the currently active script and managesieve does not log anything anymore about the sieve script not being there. Ignore this one, it's an issue with Ingo

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Nick Douma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17-12-2009 21:21, Luca Corti wrote: On Thu, 2009-12-17 at 20:56 +0100, Luca Corti wrote: I could also alter my filters from Horde Ingo, but strangely enough it won't display the currently active script and managesieve does not log anything

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Luca Corti
On Thu, 2009-12-17 at 21:55 +0100, Nick Douma wrote: // Name of the sieve script 'scriptname' = 'ingo', 'scriptname' = '.dovecot.sieve', Everything else seems good to me. ciao Luca

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Nick Douma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17-12-2009 22:02, Luca Corti wrote: On Thu, 2009-12-17 at 21:55 +0100, Nick Douma wrote: // Name of the sieve script 'scriptname' = 'ingo', 'scriptname' = '.dovecot.sieve', Everything else seems good to me. ciao Luca

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Luca Corti
On Thu, 2009-12-17 at 22:14 +0100, Nick Douma wrote: Ok, but how do I tell ingo to use this backend? I can't find a config entry of something in the Horde Administration panels that seem to control this. Also, when I click filters, I don't see my already present Sieve filters. Just leave only

Re: [Dovecot] v2.0.beta1 released

2009-12-17 Thread Nick Douma
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17-12-2009 23:06, Luca Corti wrote: On Thu, 2009-12-17 at 22:14 +0100, Nick Douma wrote: Ok, but how do I tell ingo to use this backend? I can't find a config entry of something in the Horde Administration panels that seem to control this.

Re: [Dovecot] v2.0.beta1 released

2009-12-16 Thread Ed W
Hmm, you raise some good points... This could be a problem, yes.. I probably have to make this configurable in some way. Or perhaps I could add some more code so that if only the same user+password combination (or a few of them) are the problem, it doesn't penalize. This feels familiar, I think

Re: [Dovecot] v2.0.beta1 released

2009-12-16 Thread Timo Sirainen
Just in case someone thought about testing beta1 on a live system, here's a small update about some of the bad bugs found (and fixed in hg) so far: - LMTP server drops first 128k from mails with 128k mails - some plugins crash / don't work correctly I'll probably make a beta2 release on

Re: [Dovecot] v2.0.beta1 released

2009-12-16 Thread Odhiambo Washington
On Thu, Dec 17, 2009 at 12:02 AM, Timo Sirainen t...@iki.fi wrote: Just in case someone thought about testing beta1 on a live system, here's a small update about some of the bad bugs found (and fixed in hg) so far: - LMTP server drops first 128k from mails with 128k mails - some plugins

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Odhiambo Washington
On Mon, Dec 14, 2009 at 6:12 AM, Timo Sirainen t...@iki.fi wrote: http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig FreeBSD 6.4 (yes, it is old but I have been running the latest alpha on it): /usr/local/bin/bash

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Luca Corti
On Sun, 2009-12-13 at 22:12 -0500, Timo Sirainen wrote: http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Testing this in low volume very simple setup and seems to work fine after a day. Configuration is just plain

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Pascal Volk
On 12/15/2009 10:31 PM Luca Corti wrote: … dovecot-2.0-managesieve does not even build though. I know this is not for you Timo, but here is the debug output anyway if anyone cares. … Making all in managesieve … managesieve-settings.c:30: warning: implicit declaration of function 'MEMBER'

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Ed W
On 14/12/2009 03:12, Timo Sirainen wrote: Largest changes since alpha3: - if some IP address is failing authentications, all auth attempts from the IP are delayed increasingly. a successful auth drops the delay. max delay is 15 seconds. this is enforced by auth process, so it works across

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Timo Sirainen
On Wed, 2009-12-16 at 00:03 +, Ed W wrote: On 14/12/2009 03:12, Timo Sirainen wrote: Largest changes since alpha3: - if some IP address is failing authentications, all auth attempts from the IP are delayed increasingly. a successful auth drops the delay. max delay is 15 seconds.

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Luca Corti
On 12/15/2009 10:48 PM, Pascal Volk wrote: There were a few API changes in the past. My ManageSieve installation is working so far. The necessary modifications are attached as patch. (But remember: There is no guarantee …) Thanks a lot Pascal for sharing the patch. I don't expect

Re: [Dovecot] v2.0.beta1 released

2009-12-15 Thread Pascal Volk
On 12/16/2009 04:15 AM Luca Corti wrote: … I patched and compiled fine, then added protocols = ... managesieve and service managesieve { inet_listener { port = 2000 } } Are you sure? Or was it: 'service managesieve-login {…}'? BTW: Use port 4190

[Dovecot] v2.0.beta1 released

2009-12-13 Thread Timo Sirainen
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are