--On Friday, September 11, 2009 1:35 PM -0400 Victor Duchovni
<victor.ducho...@morganstanley.com> wrote:
On Fri, Sep 11, 2009 at 10:27:55AM -0700, Quanah Gibson-Mount wrote:
Any ideas on why this would be reporting above error every few minutes,
when everything seems to be correct?
Some nss library is causing "postdrop" to chdir? What the working
directory of the process?
This is a standalone mac system, not using nss that I can see. :/
Well, "nss" or otherwise, one plausible explanation is that the process
is not in the right directory... Otherwise, perhaps "postdrop" is no
longer setgid, or the directory permissions of /var/spool/postfix/public/
or /var/spool/postfix/ are wrong:
$ ls -ld /var/spool/postfix/{,public/}
drwxr-xr-x 16 root root 4096 Aug 18 15:24
/var/spool/postfix/ drwx--x--- 2 postfix postdrop 4096 Aug 18
15:24 /var/spool/postfix/public/
Hm, postdrop is setgid:
zimbra:conf root# ls -l /opt/zimbra/postfix/sbin/postdrop
-rwxr-sr-x 1 root _postdrop 285180 Aug 3 01:38
/opt/zimbra/postfix/sbin/postdrop
Directory perms seem right too:
zimbra:postfix root# ls -ld spool/{,public/}
drwxr-xr-x 16 _postfix _postfix 544 Jul 5 13:08 spool/
drwx--x--- 7 _postfix _postdrop 238 Sep 11 17:49 spool/public/
Changing the pickup FIFO to be _postfix instead of _postdrop didn't change
the behavior.
Running postdrop -v as didn't throw any error. :/
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
