[Dovecot] Error "Initializing mail storage ..." after upgrading to 2.2.10
Hi,
I did the upgrade frpom 1.2.x to 2.2.10 and had some warnings/errors on a very few accounts/mailboxes. All of them where permission related and solved.
Dovecot rocks again.
But on one mailbox I do get an error:
Error: user rechnnugseingang-animationsinstitut: Initialization failed: Initializing mail storage from mail_location setting failed
Error: Invalid user settings. Refer to server log for more information.
There is a homedirectory and the permissions are set like on all other accounts.
The username is quite long (35 characters) but an other one with 34 is working fine.
And before the upgrade there was no error.
Thnaks for any help or hint. Regards . Götz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
But on one mailbox I do get an error:
Error: user rechnnugseingang-animationsinstitut: Initialization failed: Initializing mail storage from mail_location setting failed
Error: Invalid user settings. Refer to server log for more information.
Is above error the only error in the log?
There is a homedirectory and the permissions are set like on all other accounts.
The username is quite long (35 characters) but an other one with 34 is working fine.
I do not have such long names ...
I suggest to turn on mail_debug, then you see all paths a.s.o.
Steffen Kaiser
Am 27.02.14 09:41, schrieb Steffen Kaiser:
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
But on one mailbox I do get an error:
Error: user rechnnugseingang-animationsinstitut: Initialization failed: Initializing mail storage from mail_location setting failed
Error: Invalid user settings. Refer to server log for more information.
Is above error the only error in the log?
Yes, thats the only log for about 8 hours +- now.
There is a homedirectory and the permissions are set like on all other accounts.
The username is quite long (35 characters) but an other one with 34 is working fine.
I do not have such long names ...
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
/Götz
On 2/27/2014 3:48 AM, Götz Reinicke - IT Koordinator goetz.reinicke@filmakademie.de wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
But on one mailbox I do get an error: Error: user rechnnugseingang-animationsinstitut: Initialization failed: Initializing mail storage from mail_location setting failed Error: Invalid user settings. Refer to server log for more information.
Is above error the only error in the log?
Yes, thats the only log for about 8 hours +- now.
There is a homedirectory and the permissions are set like on all other accounts. The username is quite long (35 characters) but an other one with 34 is working fine.
I do not have such long names ...
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
doveconf -n output?
(should have provided that in the first email)
Am 27.02.14 13:27, schrieb Charles Marcus:
On 2/27/2014 3:48 AM, Götz Reinicke - IT Koordinator goetz.reinicke@filmakademie.de wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
But on one mailbox I do get an error: Error: user rechnnugseingang-animationsinstitut: Initialization failed: Initializing mail storage from mail_location setting failed Error: Invalid user settings. Refer to server log for more information.
Is above error the only error in the log?
Yes, thats the only log for about 8 hours +- now.
There is a homedirectory and the permissions are set like on all other accounts. The username is quite long (35 characters) but an other one with 34 is working fine.
I do not have such long names ...
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
doveconf -n output?
[root@mail ~]# doveconf -n # 2.2.10: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2148) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2151) # OS: Linux 2.6.18-371.4.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.10 (Tikanga) auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_location = mbox:~/:INBOX=/var/mail/%u mail_privileged_group = mail passdb { driver = pam } protocols = imap pop3 service auth { user = root } service imap-login { process_limit = 1024 process_min_avail = 10 service_count = 1 } service imap { process_limit = 1024 vsz_limit = 1 G } service pop3-login { process_limit = 1024 process_min_avail = 10 service_count = 1 } service pop3 { process_limit = 1024 vsz_limit = 1 G } ssl_ca = </etc/pki/tls/certs/ca-bundle_all.crt ssl_cert = </etc/pki/tls/certs/mail_filmakademie_de.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/pki/tls/private/mail_filmakademie_de.key userdb { driver = passwd } protocol imap { mail_max_userip_connections = 20 }
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
But you'll see lines with home= mail= a.s.o. Are these settings correct? Maybe, post them, too.
Steffen
Am 27.02.14 17:06, schrieb Steffen:
Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
But you'll see lines with home= mail= a.s.o. Are these settings correct? Maybe, post them, too.
I just realised, that I used just a basic configuration (from the migration); I just added and started with the big conf.d and added my setting.
There is still the same problem/error in the log, but with some more text:
E.g. the rechnungseingang-finanzbuchhaltung looks like:
Feb 27 16:59:55 imap(rechnungseingang-finanzbuchhaltung): Debug: Effective uid=3473, gid=1182, home=/home/misc_accounts/rechnungseingang-finanzbuchhaltung
Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Debug: Effective uid=3474, gid=1182, home=
Feb 27 17:02:11 auth-worker(19896): Debug: pam(rechnungseingang-animationsinstitut,172.17.25.85): lookup service=dovecot Feb 27 17:02:11 auth-worker(19896): Debug: pam(rechnungseingang-animationsinstitut,172.17.25.85): #1/1 style=1 msg=Password: Feb 27 17:02:11 auth: Debug: client passdb out: OK 1 user=rechnungseingang-animationsinstitut Feb 27 17:02:11 auth-worker(19896): Debug: passwd(rechnungseingang-animationsinstitut,172.17.25.85): lookup Feb 27 17:02:11 auth: Debug: master userdb out: USER 3536191489 rechnungseingang-animationsinstitut system_groups_user=rechnungseingang-animationsinstitut uid=3474 gid=1182 home auth_token=58932681706c22720023a40104779c049ae2ac42 Feb 27 17:02:11 imap-login: Info: Login: user=<rechnungseingang-animationsinstitut>, method=PLAIN, rip=172.17.25.85, lip=193.196.129.3, mpid=21531, TLS, session=<dAWscWXzyQCsERlV> Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Debug: Effective uid=3474, gid=1182, home= Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/:INBOX=/var/mail/rechnungseingang-animationsinstitut Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Error: user rechnungseingang-animationsinstitut: Initialization failed: Namespace '': Home directory not set for user. Can't expand ~/ for mail root dir in: ~/:INBOX=/var/mail/rechnungseingang-animationsinstitut Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Error: Invalid user settings. Refer to server log for more information.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 17:06, schrieb Steffen:
Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
But you'll see lines with home= mail= a.s.o. Are these settings correct? Maybe, post them, too.
I just realised, that I used just a basic configuration (from the migration); I just added and started with the big conf.d and added my setting.
There is still the same problem/error in the log, but with some more text:
E.g. the rechnungseingang-finanzbuchhaltung looks like:
Feb 27 16:59:55 imap(rechnungseingang-finanzbuchhaltung): Debug: Effective uid=3473, gid=1182, home=/home/misc_accounts/rechnungseingang-finanzbuchhaltung
Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Debug: Effective uid=3474, gid=1182, home=
list=yes, subscriptions=yes location=mbox:~/:INBOX=/var/mail/rechnungseingang-animationsinstitut
See that next Info line:
!!!! Home directory not set for user. Can't expand ~/ for mail root dir in: ~/ !!!!
In contrast to rechnungseingang-finanzbuchhaltung your userdb does not return no home dir for rechnungseingang-animationsinstitut, therefore your mail_location ~/ expands to the root directory "/".
You have to correct your userdb. Maybe you need to clean the cache:
doveadm auth cache flush
Steffen Kaiser
Am 28.02.14 08:37, schrieb Steffen Kaiser:
On Thu, 27 Feb 2014, Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 17:06, schrieb Steffen:
Götz Reinicke - IT Koordinator wrote:
Am 27.02.14 09:41, schrieb Steffen Kaiser:
I suggest to turn on mail_debug, then you see all paths a.s.o.
Switched it on, but there are no more error messages.
But you'll see lines with home= mail= a.s.o. Are these settings correct? Maybe, post them, too.
I just realised, that I used just a basic configuration (from the migration); I just added and started with the big conf.d and added my setting.
There is still the same problem/error in the log, but with some more text:
E.g. the rechnungseingang-finanzbuchhaltung looks like:
Feb 27 16:59:55 imap(rechnungseingang-finanzbuchhaltung): Debug: Effective uid=3473, gid=1182, home=/home/misc_accounts/rechnungseingang-finanzbuchhaltung
Feb 27 17:02:11 imap(rechnungseingang-animationsinstitut): Debug: Effective uid=3474, gid=1182, home=
list=yes, subscriptions=yes location=mbox:~/:INBOX=/var/mail/rechnungseingang-animationsinstitut
See that next Info line:
!!!! Home directory not set for user. Can't expand ~/ for mail root dir in: ~/ !!!!
In contrast to rechnungseingang-finanzbuchhaltung your userdb does not return no home dir for rechnungseingang-animationsinstitut, therefore your mail_location ~/ expands to the root directory "/".
You have to correct your userdb. Maybe you need to clean the cache:
doveadm auth cache flush
Hi,
[root@mail ~]# doveadm auth cache flush doveadm(root): Error: userdb lookup: connect(/var/run/dovecotauth-master) failed: No such file or directory 0 cache entries flushed
On the other hand I can confirm, that the user has a homedirectory which he can access and write to. (e.g. there is a .forward file written by that user.)
Strange. Cheers . Götz
Am 28.02.14 09:19, schrieb Götz Reinicke - IT Koordinator: <...>
Hi, thanks to all suggestions, but it looks like the long username (35 letters) causes that problem, that just one out of about 1.000 users cant log in.
We shorted/changed the username to less than 35 letters and every thing is fine now.
dovecot-2.2.10-1_14.el5 Red Hat Enterprise Linux Server release 5.10 CPU architecture x86_64 SMP Local Filesystem ext3 PAM authentication with ldap backend.
May be that's a bug? Or feature?
Regards . Götz
Am 04.03.2014 09:03, schrieb Götz Reinicke - IT Koordinator:
Am 28.02.14 09:19, schrieb Götz Reinicke - IT Koordinator: <...>
Hi, thanks to all suggestions, but it looks like the long username (35 letters) causes that problem, that just one out of about 1.000 users cant log in.
We shorted/changed the username to less than 35 letters and every thing is fine now.
dovecot-2.2.10-1_14.el5 Red Hat Enterprise Linux Server release 5.10 CPU architecture x86_64 SMP Local Filesystem ext3 PAM authentication with ldap backend.
May be that's a bug? Or feature?
Regards . Götz
reading this
http://www.rfc-editor.org/errata_search.php?rfc=3696&eid=1690
it should be a bug , until you did not go over the total max limit but you may look in ldap problems too, perhaps there is a limit too
Best Regards MfG Robert Schetterer
Am 04.03.14 09:24, schrieb Robert Schetterer:
Am 04.03.2014 09:03, schrieb Götz Reinicke - IT Koordinator:
Am 28.02.14 09:19, schrieb Götz Reinicke - IT Koordinator: <...>
Hi, thanks to all suggestions, but it looks like the long username (35 letters) causes that problem, that just one out of about 1.000 users cant log in.
We shorted/changed the username to less than 35 letters and every thing is fine now.
dovecot-2.2.10-1_14.el5 Red Hat Enterprise Linux Server release 5.10 CPU architecture x86_64 SMP Local Filesystem ext3 PAM authentication with ldap backend.
May be that's a bug? Or feature?
Regards . Götz62
reading this
http://www.rfc-editor.org/errata_search.php?rfc=3696&eid=1690
it should be a bug , until you did not go over the total max limit but you may look in ldap problems too, perhaps there is a limit too
Thanks for your feedback,
from that RFC Document it looks like we are save. 35 < 64 characters.
However, the problem is solved when WE change the users login name, so for curiosity: what has been changed in the dovecot code?
Regards . Götz
participants (5)
-
Charles Marcus
-
Götz Reinicke - IT Koordinator
-
Robert Schetterer
-
Steffen
-
Steffen Kaiser