Re: [Dovecot] bsdauth + dovecot-sieve

2011-01-28 Thread Gonzalo Rodriguez
well with allow_all_users=yes is fixed, so now I need to avoid spam :) cheers mate. 2011/1/28 Timo Sirainen : > On 28.1.2011, at 23.22, Timo Sirainen wrote: > >> On 28.1.2011, at 23.16, Gonzalo Rodriguez wrote: >> >>> Remember I have the user system added in the mail server but they auth >>> to a

Re: [Dovecot] bsdauth + dovecot-sieve

2011-01-28 Thread Timo Sirainen
On 28.1.2011, at 23.22, Timo Sirainen wrote: > On 28.1.2011, at 23.16, Gonzalo Rodriguez wrote: > >> Remember I have the user system added in the mail server but they auth >> to a AD, any way to solve this? > > By: > >>> add allow_all_users=yes to userdb static. Or is there a reason why you do

Re: [Dovecot] bsdauth + dovecot-sieve

2011-01-28 Thread Timo Sirainen
On 28.1.2011, at 23.16, Gonzalo Rodriguez wrote: > Remember I have the user system added in the mail server but they auth > to a AD, any way to solve this? By: >> add allow_all_users=yes to userdb static.

Re: [Dovecot] bsdauth + dovecot-sieve

2011-01-28 Thread Gonzalo Rodriguez
hi thank you for response, without the allow_all_users=yes I have this: deliver(prue...@bla.com): Jan 28 18:09:49 Info: Loading modules from directory: /usr/local/lib/dovecot/lda deliver(prue...@bla.com): Jan 28 18:09:49 Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so de

Re: [Dovecot] bsdauth + dovecot-sieve

2011-01-27 Thread Timo Sirainen
On Wed, 2011-01-26 at 16:12 -0300, Gonzalo Rodriguez wrote: > passdb: > driver: bsdauth > userdb: > driver: static > args: uid=vmail gid=vmail home=/var/www/datos/correo/bla.com/%n .. > Can I use in dovecot deliver (master.cf) with parameters -d if I use > bsdauth to auth without

[Dovecot] bsdauth + dovecot-sieve

2011-01-26 Thread Gonzalo Rodriguez
Hi all, I have a problem with my dovecot/postfix configuration: here is my dovecot -n # /usr/local/sbin/dovecot -n # 1.1.20: /etc/dovecot.conf Warning: fd limit 128 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and