postdrop fail to create file after upgrade to 5.0.3

[echoadisan]

i was successfully upgrade from 5.0.2 to 5.0.3 on centos 4.6. thanks for all you guys make this amazing services

all email delivery normal as usually

but actually, i found same warning on zimbra.log :

Mar 22 19:24:52 domain postfix/postdrop[3624]: warning: mail_queue_enter: create file maildrop/976917.3624: No such file or directory

i has been tried to fix permission but didn't work.

how to fix this tiny problem?

tx
echo

[phoenix]

The error message states "No such file or directory" - does the directory exist and if not have you tried creating it?

[echoadisan]

yep it's exist

[root@domain spool]# find /opt/zimbra -name maildrop
/opt/zimbra/postfix-2.4.3.4z/spool/private/maildrop
/opt/zimbra/postfix-2.4.3.3z/spool/private/maildrop
/opt/zimbra/data/postfix/spool/maildrop
/opt/zimbra/data/postfix/spool/private/maildrop

[root@domain spool]# ll /opt/zimbra/data/postfix/spool/
total 56
drwx------   2 postfix postfix  4096 Mar 22 19:56 active
drwx------   2 postfix postfix  4096 Mar 22 18:21 bounce
drwx------   2 postfix postfix  4096 Mar 22 18:21 corrupt
drwx------  18 postfix postfix  4096 Mar  1 13:20 defer
drwx------  18 postfix postfix  4096 Mar  1 13:20 deferred
drwx------   2 postfix postfix  4096 Mar 22 18:21 flush
drwx------   2 postfix postfix  4096 Mar 22 18:21 hold
drwx------   2 postfix postfix  4096 Mar 22 19:56 incoming
drwxrwx---   2 postfix postdrop 4096 Mar 22 18:21 maildrop
drwxr-xr-x   2 postfix postfix  4096 Mar  4 18:40 pid
drwx------   2 postfix postfix  4096 Mar 22 18:38 private
drwx--x---   2 postfix postdrop 4096 Mar 22 18:38 public
drwx------   2 postfix postfix  4096 Mar 22 18:21 saved
drwx------   2 postfix postfix  4096 Mar 22 18:21 trace

[root@domain spool]# ll /opt/zimbra/data/postfix/spool/private
total 0
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 anvil
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 bounce
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 bsmtp
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 cyrus
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 defer
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 discard
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 error
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 ifmail
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 lmtp
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 local
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 maildrop
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 old-cyrus
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 proxymap
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 relay
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 rewrite
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 scache
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 smtp
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 smtp-amavis
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 tlsmgr
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 trace
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 uucp
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 verify
srw-rw-rw-  1 postfix postfix 0 Mar 22 18:38 virtual

i dunno which one?

tx
echo

[phoenix]

What were you trying to do when you received the error message in the logs, send a mail via the command line?

[echoadisan]

sending n receiving message work fine on webmail n outlook

i did
#/opt/zimbra/libexec/zmfixperms

but didnt solved this warning.

should i downgrade to be ZCS 5.0.2 ?

i see an announcement about 5.0.3 pulled out, is't save to my mail server?

tx
echo

[phoenix]

Originally Posted by echoadisan

i did
#/opt/zimbra/libexec/zmfixperms

I don't really understand your answers, why did you run zmfixperms? What caused the error message in the log file (wre you trying to send an email via the command line)?

If you saw the announcement about 5.0.3 being pulled then you should have seen the part that that says 'if your install is running OK then you should leave it alone' - it is fine.

[naeb]

I was having a similar problem ('permission denied' rather than 'no such file') after upgrading from 5.02 to 5.04. To get rid of the recurring message, I chmod'ed /opt/zimbra/postfix-2.4.3.4z/spool/maildrop to 777. Perhaps you can just create said directory?

Now this approach doesn't actually seem to fix the problem, it just gives up trying after receiving another permission denied from the public/pickup directory. My suspicion is that postfix is operating in the wrong place to begin with (/opt/zimbra/postfix-2.4.3.4z/ vs. /opt/zimbra/data/postfix/). Can anyone with a better knowledge of the inner workings of Zimbra confirm or deny this?

[quanah]

Originally Posted by naeb

I was having a similar problem ('permission denied' rather than 'no such file') after upgrading from 5.02 to 5.04. To get rid of the recurring message, I chmod'ed /opt/zimbra/postfix-2.4.3.4z/spool/maildrop to 777.

Nothing should be using this directory anymore. What's the output of

zmlocalconfig postfix_queue_directory

[naeb]

postfix_queue_directory = /opt/zimbra/data/postfix/spool

There is nothing in the folder /opt/zimbra/postfix-2.4.3.4z/spool/maildrop date-stamped after the six files that were originally causing the error message were deposited.

If it's of any interest, this is the format of the message received after I changed the permissions:

Mar 26 15:07:58 hostname postfix/postdrop[28682]: warning: unable to look up public/pickup: Permission denied
Mar 26 15:07:58 hostname CRON[28570]: (pam_unix) session closed for user zimbra

[AdamG]

I just upgraded from 4.5.10 to 5.0.4 on Ubuntu 6.0.6 LTS, and now I am seeing these Permission denied errors as well as no such file or directory errors in my zimbra.log.

Apr 16 11:33:23 zimbra postfix/postdrop[6901]: warning: mail_queue_enter: create file maildrop/944870.6901: Permission denied
Apr 16 11:33:26 zimbra postfix/postdrop[3142]: warning: unable to look up public/pickup: No such file or directory

My /opt/zimbra/postfix/spool directory looks very different from 4.5.10:

root@zimbra:/opt/zimbra/postfix/spool# ls -l
total 12
drwxr-xr-x 18 root root 4096 2008-04-15 19:27 defer/
drwxr-xr-x 18 root root 4096 2008-04-15 19:27 deferred/
drwxrwxrwx  2 root root 4096 2008-04-16 11:37 maildrop/

Are the new directory structure and permissions this way by design? They seem to be causing errors, plus I am no longer able to send mail from my shell scripts using /usr/bin/mail.
I would like to know what these errors mean as far as my mail delivery is concerned (no one has complained of missing mail yet).

I had installed 5.0.3 in test and although it has the same version of postfix, 2.4.3.4z, it's spool directory is fully populated with the normal compliment of directories owned by postfix. Is this new for 5.0.4?