Milos
My feedback
3 results found
-
24 votes
As https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/16956373-set-a-senders-email-address-for-plesk-notification was resolved and the sender address of notifications is now customizable we are wondering whether the issue described in this feature request cannot also be considered solved. The issue here was described as sender and recipient being the same address so that notifications are evaluated as "spam" at the recipient's mailbox. However, now that the sender address can be customized, this could easily be circumvented.
Further, the recipient address of notifications can be freely set in the notifications page.
Please comment if and why this feature request is still actual.
-- PD
Milos
supported this idea
·
-
386 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
An error occurred while saving the comment -
153 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGMilos
supported this idea
·
I just can't belive Plesk have such issues with SSL certificates on panels.
Problem continues from year to year, and you still did not fixed it
Some kind of a workarond you give us here is still not enough.
https://support.plesk.com/hc/en-us/articles/115001421414-How-to-configure-a-redirect-from-the-domain-name-IP-address-to-the-server-hostname-on-port-8443-
https://talk.plesk.com/threads/not-properly-redirect-https-domain-tld-8443-to-https-server-hostname-tld-8443-security-errors.353569/
We need either to redirect user before certificate validation by browser, or you to make SSL certificates works for customerdomain.com:8443.
People should consider about paying PLESK license for product that does not meet industry standards.