Username:
TITLE
Plesk tries to get server hostname from /etc/mailname for cronjob notifications on RHEL based systems
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 18.0.74#1
AlmaLinux 8 and 9 (not tested on AL10)
PROBLEM DESCRIPTION
On RHEL based systems Plesk tries to get server hostname from the
As a results cronjob notifications are send without a proper hostname in their sender address. Causing authentication issues (like SPF) on the receiving end to either fail or mark the notification as spam.
STEPS TO REPRODUCE
1) On a RHEL based server setup a cronjob in Plesk (via T&S > Scheduled Tasks) with Root as the System user, set the notify option to "Every time".
2) Wait until the cron job has run
3) Look at the mail or system log and notice the error posted above
ACTUAL RESULT
Plesk tries to use the
EXPECTED RESULT
Plesk uses another method that's RHEL compatible to get the server hostname for the sender address of the cronjob notification.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
Plesk tries to get server hostname from /etc/mailname for cronjob notifications on RHEL based systems
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 18.0.74#1
AlmaLinux 8 and 9 (not tested on AL10)
PROBLEM DESCRIPTION
On RHEL based systems Plesk tries to get server hostname from the
/etc/mailname file for use of the sender address of cronjob notifications. However, by default RHEL based system do not use a /etc/mailname file to store the server hosts name. Resulting in the following errors being logged:
Code:
add-from [120344] S120342: Could not construct 'From:' address, do nothing
add-from [120344] S120342: Cannot get hostname FQDN from /etc/mailname
plesk-sendmail [120343] S120342: add-from: stderr: System error 2: No such file or directory
plesk-sendmail [120343] S120342: add-from: stderr: Unable to open file /etc/mailname: No such file or directory
As a results cronjob notifications are send without a proper hostname in their sender address. Causing authentication issues (like SPF) on the receiving end to either fail or mark the notification as spam.
STEPS TO REPRODUCE
1) On a RHEL based server setup a cronjob in Plesk (via T&S > Scheduled Tasks) with Root as the System user, set the notify option to "Every time".
2) Wait until the cron job has run
3) Look at the mail or system log and notice the error posted above
ACTUAL RESULT
Plesk tries to use the
/etc/mailname file to get the server hostname for the sender address of the cronjob notification.EXPECTED RESULT
Plesk uses another method that's RHEL compatible to get the server hostname for the sender address of the cronjob notification.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
Last edited: