Sieve doesn't work after LTMP Director implementation

2021-04-12 Thread Gonzalo Palacios Goicolea 

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: Quota - Invalid bytes limit

2021-04-08 Thread Gonzalo Palacios Goicolea 

Hi

Just for if it's helpful for anyone, I have solved the issue modifying 
the quota-warning script. I realized about this log line:


Apr  8 09:34:24 server dovecot: lda(u...@domain.es): Debug: Ignoring 
overridden (-o) userdb setting: plugin/quota_rule


So I changed at the script this line

#cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o 
"plugin/quota_rule=*:bytes=%$"


whit this one:

cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER

And now it's working fine.

Best regards

El 25/03/2021 a las 12:30, Gonzalo Palacios Goicolea escribió:


Hi,

More info. At previous version (dovecot-2.2.10-1_14.el6.x86_64) we 
didn't installed dovecot-pigeonhole, but for this one 
(dovecot-2.2.36-8.el7.x86_64) it was mandatory or dovecot didn't start 
because of this error:


"doveconf: Fatal: Error in configuration file 
/etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve"


May it be related?

Thanks and best regards

El 22/03/2021 a las 8:47, Gonzalo Palacios Goicolea escribió:


Hi

Has anyone experienced this issue? I'm not able to debug it.

Config, users, permissions, etc are the same as in the previous 
version, where it worked without problems.


If anyone can help it would be appreciated, I don't know what else look.

Thanks and best regards

El 16/03/2021 a las 11:40, Gonzalo Palacios Goicolea escribió:


Hi All,

Since upgrading to RHEL7 and  we're not able to get quota warnings work.

We get the error "User initialization failed: Failed to initialize 
quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid 
bytes limit:"


/mar 16 10:29:27 lda(user@domain): Quota: Executing warning: 
quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 gonzalo: mar 16 10:29:27 lda(user@domain): 
Quota: Executing warning: quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Loading 
modules from directory: /usr/lib64/dovecot//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib10_quota_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib15_notify_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: auth 
USER input: user@domain home=/buzones/externos/4/215283255776546 
uid=508 gid=503 quota_rule=*:bytes=2147483648//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Ignoring 
overridden (-o) userdb setting: plugin/quota_rule//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: 
Effective uid=508, gid=503, home=/buzones/externos/4/215283255776546//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
root: name=_backup backend=maildir args=ns=//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
rule: root=_backup mailbox=* bytes=0 messages=0//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Error: User 
initialization failed: Failed to initialize quota: Invalid quota 
root quota: Invalid rule *:bytes=: Invalid bytes limit://
//Mar 16 10:29:27 buzonn5 dovecot: lda: Fatal: Invalid user 
settings. Refer to server log for more information./


This is the quota-warning script:


/#!/bin/sh//
//#Variables//
//PERCENT=$1//
//USER=$2//
//FECHA=`date '+%b %d %H:%M:%S'`//
//
//#Logueo del evento//
//echo "$FECHA lda($USER): Quota: Executing warning: quota-warning 
$PERCENT $USER" >> /var/log/dovecot/dovecot.log//
//logger -p local1.notice -f /var/log/dovecot/dovecot.log "$FECHA 
lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER"//

//
//cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o 
"plugin/quota_rule=*:bytes=%$"//

//From: postmaster at domain//
//Subject: Alerta de Capacidad//
//Date: `date`//
//
//El espacio asignado para el almacenamiento de su correo ha 
superado el $PERCENT% de su capacidad total. Por ello, se recomienda 
que elimine correos y/o vacie la papelera para liberar espacio.//

//Mensaje enviado desde `hostname`//
//
//Atentamente,//
//
//--//
//Responsable correo //
//postmaster at domain//
//
//EOF//
/
-

This is 90-quota.conf

