Set custom "system" email address in panel.ini for server notifications, e.g. password reset mails
Some notifications such as Additional Administrators activation email, password reset requests, etc. are sent from the "System" with the address: no-reply@<full-server-hostname>. To change this "System" sender email address, we can set the required full hostname under Tools & Settings > Server Settings > Full hostname.
It would be useful in the future to be able to change the address used for Activation and Password Reset emails in the panel.ini file.
Plesk Tech Support
shared this idea
Since Plesk 18.0.57, published November 21st, 2023, password reset and activation emails are no longer sent from the default email address if a custom one is specified in the senderAddress setting of the panel.ini file. (PPPM-14183).
Please let us know in your comments if this is not the expected solution for this feature request.
-- PD
-
Plesk Tech Support
commented
In Plesk 18.0.45, the functionality of changing the sender address email in Plesk email notifications was implemented ("senderAddress" option in "[notification]" section of panel.ini file).
However, not all emails sent by Plesk respect this option - password reset emails, additional Plesk administrators activation emails, etc - they are sent from emails like noreply@<server_hostname>.
This may lead to such emails being rejected on the receiver side due to invalid SPF because the server hostname is quite often is like plesk.example.com which obviously doesn't have SPF.
So it'd be great if all emails sent by Plesk are unified and respect the mentioned panel.ini option and it's possible to change sender address for all of them. -
mcortez
commented
This is really needed for those of us using external SMTP mail servers, because we can't always configure the external server to accept <addresses>@<hostname-of-plesk-server>
-
Anonymous
commented
Add the possibility to change the FROM address from the password-reset emails
Some of the reasons are:
- To be able to receive bounce messages if the customer mail address cannot be reached.
- To set-up valid SPF records to prevent these mails from ending up in a spam filter.
- To prevent these mails from being blocked by spam filters because the "from" address check fails.