Re: dsync does not like sieve

Yes, both ends have almost the same configuration.

protocols {
  sieve = yes
}

service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
}

sieve_pipe_bin_dir = /etc/dovecot/sieve
sieve_pipe_socket_dir = sieve-pipe

protocol sieve {
}

sieve_script personal {
#  path = ~/sieve
#  active_path = ~/.dovecot.sieve
}
sieve_script default {
  path = /etc/dovecot/sieve/spam.sieve
}

sieve_plugins {
  sieve_imapsieve = yes
  sieve_extprograms = yes
}
sieve_global_extensions {
  vnd.dovecot.pipe = yes
  vnd.dovecot.environment = yes
}
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]