I've seen issues with postdrop for years, complaining that about permission
denied errors, such as:
postfix/postdrop[4158]: warning: mail_queue_enter: create file
maildrop/768314.4158: Permission denied
I'm not entirely clear why they occur. It seems related to postfix being
stopped while attempting to write to this location. When that happens, an
orphan postdrop process is left behind, like:
zimbra 26222 0.0 0.0 45828 4164 ? S 11:40 0:00
/opt/zimbra/common/sbin/postdrop -r
The only way to fix the problem is to kill those processes. Once postfix
is restarted, thihngs continue to work as expected. Permissions appear
fine, and again, this problem is not seen unless postfix is stopped while
postdrop is attempting to write out to the spool/maildrop location.
drwxr-xr-x 16 root root 4096 Dec 10 01:03
/opt/zimbra/data/postfix/spool
drwx-wx--- 2 postfix postdrop 4096 Dec 10 01:14
/opt/zimbra/data/postfix/spool/maildrop
Is this a bug in postdrop itself? Should the master postfix processes wait
until postdrop completes before shutting down? I.e., I'm not clear on why
it loses its ability to write to the directory on shutdown.
Thanks,
Quanah
--
Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
