Bob B
My feedback
46 results found
-
26 votes
Thank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
Bob B
supported this idea
·
An error occurred while saving the comment -
411 votes
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
The original request contains a manual solution, so, we consider to automate it. Please, add a comment if your case will not be solved with that solution.
Thanks in advance!
— rk
Bob B
supported this idea
·
-
72 votesBob B
supported this idea
·
-
9 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGBob B
supported this idea
·
-
448 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Bob B
supported this idea
·
-
5 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.
—
IGBob B
supported this idea
·
-
115 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.
—
IGBob B
supported this idea
·
-
5 votesBob B
supported this idea
·
-
53 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.
The previous status update was done by mistake.
— AY
Bob B
supported this idea
·
-
39 votesBob B
supported this idea
·
-
62 votes
Good news! Despite the low number of votes that this request got, from some additional reports Plesk understands that this is a critical function for some users. We do not have an ETA yet, but it will be worked on in the scope of upcoming feature enhancements.
Bob B
supported this idea
·
-
158 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.
—
IGBob B
supported this idea
·
-
28 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
An error occurred while saving the comment Bob B
commented
SPF fails for all of the notifications because Plesk is spoofing the "From:" email address. The From: address needs to be specified separately from the To: address, so the From: may be set to something that would pass SPF checks (e.g. pleskadmin@hostname).
Bob B
supported this idea
·
-
20 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGBob B
supported this idea
·
-
14 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.
—
IGBob B
supported this idea
·
-
7 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGBob B
supported this idea
·
-
49 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.—
IGAn error occurred while saving the comment Bob B
commented
This would be a time saving feature. However, until it's available, this "IP Range to CIDR" calculator is useful...
Bob B
supported this idea
·
-
5 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.
—
IGBob B
supported this idea
·
-
71 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.
—
IGBob B
supported this idea
·
-
84 votes
We are working already to add CSF support. It will be available in the one of the nearest releases.
SE
Bob B
supported this idea
·
.png){kind=link}
Adding the hostname of the server as a "Subscription" and setting that Subscription to enable DKIM allows Plesk notification messages to be signed by DKIM. However, that feels more like a work-around than the best method to accomplish this. I'd like to see a better method implemented by Plesk.