Hi all, I just updated my ISPConfig instance to 3.2.7p1 and somewhy my Postfix just broke so I'm unable to send out mails due to this "permission denied" error message. Code: Feb 12 14:22:00 cloud postfix/postfix-script[2965]: warning: symlink leaves directory: /etc/postfix/./smtpd.cert Feb 12 14:22:00 cloud postfix/postfix-script[2968]: warning: symlink leaves directory: /etc/postfix/./smtpd.key Feb 12 14:22:00 cloud postfix/postfix-script[2971]: warning: symlink leaves directory: /etc/postfix/./smtpd.cert-20210930222706.bak Feb 12 14:22:00 cloud postfix/postfix-script[2974]: warning: symlink leaves directory: /etc/postfix/./smtpd.cert-210930222938.bak Feb 12 14:22:00 cloud postfix/postfix-script[2977]: warning: symlink leaves directory: /etc/postfix/./smtpd.key-20210930222706.bak Feb 12 14:22:00 cloud postfix/postfix-script[2980]: warning: symlink leaves directory: /etc/postfix/./smtpd.key-210930222938.bak Feb 12 14:22:00 cloud postfix/postfix-script[3019]: starting the Postfix mail system Feb 12 14:22:00 cloud postfix/master[3021]: daemon started -- version 3.3.0, configuration /etc/postfix Feb 12 14:22:03 cloud postfix/smtpd[3085]: connect from unknown[x.x.x.x] Feb 12 14:22:06 cloud postfix/smtpd[3090]: warning: connect #1 to subsystem /var/spool/postfix/private/proxymap: Permission denied Feb 12 14:22:16 cloud postfix/smtpd[3085]: warning: unknown[x.x.x.x]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 12 14:22:16 cloud postfix/smtpd[3090]: warning: connect #2 to subsystem /var/spool/postfix/private/proxymap: Permission denied Feb 12 14:22:26 cloud postfix/smtpd[3090]: warning: connect #3 to subsystem /var/spool/postfix/private/proxymap: Permission denied What i've tried: - sending email with Laravel + "mail" configuration gives the above error - sending email with native PHP mail functionality sends out the email - sending through bash it sends out the email - before update it worked - not sure what has been changed in configs Any advice is appreciated. Thanks!
On my system Code: ls -lh /var/spool/postfix/private/proxymap srw-rw-rw- 1 postfix postfix 0 tammi 30 22:32 /var/spool/postfix/private/proxymap What are owners and permissions on your system? Did you allow ispconfig upgrade to do reconfigure services? Have you rebooted after the upgrade? Have you modified your system in some way?
Hi Taleman and thanks for your reply. I allowed to reconfigure services, rebooted the system (it's a VPS with Ubuntu 18.04). The only change did was an "apt-get upgrade" without any warning/error (afterwards did the ISPConfig upgrade). This is the output of the command: Code: ls -lh /var/spool/postfix/private/prox ymap srw-rw-rw- 1 postfix postfix 0 Feb 12 14:22 /var/spool/postfix/private/proxymap
Another finding: setting "mail" as mail driver for Laravel and sending it through "php artisan tinker" works perfectly. Now I'm wondering what could be the difference between triggering via CLI and through Apache. Seems to be pretty similar to this (https://www.howtoforge.com/community/threads/solved-proxymap-permission-denied.86089/), but I can not think if it's a framework bug or just a PHP / postfix configuration.
