Re: Sieve doesn't work after LTMP Director implementation
> On 12/04/2021 10:28 Gonzalo Palacios Goicolea > wrote: > > > Hi All, > We're running dovecot director por proxying imap/pop queries to the backends. > Yesterday we add LMTP proxying and it works fine, but we have realized that > Sieve filters are no longer working after this change. Is it mandatory to add > some config to the directors or backends after implementing LMTP through > Director? > We use > > dovecot-pigeonhole-2.2.36-8.el7.x86_64 > dovecot-2.2.36-8.el7.x86_64 > > This is director servers config, if you also need backends config, please let > me know > > doveconf -n > # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.24 (124e06aa) > # OS: Linux 3.10.0-1160.15.2.el7.x86_64 x86_64 Red Hat Enterprise Linux > Server release 7.9 (Maipo) Sieve filtering happens in backend, so director configuration does not really factor into this. Perhaps check backend logs for clues? Aki Aki
Sieve doesn't work after LTMP Director implementation
Hi All,
We're running dovecot director por proxying imap/pop queries to the
backends. Yesterday we add LMTP proxying and it works fine, but we have
realized that Sieve filters are no longer working after this change. Is
it mandatory to add some config to the directors or backends after
implementing LMTP through Director?
We use
dovecot-pigeonhole-2.2.36-8.el7.x86_64
dovecot-2.2.36-8.el7.x86_64
This is director servers config, if you also need backends config,
please let me know
doveconf -n
# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.24 (124e06aa)
# OS: Linux 3.10.0-1160.15.2.el7.x86_64 x86_64 Red Hat Enterprise Linux
Server release 7.9 (Maipo)
# Hostname: hidden
auth_cache_negative_ttl = 5 mins
auth_cache_size = 64 M
auth_cache_ttl = 5 mins
auth_failure_delay = 5 secs
auth_verbose = yes
default_client_limit = 4
default_process_limit = 5500
director_mail_servers = Hidden
director_servers = Hidden
disable_plaintext_auth = no
doveadm_port = 24245
listen = *
lmtp_proxy = yes
mail_location = maildir:%h/Maildir
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart extracttext
mbox_write_locks = fcntl
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = proxy=y nopassword=y
driver = static
}
plugin {
mail_log_events = delete undelete expunge mailbox_delete
mailbox_rename mailbox_create save
mail_log_fields = uid box msgid from subject
sieve = file:~/sieve;active=~/.dovecot.sieve
}
service director {
fifo_listener login/proxy-notify {
mode = 0666
user = $default_login_user
}
inet_listener {
port = 9090
}
unix_listener director-userdb {
mode = 0600
}
unix_listener login/director {
mode = 0666
}
}
service doveadm {
inet_listener {
port = 24245
}
}
service imap-login {
executable = imap-login director
}
service ipc {
unix_listener ipc {
user = dovecot
}
}
service lmtp {
inet_listener lmtp {
address = x.x.x.x
port = 24
}
}
service managesieve-login {
executable = managesieve-login director
}
service pop3-login {
executable = pop3-login director
}
ssl = no
ssl_cert = Antes de imprimir este correo piense si es necesario.Cuidemos el
medioambiente.
Re: director implementation
Il 08/03/21 17:55, Gonzalo Palacios Goicolea ha scritto: My doubt is if it's recommended to delete all dovecot.index* files before passing the traffic through de director servers or it's not required. Any information on this way will be appreciated. Is not required. Dovecot will fix previous errors itself.
director implementation
Hi All, We're going to put into production dovecot-director. As I wrote in a previous message, we have a lot of errors like these: Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Log is locked - newer log can't exist (initial_mapped=1, reason=Index mapped) Feb 28 08:50:42 server5 dovecot: imap(user@domain): Warning: fscking index file path/Maildir/dovecot.index Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:42 server5 dovecot: imap(user@domain): Error: Index path/Maildir/dovecot.index: Lost log for seq=5 offset=228: Missing middle file seq=5 (between 5..4294967295, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged (initial_mapped=1, reason=Index mapped) Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map transaction log path/Maildir/dovecot.index.log at sync_offset=10328 after locking: pread() failed: Stale file handle Feb 28 08:50:45 server5 dovecot: imap(user@domain): Error: Failed to map view for path/Maildir/dovecot.index: Missing middle file seq=5 (between 5..5, we have seqs 4): Requested newer log than exists - still after NFS flush: Log inode is unchanged My doubt is if it's recommended to delete all dovecot.index* files before passing the traffic through de director servers or it's not required. Any information on this way will be appreciated. We've dovecot-2.2.36-8.el7.x86_64 over RHEL7 Thanks and best regards -- *Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/;> Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.
