Skip to main content

dovecot mysql nfs


  • Debian Lenny
  • Dovecot querying MySQL (virtual users)
  • Remote NFS server storing Maildirs (owned by vmail, iud 500)


Dovecot is able to fetch (through IMAP or POP) Maildirs message if it has:
  • The user's HOME
  • The user's UID
  • The user's GID
For Dovecot:
  • The user's Maildir is the user's HOME appended with "/Maildir"
  • Dovecot executes the message fetching as the user's UID
  • Dovecot executes the message fetching as the user's GID

My troubles

returned something like:
home uid gid
/data/mailaka/ 500 500
I found those lines in my debug logs:
maildir: access(/data/mailaka/, rwx):
failed: No such file or directory
maildir: couldn't find root dir
mbox: root exists (/data/mailaka/
mbox: INBOX: access(/var/mail/, rw)
failed: No such file or directory
mbox: INBOX: access(/var/spool/mail/, rw)
failed: No such file or directory
mbox: INBOX defaulted to /data/mailaka/
Dovecot tried to look for the Maildir structure in
which doesnt exist on my system.

The solution

I found that my
may return an additional column "mail", sot that the result is:
home mail uid gid
/data/mailaka/ /data/mailaka/ 500 500
Dovecot immediately found my messages...

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X" -o ./bin -p 10 ./cmd/... go: downloading v3.53.1 ... ... ... go install -ldflags "-X" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"\") \