I observed regular error messages in the Dovecot logs ages ago but w/o seeing any misbehavior. But finally decided to look deeper into it and also reached out to the Dovecot community.
The error looks like this:
imap(USERNAME)<6637><fB95wfXo7tFbEJQa>: Error: stat(/srv/customers/mail/$CUSTOMER/$DOMAIN/$USER/Maildir/.dovecot.sieve/tmp) failed: Not a directory
That message is because Dovecot thinks that .dovecot.sieve is a mailbox/folder (as maildir++ format is used). I've been told by the Dovecot community that it is a very bad idea and not at all recommended to use the same directory as home AND mail_location but apparently that is currently the default for Froxlor?
I think my settings are pretty default:
homedir: /srv/customers/mail
maildirname: Maildir
So in the mail_users table there is always /srv/customers/mail/ in homedir and $CUSTOMER/$DOMAIN/$USER/Maildir/ in maildir.
The userdb lookup in Dovecot as documented by Froxlor is:
user_query = SELECT CONCAT(homedir, maildir) AS home, CONCAT('maildir:', homedir, maildir) AS mail, uid, gid, CONCAT('*:storage=', quota, 'M') as quota_rule FROM mail_users WHERE (username = '%u' OR email = '%u')
So this returns the same directory for home and mail indeed.
Apparently there is a workaround to avoid that error but is also in general performance degrading which is to set
maildir_stat_dirs = yes
So overall this leaves some questions:
Is that a known issue or does it qualify to handle it as a bugreport (or improvement request) to use different home and mail dirs for Dovecot?
Should the maildir_stat_dirs = yes workaround be reflected in the configuration documentation?
Or is there anything wrong in my own Froxlor setup?
Question
woro
Hi,
I'm using Froxlor with Dovecot under the hood.
I observed regular error messages in the Dovecot logs ages ago but w/o seeing any misbehavior. But finally decided to look deeper into it and also reached out to the Dovecot community.
The error looks like this:
imap(USERNAME)<6637><fB95wfXo7tFbEJQa>: Error: stat(/srv/customers/mail/$CUSTOMER/$DOMAIN/$USER/Maildir/.dovecot.sieve/tmp) failed: Not a directory
That message is because Dovecot thinks that .dovecot.sieve is a mailbox/folder (as maildir++ format is used). I've been told by the Dovecot community that it is a very bad idea and not at all recommended to use the same directory as home AND mail_location but apparently that is currently the default for Froxlor?
I think my settings are pretty default:
homedir: /srv/customers/mail
maildirname: Maildir
So in the mail_users table there is always /srv/customers/mail/ in homedir and $CUSTOMER/$DOMAIN/$USER/Maildir/ in maildir.
The userdb lookup in Dovecot as documented by Froxlor is:
user_query = SELECT CONCAT(homedir, maildir) AS home, CONCAT('maildir:', homedir, maildir) AS mail, uid, gid, CONCAT('*:storage=', quota, 'M') as quota_rule FROM mail_users WHERE (username = '%u' OR email = '%u')
So this returns the same directory for home and mail indeed.
Apparently there is a workaround to avoid that error but is also in general performance degrading which is to set
maildir_stat_dirs = yes
So overall this leaves some questions:
Is that a known issue or does it qualify to handle it as a bugreport (or improvement request) to use different home and mail dirs for Dovecot?
Should the maildir_stat_dirs = yes workaround be reflected in the configuration documentation?
Or is there anything wrong in my own Froxlor setup?
Thanks
Wolfgang
4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now