From the engine/setup/set-engine-permissions.sh script:
Code:
62 recursive_set_permissions "$LOG_DIR/ispcp-arpl-msgr" \
63 $MTA_MAILBOX_UID_NAME $MTA_MAILBOX_GID_NAME 0750 0640
Hence, if you get the following:
Quote:
Code:
drwxr-x--- 2 1000 mail 4096 12. Jul 15:42 ispcp-arpl-msgr
It means that your MTA_MAILBOX_UID_NAME (that should be "vmail") and MTA_MAILBOX_GID_NAME (that should be "mail") variables are incorrectly set in your ispcp config file (/etc/ispcp/ispcp.conf). Can you confirm it?
Otherwise, simply running the said set-engine-permissions script should fix this issue.
@joxi,nuxwin: Since both "engine/ispcp-db-keys.pl" and "engine/messenger/ispcp-db-keys.pl" have the exact same content, we could change the update instructions from:
Quote:Prior 1.0.3:
Code:
# cp -v /var/www/ispcp/engine/messager/ispcp-db-keys.pl /tmp/ispcp/var/www/ispcp/engine/messenger/
After 1.0.3:
Code:
# cp -v /var/www/ispcp/engine/messenger/ispcp-db-keys.pl /tmp/ispcp/var/www/ispcp/engine/messenger/
to a much simpler:
Quote:(All versions
Code:
# cp -v /var/www/ispcp/engine/ispcp-db-keys.pl /tmp/ispcp/var/www/ispcp/engine/messenger/
It's much simpler, isn't it? Any arguments against doing so?