dovecot - Dec 2006 - Problems with dovecot-sieve on Debian Etch using dovecot LDA

I am running debian etch with dovecot 1.0 rc15 from the debian repository with 
postfix 2.3

I am using virtual users in a postgreSQL database as taken from the dovecot 
wiki while making use of the password field for authentication

I am using deliver as LDA and I am attempting to use the sieve plugin but try 
as I might I can't seem to get it working.

Am I wrong in thinking that a sieve daemon should become active when dovecot 
starts?

Here is my .dovecot.sieve

require "fileinto";
if address :is "from" "foo at example" {
	fileinto ".INBOX.test";
} else {
# The rest goes into INBOX
# default is "implicit keep", we do it explicitly here
	keep;
}

Here is my dovecot.conf:

base_dir: /var/run/dovecot/
log_path: /var/log/dovecot/dovecot.log
info_log_path: /var/log/dovecot/info.log
log_timestamp: %Y-%m-%d %H:%M:%S
syslog_facility: mail
protocols: imaps
listen: *:143
ssl_listen:
ssl_disable: no
ssl_ca_file:
ssl_cert_file: xxxx.pem
ssl_key_file: xxxx.pem
ssl_key_password:
ssl_parameters_regenerate: 168
ssl_cipher_list:
ssl_verify_client_cert: no
disable_plaintext_auth: no
verbose_ssl: no
shutdown_clients: yes
nfs_check: yes
version_ignore: no
login_dir: /var/run/dovecot/login
login_executable: /usr/lib/dovecot/imap-login
login_user: dovecot
login_greeting: Dovecot ready.
login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c
login_log_format: %$: %s
login_process_per_connection: yes
login_chroot: yes
login_greeting_capability: no
login_process_size: 32
login_processes_count: 3
login_max_processes_count: 128
login_max_connections: 256
valid_chroot_dirs:
mail_chroot:
max_mail_processes: 1024
verbose_proctitle: no
first_valid_uid: xxxx
last_valid_uid: xxxx
first_valid_gid: xxxx
last_valid_gid: xxxx
mail_extra_groups:
default_mail_env:
mail_location: maildir:/home/%d/mailboxes/%n
mail_cache_fields: flags
mail_never_cache_fields: imap.envelope
mail_cache_min_mail_count: 0
mailbox_idle_check_interval: 30
mail_debug: no
mail_full_filesystem_access: no
mail_max_keyword_length: 50
mail_save_crlf: no
mail_read_mmaped: no
mmap_disable: no
mmap_no_write: no
lock_method: fcntl
maildir_stat_dirs: no
maildir_copy_with_hardlinks: no
mbox_read_locks: fcntl
mbox_write_locks: dotlock fcntl
mbox_lock_timeout: 300
mbox_dotlock_change_timeout: 120
mbox_min_index_size: 0
mbox_dirty_syncs: yes
mbox_very_dirty_syncs: no
mbox_lazy_writes: yes
dbox_rotate_size: 2048
dbox_rotate_min_size: 16
dbox_rotate_days: 1
umask: 63
mail_drop_priv_before_exec: no
mail_executable: /usr/lib/dovecot/imap
mail_process_size: 256
mail_plugins:
mail_plugin_dir: /usr/lib/dovecot/modules/imap
mail_log_prefix: %Us(%u):
imap_max_line_length: 65536
imap_capability:
imap_client_workarounds: outlook-idle
pop3_no_flag_updates: no
pop3_enable_last: no
pop3_reuse_xuidl: no
pop3_lock_session: no
pop3_uidl_format:
pop3_client_workarounds:
pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
auth default:
  mechanisms: login
  realms:
  default_realm:
  cache_size: 0
  cache_ttl: 3600
  executable: /usr/lib/dovecot/dovecot-auth
  user: root
  chroot:
  username_chars: 
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
  username_translation:
  username_format: %n@%d
  master_user_separator:
  anonymous_username: anonymous
  krb5_keytab:
  verbose: yes
  debug: yes
  debug_passwords: yes
  ssl_require_client_cert: no
  ssl_username_from_cert: no
  count: 1
  worker_max_count: 30
  process_size: 256
  passdb:
    driver: sql
    args: /etc/dovecot/dovecot-sql.conf
    deny: no
    pass: no
    master: no
  userdb:
    driver: sql
    args: /etc/dovecot/dovecot-sql.conf
  socket:
    type: listen
    client:
      path: /var/spool/postfix/private/auth
      mode: 438
      user:
      group:
    master:
      path: /var/run/dovecot/auth-master
      mode: 438
      user:
      group:

Thank you very much,
Samir M. Nassar

On 12/29/06, Samir M. Nassar <dovecot at myriapolis.net>
wrote:
> Am I wrong in thinking that a sieve daemon should become active when
dovecot
> starts?
There's supposed to be a daemon?
> Here is my .dovecot.sieve
>
> require "fileinto";
> if address :is "from" "foo at example" {
>         fileinto ".INBOX.test";
> } else {
> # The rest goes into INBOX
> # default is "implicit keep", we do it explicitly here
>         keep;
> }
Does .dovecot.sieve.err exist?  I believe I tried something similar to
that at first and had to change "from" to "From"

Most certainly though check for the existance (and contents) of the
.dovecot.sieve.err file, it'll tell you exactly what's wrong (assuming
sieve is probably configured and running).

Regards,
Daniel
-- 
Daniel Ballenger
http://denetron.com
Sr. Systems Administrator - Denetron LLC

On Fri, 2006-12-29 at 12:29 -0600, Samir M. Nassar
wrote:
> I am running debian etch with dovecot 1.0 rc15 from the debian repository
with
> postfix 2.3
> I am using virtual users in a postgreSQL database as taken from the dovecot
> wiki while making use of the password field for authentication
Same setup here, except for local user accounts.
> I am using deliver as LDA and I am attempting to use the sieve plugin but
try
> as I might I can't seem to get it working.
> 
> Am I wrong in thinking that a sieve daemon should become active when
dovecot
> starts?
There's no SIEVE daemon. SIEVE functionality is implemented as a plugin
to the dovecot LDA. You sould check out the dovecot-lda module from CVS
and build it against your dovecot sources.

> Here is my .dovecot.sieve
This is not processed until you build and configure the sieve plugin.

> Here is my dovecot.conf:
You miss a "protocol lda" section specifying which plugins should be
loaded. See http://wiki.dovecot.org/LDA/Sieve for documentation.

ciao

Luca

On Friday 29 December 2006 12:29, Samir M. Nassar wrote:
> I am running debian etch with dovecot 1.0 rc15 from the debian repository
> with postfix 2.3
I have found part of the problem.

I am using postfix-2.3 and the instructions on the dovecot wiki are there for 
postfix <2.0 from some of the configuration options.

I will have to read up on the configuration option for postfix 2.3.

Also, in certain circumstances deliver works as advertised and everything is 
fine that way, the problem is making sure that postfix delivers mail to the 
virtual users.

Thanks for all the help, it is much appreciated.

-- 
Samir M. Nassar
http://myriapolis.net