• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Removal of -bs option from plesk-sendmail-wrapper

We have upgraded to 18.0.45.1 and the error about sendmail has disappeared, however it is now replaced by another error:

554 5.7.1 <[email protected]>: Relay access denied\".\" at /var/www/vhosts/domainname.co.uk/httpdocs/vendor/symfony/mailer/Transport/Smtp/SmtpTransport.php line 306
 
In maillog I get this:

Jul 20 16:39:56 postfix/smtpd[27983]: warning: error opening chain file: /etc/postfix/postfix.pem: Permission denied
Jul 20 16:39:56 postfix/smtpd[27983]: connect from localhost[127.0.0.1]
Jul 20 16:39:56 postfix/smtpd[27983]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 554 5.7.1 <informacion@******.com>: Relay accMTP helo=<******..com>
Jul 20 16:39:56 postfix/smtpd[27983]: disconnect from localhost[127.0.0.1] helo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5
Jul 20 16:39:56 psa-pc-remote[27335]: Message aborted.
Jul 20 16:39:56 psa-pc-remote[27335]: Message aborted.
 
Same issue here , even upgrading to 18.0.45.1 , log shows :

Jul 21 08:00:10 api postfix/smtpd[3849]: warning: error opening chain file: /etc/postfix/postfix.pem: Permission denied
Jul 21 08:00:10 api postfix/smtpd[3849]: connect from localhost[127.0.0.1]
Jul 21 08:00:10 api postfix/smtpd[3849]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=SMTP helo=<[127.0.0.1]>
Jul 21 08:00:10 api postfix/smtpd[3849]: disconnect from localhost[127.0.0.1] helo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5
Jul 21 08:00:10 api psa-pc-remote[20437]: Message aborted.
Jul 21 08:00:10 api psa-pc-remote[20437]: Message aborted.
 
I think i solved it:

On twitter they told me:

Make sure that 127.0.0.0/24 is added to the Tools & Settings > Mail Server Settings > White List

I put it but it gave another error.

I have restarted the service and OK.

service postfix restart && service pc-remote restart



BUT THIS SHOULD HAVE BEEN SOLVED BY PLESK IN THE UPDATE!
 
I think i solved it:

On twitter they told me:

Make sure that 127.0.0.0/24 is added to the Tools & Settings > Mail Server Settings > White List

I put it but it gave another error.

I have restarted the service and OK.

service postfix restart && service pc-remote restart



BUT THIS SHOULD HAVE BEEN SOLVED BY PLESK IN THE UPDATE!

It looks like someone gave you some bad advice. 127.0.0.0/8 isn't added to the whitelist as of Plesk 12 to make sure outbound spam protection is functioning correctly:

 
I think i solved it:

On twitter they told me:

Make sure that 127.0.0.0/24 is added to the Tools & Settings > Mail Server Settings > White List

I put it but it gave another error.

I have restarted the service and OK.

service postfix restart && service pc-remote restart



BUT THIS SHOULD HAVE BEEN SOLVED BY PLESK IN THE UPDATE!
Hat bei mir mit dieser Anleitung funktioniert.
Danke.
 
Ok, now that 18.0.45 update 1 is installed, we also get the following error:

554 5.7.1 <[email protected]>: Relay access denied

Adding 127.0.0.0/8 to the whitelist solves this indeed, but IMHO this should have been handled by the update.
 
Hi,
urgent please :

with new version plesk-mail-pc-driver 18.0-v.ubuntu.20.04+p18.0.45.1+t220720.0425 amd64 :

Now i hav a silent end of PHP script :

tail /var/log/mail.err

Jul 21 12:17:48 webXY psa-pc-remote[3944809]: Message aborted.

tail /var/log/maillog

Jul 21 12:17:48 web11 postfix/smtpd[3974182]: warning: error opening chain file: /etc/postfix/postfix.pem: Permission denied
Jul 21 12:17:48 web11 postfix/smtpd[3974182]: connect from localhost[127.0.0.1]
Jul 21 12:17:48 web11 postfix/smtpd[3974182]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=SMTP helo=<localhost>

Thanks
 
Please don't let it happen again.
This causes us a lot of problems and waste of time.
Yes, I understand your concern. It wasn't well done and tested on our part. We do apologize for that.
 
Hello, thank you for the fix.
I have a question, I had blocked my updates before version 18.0.45 was deployed on my server.
I'm still on 18.0.44 update #3, can I upgrade directly to version 18.0.46 without worries?
Thanking you.
 
Back
Top