/plugin {//
//  quota = maildir:_backup:ns=//
//}//
//
//plugin {//
//  quota_exceeded_message = El espacio asignado para el 
almacenamiento del correo del destinatario ha superado su capacidad 
total. Por ello, el correo que usted intenta enviar no se puede 
entregar al destinatario.//

//  quota_warning = storage=70%% quota-warning 70 %u//
//  quota_warning1 = storage=90%% quota-warning 90 %u//
//  quota_warning2 = storage=95%% quota-warning 95 %u//
//  quota_warning3 = storage=99%% quota-warning 99 %u//
//}//
//
//service quota-warning {//
//  executable =

Re: Quota - Invalid bytes limit

2021-03-25 Thread Gonzalo Palacios Goicolea 

Hi,

More info. At previous version (dovecot-2.2.10-1_14.el6.x86_64) we 
didn't installed dovecot-pigeonhole, but for this one 
(dovecot-2.2.36-8.el7.x86_64) it was mandatory or dovecot didn't start 
because of this error:


"doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: 
protocols: Unknown protocol: sieve"


May it be related?

Thanks and best regards

El 22/03/2021 a las 8:47, Gonzalo Palacios Goicolea escribió:


Hi

Has anyone experienced this issue? I'm not able to debug it.

Config, users, permissions, etc are the same as in the previous 
version, where it worked without problems.


If anyone can help it would be appreciated, I don't know what else look.

Thanks and best regards

El 16/03/2021 a las 11:40, Gonzalo Palacios Goicolea escribió:


Hi All,

Since upgrading to RHEL7 and  we're not able to get quota warnings work.

We get the error "User initialization failed: Failed to initialize 
quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid bytes 
limit:"


/mar 16 10:29:27 lda(user@domain): Quota: Executing warning: 
quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 gonzalo: mar 16 10:29:27 lda(user@domain): 
Quota: Executing warning: quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Loading 
modules from directory: /usr/lib64/dovecot//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib10_quota_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib15_notify_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: auth USER 
input: user@domain home=/buzones/externos/4/215283255776546 uid=508 
gid=503 quota_rule=*:bytes=2147483648//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Ignoring 
overridden (-o) userdb setting: plugin/quota_rule//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Effective 
uid=508, gid=503, home=/buzones/externos/4/215283255776546//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
root: name=_backup backend=maildir args=ns=//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
rule: root=_backup mailbox=* bytes=0 messages=0//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Error: User 
initialization failed: Failed to initialize quota: Invalid quota root 
quota: Invalid rule *:bytes=: Invalid bytes limit://
//Mar 16 10:29:27 buzonn5 dovecot: lda: Fatal: Invalid user settings. 
Refer to server log for more information./


This is the quota-warning script:


/#!/bin/sh//
//#Variables//
//PERCENT=$1//
//USER=$2//
//FECHA=`date '+%b %d %H:%M:%S'`//
//
//#Logueo del evento//
//echo "$FECHA lda($USER): Quota: Executing warning: quota-warning 
$PERCENT $USER" >> /var/log/dovecot/dovecot.log//
//logger -p local1.notice -f /var/log/dovecot/dovecot.log "$FECHA 
lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER"//

//
//cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o 
"plugin/quota_rule=*:bytes=%$"//

//From: postmaster at domain//
//Subject: Alerta de Capacidad//
//Date: `date`//
//
//El espacio asignado para el almacenamiento de su correo ha superado 
el $PERCENT% de su capacidad total. Por ello, se recomienda que 
elimine correos y/o vacie la papelera para liberar espacio.//

//Mensaje enviado desde `hostname`//
//
//Atentamente,//
//
//--//
//Responsable correo //
//postmaster at domain//
//
//EOF//
/
-

This is 90-quota.conf

/plugin {//
//  quota = maildir:_backup:ns=//
//}//
//
//plugin {//
//  quota_exceeded_message = El espacio asignado para el 
almacenamiento del correo del destinatario ha superado su capacidad 
total. Por ello, el correo que usted intenta enviar no se puede 
entregar al destinatario.//

//  quota_warning = storage=70%% quota-warning 70 %u//
//  quota_warning1 = storage=90%% quota-warning 90 %u//
//  quota_warning2 = storage=95%% quota-warning 95 %u//
//  quota_warning3 = storage=99%% quota-warning 99 %u//
//}//
//
//service quota-warning {//
//  executable = script 
/etc/dovecot/scripts_notification_quota/quota-warning.sh//

//  user = vmail//
//  unix_listener quota-warning {//
//    user = vmail//
//  }//
//}/

Getting user attibutes and quota with doveadms works right:

/# doveadm user user@domain//
//field   value//
//uid 508//
//gid 503//
//home    /buzones/externos/4/215283255776546//
//mail maildir:/buzones/externos/4/215283255776546/Maildir//
//quota_rule *:bytes=2147483648//
//# doveadm quota get -u user@domain//
//Quota name Type  Value Limit %//
//_backup    STORAGE 1153093 2097152 54//
//_backup    MESSAGE   44347   

Re: Quota - Invalid bytes limit

2021-03-22 Thread Gonzalo Palacios Goicolea 

Hi

Has anyone experienced this issue? I'm not able to debug it.

Config, users, permissions, etc are the same as in the previous version, 
where it worked without problems.


If anyone can help it would be appreciated, I don't know what else look.

Thanks and best regards

El 16/03/2021 a las 11:40, Gonzalo Palacios Goicolea escribió:


Hi All,

Since upgrading to RHEL7 and dovecot-2.2.36-8.el7.x86_64 we're not 
able to get quota warnings work.


We get the error "User initialization failed: Failed to initialize 
quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid bytes 
limit:"


/mar 16 10:29:27 lda(user@domain): Quota: Executing warning: 
quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 gonzalo: mar 16 10:29:27 lda(user@domain): 
Quota: Executing warning: quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Loading 
modules from directory: /usr/lib64/dovecot//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib10_quota_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib15_notify_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: auth USER 
input: user@domain home=/buzones/externos/4/215283255776546 uid=508 
gid=503 quota_rule=*:bytes=2147483648//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Ignoring 
overridden (-o) userdb setting: plugin/quota_rule//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Effective 
uid=508, gid=503, home=/buzones/externos/4/215283255776546//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
root: name=_backup backend=maildir args=ns=//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota 
rule: root=_backup mailbox=* bytes=0 messages=0//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Error: User 
initialization failed: Failed to initialize quota: Invalid quota root 
quota: Invalid rule *:bytes=: Invalid bytes limit://
//Mar 16 10:29:27 buzonn5 dovecot: lda: Fatal: Invalid user settings. 
Refer to server log for more information./


This is the quota-warning script:


/#!/bin/sh//
//#Variables//
//PERCENT=$1//
//USER=$2//
//FECHA=`date '+%b %d %H:%M:%S'`//
//
//#Logueo del evento//
//echo "$FECHA lda($USER): Quota: Executing warning: quota-warning 
$PERCENT $USER" >> /var/log/dovecot/dovecot.log//
//logger -p local1.notice -f /var/log/dovecot/dovecot.log "$FECHA 
lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER"//

//
//cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o 
"plugin/quota_rule=*:bytes=%$"//

//From: postmaster at domain//
//Subject: Alerta de Capacidad//
//Date: `date`//
//
//El espacio asignado para el almacenamiento de su correo ha superado 
el $PERCENT% de su capacidad total. Por ello, se recomienda que 
elimine correos y/o vacie la papelera para liberar espacio.//

//Mensaje enviado desde `hostname`//
//
//Atentamente,//
//
//--//
//Responsable correo //
//postmaster at domain//
//
//EOF//
/
-

This is 90-quota.conf

/plugin {//
//  quota = maildir:_backup:ns=//
//}//
//
//plugin {//
//  quota_exceeded_message = El espacio asignado para el 
almacenamiento del correo del destinatario ha superado su capacidad 
total. Por ello, el correo que usted intenta enviar no se puede 
entregar al destinatario.//

//  quota_warning = storage=70%% quota-warning 70 %u//
//  quota_warning1 = storage=90%% quota-warning 90 %u//
//  quota_warning2 = storage=95%% quota-warning 95 %u//
//  quota_warning3 = storage=99%% quota-warning 99 %u//
//}//
//
//service quota-warning {//
//  executable = script 
/etc/dovecot/scripts_notification_quota/quota-warning.sh//

//  user = vmail//
//  unix_listener quota-warning {//
//    user = vmail//
//  }//
//}/

Getting user attibutes and quota with doveadms works right:

/# doveadm user user@domain//
//field   value//
//uid 508//
//gid 503//
//home    /buzones/externos/4/215283255776546//
//mail maildir:/buzones/externos/4/215283255776546/Maildir//
//quota_rule *:bytes=2147483648//
//# doveadm quota get -u user@domain//
//Quota name Type  Value Limit %//
//_backup    STORAGE 1153093 2097152 54//
//_backup    MESSAGE   44347   - /

It also works fine with ldapsearch


/# ldapsearch -x -D "cn=mail_admin,cn=users,dc=domain,dc=es" -w 
** -b "dc=domain,dc=es" -h ldap.host mail=user@domain 
mailquotasize//

//# extended LDIF//
//#//
//# LDAPv3//
//# base  with scope subtree//
//# filter: mail=user@domain//
//# requesting: mailquotasize//
//#//
//
//# user@domain, users, domain.es//
//dn: cn=user@domain,cn=users,dc=doma

Quota - Invalid bytes limit

2021-03-16 Thread Gonzalo Palacios Goicolea 

Hi All,

Since upgrading to RHEL7 and dovecot-2.2.36-8.el7.x86_64 we're not able 
to get quota warnings work.


We get the error "User initialization failed: Failed to initialize 
quota: Invalid quota root quota: Invalid rule *:bytes=: Invalid bytes 
limit:"


/mar 16 10:29:27 lda(user@domain): Quota: Executing warning: 
quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 gonzalo: mar 16 10:29:27 lda(user@domain): 
Quota: Executing warning: quota-warning 90 user@domain//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Loading 
modules from directory: /usr/lib64/dovecot//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib10_quota_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib15_notify_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Module 
loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: auth USER 
input: user@domain home=/buzones/externos/4/215283255776546 uid=508 
gid=503 quota_rule=*:bytes=2147483648//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Ignoring 
overridden (-o) userdb setting: plugin/quota_rule//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Effective 
uid=508, gid=503, home=/buzones/externos/4/215283255776546//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota root: 
name=_backup backend=maildir args=ns=//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Debug: Quota rule: 
root=_backup mailbox=* bytes=0 messages=0//
//Mar 16 10:29:27 buzonn5 dovecot: lda(user@domain): Error: User 
initialization failed: Failed to initialize quota: Invalid quota root 
quota: Invalid rule *:bytes=: Invalid bytes limit://
//Mar 16 10:29:27 buzonn5 dovecot: lda: Fatal: Invalid user settings. 
Refer to server log for more information./


This is the quota-warning script:


/#!/bin/sh//
//#Variables//
//PERCENT=$1//
//USER=$2//
//FECHA=`date '+%b %d %H:%M:%S'`//
//
//#Logueo del evento//
//echo "$FECHA lda($USER): Quota: Executing warning: quota-warning 
$PERCENT $USER" >> /var/log/dovecot/dovecot.log//
//logger -p local1.notice -f /var/log/dovecot/dovecot.log "$FECHA 
lda($USER): Quota: Executing warning: quota-warning $PERCENT $USER"//

//
//cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o 
"plugin/quota_rule=*:bytes=%$"//

//From: postmaster at domain//
//Subject: Alerta de Capacidad//
//Date: `date`//
//
//El espacio asignado para el almacenamiento de su correo ha superado el 
$PERCENT% de su capacidad total. Por ello, se recomienda que elimine 
correos y/o vacie la papelera para liberar espacio.//

//Mensaje enviado desde `hostname`//
//
//Atentamente,//
//
//--//
//Responsable correo //
//postmaster at domain//
//
//EOF//
/
-

This is 90-quota.conf

/plugin {//
//  quota = maildir:_backup:ns=//
//}//
//
//plugin {//
//  quota_exceeded_message = El espacio asignado para el almacenamiento 
del correo del destinatario ha superado su capacidad total. Por ello, el 
correo que usted intenta enviar no se puede entregar al destinatario.//

//  quota_warning = storage=70%% quota-warning 70 %u//
//  quota_warning1 = storage=90%% quota-warning 90 %u//
//  quota_warning2 = storage=95%% quota-warning 95 %u//
//  quota_warning3 = storage=99%% quota-warning 99 %u//
//}//
//
//service quota-warning {//
//  executable = script 
/etc/dovecot/scripts_notification_quota/quota-warning.sh//

//  user = vmail//
//  unix_listener quota-warning {//
//    user = vmail//
//  }//
//}/

Getting user attibutes and quota with doveadms works right:

/# doveadm user user@domain//
//field   value//
//uid 508//
//gid 503//
//home    /buzones/externos/4/215283255776546//
//mail    maildir:/buzones/externos/4/215283255776546/Maildir//
//quota_rule *:bytes=2147483648//
//# doveadm quota get -u user@domain//
//Quota name Type  Value Limit %//
//_backup    STORAGE 1153093 2097152 54//
//_backup    MESSAGE   44347   - /

It also works fine with ldapsearch


/# ldapsearch -x -D "cn=mail_admin,cn=users,dc=domain,dc=es" -w 
** -b "dc=domain,dc=es" -h ldap.host mail=user@domain 
mailquotasize//

//# extended LDIF//
//#//
//# LDAPv3//
//# base  with scope subtree//
//# filter: mail=user@domain//
//# requesting: mailquotasize//
//#//
//
//# user@domain, users, domain.es//
//dn: cn=user@domain,cn=users,dc=domain,dc=es//
//mailquotasize: 2147483648/


I've been googling but I can't find where the problem may be. Can you 
please help me?


This is the whole config:

/doveconf -n//
//# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf//
//# Pigeonhole version 0.4.24 (124e06aa)//
//# OS: Linux 3.10.0-1160.6.1.el7.x86_64 x86_64 Red Hat Enterprise Linux 
Server release 7.9 (Maipo)//

//# Hostname: host.domain//

director implementation

2021-03-08 Thread Gonzalo Palacios Goicolea 

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.

start dovecot multiple instances

2021-03-05 Thread Gonzalo Palacios Goicolea 

Hi All,

I'm trying to run dovecot with dovecot-director on the same server, 
using two different instances, but I'n not able to make the two 
instances start with systemctl (we are using RHEL7)


May be I shueld create a 
/etc/systemd/system/dovecot.service.d/service.conf file and add there 
any command?


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

Re: Failed to map transaction log path - Stale file handle

2021-03-01 Thread Gonzalo Palacios Goicolea 

Hi Aki,

Thanks for your quick answer.

I've read it's recommended to use different servers for director and 
backends. So, for a 5 backend cluster, how many director servers are 
recommended? I guess that at least 2, but if it's better to use more 
than 2, please, let me know.


Best regards

Gonzalo

El 02/03/2021 a las 8:35, Aki Tuomi escribió:

It has never been safe, not even in 2.2.10, to access mail from multiple 
backends concurrently. You have just gotten lucky.

You must use director (or similar solution) to ensure all sessions end up in 
same server.

Aki


On 02/03/2021 09:26 Gonzalo Palacios Goicolea  
wrote:


Hi Aki
We're using NFS v3. Should we use v4 to avoid this problem?

Regarding concurrent access, when a user uses more than one device it can go to 
any of the servers. It's the same config we had with dovecot-2.2.10 that never 
gave us this problem.
So, if the issue is related to concurrent access, is it any configuration we 
can apply to solve it? Or the only solution is director?
Thanks again

El 02/03/2021 a las 7:27, Aki Tuomi escribió:


On 01/03/2021 14:59 Gonzalo Palacios Goicolea  
wrote:


Hi All,
  
  We recently moved from RHEL6 to RHEL7 and updated dovecot from dovecot-2.2.10-1_14.el6.x86_64 to dovecot-2.2.36-8.el7.x86_64. We use NFS for storing the mail, and 5 servers running at the same time.

  Before updating dovecot we stopped the service and deleted all dovecot.index* 
files
  Now we're experiencing some problems. For example, when deleting an email it 
is note deleted and appears again duplicated. These are the logs:
  
  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
  
  Usually restarting the email client solves the problem for a while. We've tried deleting the indexes but it happens again some time later.
  
  This is dovecot config:
  
  dovecot -n

  # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
  # Pigeonhole version 0.4.24 (124e06aa)
  # OS: Linux 3.10.0-1160.6.1.el7.x86_64 x86_64 Red Hat Enterprise Linux Server 
release 7.9 (Maipo)
  # Hostname: server
  auth_cache_negative_ttl = 5 mins
  auth_cache_size = 500 M
  auth_cache_ttl = 5 mins
  auth_failure_delay = 5 secs
  default_vsz_limit = 1 G
  disable_plaintext_auth = no
  hostname = server
  imap_logout_format = in(bytes read)=%i out(bytes sent)=%o
  listen = *
  lock_method = dotlock
  mail_fsync = always
  mail_location = maildir:%h/Maildir
  mail_nfs_index = yes
  mail_nfs_storage = yes
  mail_plugins = " quota mail_log notify"
  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 imapflags notify
  mbox_write_locks = fcntl
  mmap_disable = yes
  namespace {
  location = maildir:%h/Maildir/_backup
  prefix = _backup.
  separator = .
  type = private
  }
  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 = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
  }
  plugin {
  mail_log_events = delete undelete expunge mailbox_delete mailbox_rename 
mailbox_create save
  mail_log_fields = uid box msgid from subject
  quota = maildir:_backup:ns=
  quota_exceeded_message = El espacio asignado para el almacenamiento del 
correo del destinatario ha superado su capacidad total. Por ello, el correo que 
usted intent

Re: Failed to map transaction log path - Stale file handle

2021-03-01 Thread Gonzalo Palacios Goicolea 

Hi Aki

We're using NFS v3. Should we use v4 to avoid this problem?

Regarding concurrent access, when a user uses more than one device it 
can go to any of the servers. It's the same config we had with 
dovecot-2.2.10 that never gave us this problem.


So, if the issue is related to concurrent access, is it any 
configuration we can apply to solve it? Or the only solution is director?


Thanks again

El 02/03/2021 a las 7:27, Aki Tuomi escribió:

On 01/03/2021 14:59 Gonzalo Palacios Goicolea  
wrote:


Hi All,
  
  We recently moved from RHEL6 to RHEL7 and updated dovecot from dovecot-2.2.10-1_14.el6.x86_64 to dovecot-2.2.36-8.el7.x86_64. We use NFS for storing the mail, and 5 servers running at the same time.

  Before updating dovecot we stopped the service and deleted all dovecot.index* 
files
  Now we're experiencing some problems. For example, when deleting an email it 
is note deleted and appears again duplicated. These are the logs:
  
  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
  
  Usually restarting the email client solves the problem for a while. We've tried deleting the indexes but it happens again some time later.
  
  This is dovecot config:
  
  dovecot -n

  # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
  # Pigeonhole version 0.4.24 (124e06aa)
  # OS: Linux 3.10.0-1160.6.1.el7.x86_64 x86_64 Red Hat Enterprise Linux Server 
release 7.9 (Maipo)
  # Hostname: server
  auth_cache_negative_ttl = 5 mins
  auth_cache_size = 500 M
  auth_cache_ttl = 5 mins
  auth_failure_delay = 5 secs
  default_vsz_limit = 1 G
  disable_plaintext_auth = no
  hostname = server
  imap_logout_format = in(bytes read)=%i out(bytes sent)=%o
  listen = *
  lock_method = dotlock
  mail_fsync = always
  mail_location = maildir:%h/Maildir
  mail_nfs_index = yes
  mail_nfs_storage = yes
  mail_plugins = " quota mail_log notify"
  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 imapflags notify
  mbox_write_locks = fcntl
  mmap_disable = yes
  namespace {
  location = maildir:%h/Maildir/_backup
  prefix = _backup.
  separator = .
  type = private
  }
  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 = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
  }
  plugin {
  mail_log_events = delete undelete expunge mailbox_delete mailbox_rename 
mailbox_create save
  mail_log_fields = uid box msgid from subject
  quota = maildir:_backup:ns=
  quota_exceeded_message = El espacio asignado para el almacenamiento del 
correo del destinatario ha superado su capacidad total. Por ello, el correo que 
usted intenta enviar no se puede entregar al destinatario.
  quota_warning = storage=70%% quota-warning 70 %u
  quota_warning1 = storage=90%% quota-warning 90 %u
  quota_warning2 = storage=95%% quota-warning 95 %u
  quota_warning3 = storage=99%% quota-warning 99 %u
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/Maildir/sieve
  sieve_extensions = +notify +imapflags
  }
  postmaster_address = postmaster@domain
  protocols = imap pop3 sieve
  service auth {
  unix_listener auth-userdb {
  group = vmail
  mode = 0666
  user = vmail
  }
  }
  service imap-login {
  inet_listener imap {
  port = 143
  }
  process_min_avail = 20
  }
  service im

Failed to map transaction log path - Stale file handle

2021-03-01 Thread Gonzalo Palacios Goicolea 

Hi All,

We recently moved from RHEL6 to RHEL7 and updated dovecot from 
dovecot-2.2.10-1_14.el6.x86_64 to dovecot-2.2.36-8.el7.x86_64. We use 
NFS for storing the mail, and 5 servers running at the same time.
Before updating dovecot we stopped the service and deleted all 
dovecot.index* files
Now we're experiencing some problems. For example, when deleting an 
email it is note deleted and appears again duplicated. These are the logs:


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


Usually restarting the email client solves the problem for a while. 
We've tried deleting the indexes but it happens again some time later.


This is dovecot config:

dovecot -n
# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.24 (124e06aa)
# OS: Linux 3.10.0-1160.6.1.el7.x86_64 x86_64 Red Hat Enterprise Linux 
Server release 7.9 (Maipo)

# Hostname: server
auth_cache_negative_ttl = 5 mins
auth_cache_size = 500 M
auth_cache_ttl = 5 mins
auth_failure_delay = 5 secs
default_vsz_limit = 1 G
disable_plaintext_auth = no
hostname = server
imap_logout_format = in(bytes read)=%i out(bytes sent)=%o
listen = *
lock_method = dotlock
mail_fsync = always
mail_location = maildir:%h/Maildir
mail_nfs_index = yes
mail_nfs_storage = yes
mail_plugins = " quota mail_log notify"
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 imapflags notify

mbox_write_locks = fcntl
mmap_disable = yes
namespace {
  location = maildir:%h/Maildir/_backup
  prefix = _backup.
  separator = .
  type = private
}
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 = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  mail_log_events = delete undelete expunge mailbox_delete 
mailbox_rename mailbox_create save

  mail_log_fields = uid box msgid from subject
  quota = maildir:_backup:ns=
  quota_exceeded_message = El espacio asignado para el almacenamiento 
del correo del destinatario ha superado su capacidad total. Por ello, el 
correo que usted intenta enviar no se puede entregar al destinatario.

  quota_warning = storage=70%% quota-warning 70 %u
  quota_warning1 = storage=90%% quota-warning 90 %u
  quota_warning2 = storage=95%% quota-warning 95 %u
  quota_warning3 = storage=99%% quota-warning 99 %u
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/Maildir/sieve
  sieve_extensions = +notify +imapflags
}
postmaster_address = postmaster@domain
protocols = imap pop3 sieve
service auth {
  unix_listener auth-userdb {
    group = vmail
    mode = 0666
    user = vmail
  }
}
service imap-login {
  inet_listener imap {
    port = 143
  }
  process_min_avail = 20
}
service imap {
  process_limit = 2048
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
  inet_listener sieve_deprecated {
    port = 2000
  }
  process_min_avail = 20
}
service pop3-login {
  inet_listener pop3 {
    port = 110
  }
  process_min_avail = 20
}
service pop3 {
  process_limit = 2048
}
service quota-warning {
  executable = script 
/etc/dovecot/scripts_notification_quota/quota-warning.sh

  unix_listener quota-warning {
    user = vmail
  }
  user = vmail
}
ssl = no
ssl_cert = http://www.uam.es/;>

Antes de imprimir este correo piense si es necesario.Cuidemos el 
medioambiente.

Re: index problems after update

2019-02-21 Thread Gonzalo Palacios Goicolea via dovecot 

El 21/02/2019 a las 10:51, Aki Tuomi via dovecot escribió:

On 21.2.2019 10.53, Hajo Locke via dovecot wrote:

Hello,

Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:

On 18 February 2019 09:28 Hajo Locke via dovecot
 wrote:


Hello,
     it seems we need a dovecot developers opinion. May be we hit a
bug or cant help ourselves.


Thanks for your answer.

Core dump with backtrace would help, if possible to acquire. Please
refer to https://dovecot.org/bugreport.html for information how to
get a core dump.

Aki


Unfortunately its hard to get a backtrace because dovecot is not
crashing. so it seems to be more a kind of logic problem in code and
no unexpected situation.
yesterday evening i had next incident. I upgraded from 2.2.33.2 to
2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken
index and delivers no new mails. it starts delivering if i delete
index files. At this point i cant tell if 2.2.36.1 also has same bug
and writes a damaged index, but very likely.  We dont know this
problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on
mbox-index code must happend which leads to this big problem. So imapd
cant do what he was created for.

For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and
will try this. In my opinion this is a major problem and i expect a
lot of affected people with version > 2.2.22 and classic mbox-storage.

Thanks,
Hajo

We consider mbox + procmail setup somewhat edge case, and if the core
dump does not point into something more generic, it will probably not
get fixed. It is more likely to have this working if you use
dovecot-lda/lmtp with sieve instead of procmail.

Aki


Hi Aki,
In support of Hajo I've to say that a few days ago I posted a similar 
issue, and I use dovecot-lda+sieve. My environment has RHEL6 and 7 
servers. When I last updated the servers RHEL6 servers mantained 
2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 
2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used 
for sympa) processed a message for a user, its indexes were corrupted, 
and the user could't access his inbox through webmail, so I had to 
delete dovecot.* files from the user mail path to get it working again.
My solution was to downgrade dovecot and dovecot-pigeonhole back to 
2.2.10-8.el7.x86_64

Regards

*Gonzalo
*

Re: index problems after update

2019-02-15 Thread Gonzalo Palacios Goicolea via dovecot 
3) 
[0x7f78b3ac6aa3] -> dovecot/imap [myuser ip.ip.ip.ip 
FETCH](main+0x329) [0x5581ac75b159] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) 
[0x7f78b36bbb97] -> dovecot/imap [myuser ip.ip.ip.ip 
FETCH](_start+0x2a) [0x5581ac75b2fa]
Feb  8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: 
master: service(imap): child 14135 killed with signal 6 (core dumped)





