

Intergrating pentesting Applications in OWSAP ZAP.

Once the permissions on the file and folders are fixed, start postfix by running this command as the zimbra user: $touch opt/zimbra/data/postfix/data/master.lock Make sure that the postfix user can write to the …postfix/data/ folder. If the permissions are not correct, update them.

#chown postfix /opt/zimbra/data/postfix/data/master.lockĬheck the permissions on the folder by running this command:ĭrwxr-xr-x 2 postfix postdrop 4096 23:30 /opt/zimbra/data/postfix/data/Ĭheck the permissions on the parent folder by running this command:ĭrwxr-xr-x 4 postfix zimbra 4096 19:12 /opt/zimbra/data/postfix/ If the file is not owned by the postfix user, change the owner by running this command as root: Note: The first username, colored here in red, is the owner of the file. rw- 1 postfix postfix 33 13:52 /opt/zimbra/data/postfix/data/master.lock $ls -l /opt/zimbra/data/postfix/data/master.lock If postfix continues to fail to start, check the file by running this command: Try starting postfix again by running this command as the zimbra user: Note: This option can take a significant amount of time to run, in large deployments. #/opt/zimbra/libexec/zmfixperms -extended If postfix fails to start, and returns the same error: Try starting postfix again, by running this command as the zimbra user: The /opt/zimbra/data/postfix/data/master.lock file should be owned by the user postfix. This failure is caused by incorrect permissions on this file /opt/zimbra/data/postfix/data/master.lock I post this error along with solution for that.įatal: open lock file /opt/zimbra/data/postfix/data/master.lock: cannot open file: permission denied In one my client mail server Postfix is stopped after restarting.