Thanks,
Hajo


Thanks,
Hajo


Hi,

A few days ago I posted a similar issue. My environment has RHEL6 and 7 
servers. When I last updated the servers RHEL6 servers mantained 
2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 
2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used 
for sympa) processed a message for a user, its indexes were corrupted, 
and the user could't access his inbox through webmail, so I had to 
delete dovecot.* files from the user mail path to get it working again. 
This is the error shown at the dovecot log:


Feb  5 09:33:25 buzon1 dovecot: imap(user@domain): Panic: file 
mail-index-sync-keywords.c: line 227 (keywords_update_records): 
assertion failed: (data_offset >= sizeof(struct mail_index_record))
Feb  5 09:33:25 buzon1 dovecot: imap(user@domain): Error: Raw backtrace: 
/usr/lib64/dovecot/libdovecot.so.0() [0x3713268b8a] -> 
/usr/lib64/dovecot/libdovecot.so.0() [0x3713268bf6] -> 
/usr/lib64/dovecot/libdovecot.so.0() [0x37132224aa] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x7fd) 
[0x3713aca43d] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xec) 
[0x3713acacac] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x234) 
[0x3713acbae4] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x83) 
[0x3713abcce3] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_refresh+0xe) 
[0x3713ab793e] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(maildir_sync_header_refresh+0x10) 
[0x3713a4e1e0] -> /usr/lib64/dovecot/libdovecot-storage.so.0() 
[0x3713a4e330] -> /usr/lib64/dovecot/libdovecot-storage.so.0() 
[0x3713a4f3d4] -> /usr/lib64/dovecot/libdovecot-storage.so.0() 
[0x3713a4f7b3] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xd9) 
[0x3713a4fa59] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) 
[0x3713a7d731] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) 
[0x3713a7e7b7] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) 
[0x3713aa8fc2] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xc3ec) 
[0x7fd272dfe3ec] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x5c) 
[0x3713a7f4fc] -> dovecot/imap(imap_status_get+0x7a) [0x41dbea] -> 
dovecot/imap(cmd_status+0x179) [0x413059] -> 
dovecot/imap(command_exec+0x3d) [0x4170bd] -> dovecot/imap() [0x416180] 
-> dovecot/imap() [0x41627a] -> dovecot/imap(client_handle_input+0x11d) 
[0x4164ed] -> dovecot/imap(client_input+0x6f) [0x41685f] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3713278a56] 
-> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) 
[0x3713279b27] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x37132789c8]
Feb  5 09:33:25 buzon1 dovecot: imap(user@domain): Fatal: master: 
service(imap): child 2057 killed with signal 6 (core dumped)


My solution was to downgrade dovecot and dovecot-pigeonhole back to 
2.2.10-8.el7.x86_64

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.

problem using different dovecot versions

2019-02-05 Thread Gonzalo Palacios Goicolea 
lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x5c) 
[0x3a88e7f4fc] -> dovecot/imap(imap_status_get+0x7a) [0x41dbea] -> 
dovecot/imap(cmd_status+0x179) [0x413059] -> 
dovecot/imap(command_exec+0x3d) [0x4170bd] -> dovecot/imap() [0x416180] 
-> dovecot/imap() [0x41627a] -> dovecot/imap(client_handle_input+0x11d) 
[0x4164ed] -> dovecot/imap(client_input+0x6f) [0x41685f] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3a88678a56] 
-> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) 
[0x3a88679b27] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x3a886789c8]
Feb  5 09:33:30 buzon4 dovecot: imap(user@domain): Fatal: master: 
service(imap): child 3459 killed with signal 6 (core dumped)


Due to this issue when the user goes into his webmail, he can not see 
the inbox. If I delete dovecot.* files from the user maildir it gets 
solved, but usually it happens again, so it's not the solution.


Is it any solution for this issue or should I downgrade dovecot to 
2.2.10-8.el7.x86_64 again?


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/;>