Anonymous
My feedback
12 results found
-
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
Anonymous
supported this idea
·
-
58 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.— rk
An error occurred while saving the comment Anonymous
supported this idea
·
-
284 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.— rk
An error occurred while saving the comment Anonymous
commented
+1. It should also be possible to run Mailman under a subdomain other than lists.example.com
-
128 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.
—
IGAnonymous
supported this idea
·
-
228 votes
Thank you for your input. We will consider this functionality in upcoming releases. Note that Plesk supports multiple mail servers and if we are going to add this feature, it’s possible that it won’t be available for all supported mail servers at once
Anonymous
supported this idea
·
-
303 votes
Please note, Plesk has supported the version of Mailman provided by OS vendor by default.
The Mailman 3 is shipped by default on Ubuntu 18 and Debian 10.
Please keep voting if this request is still actual for you.
—
AAAn error occurred while saving the comment Anonymous
commented
+1
Anonymous
supported this idea
·
-
208 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 Anonymous
commented
+1
Anonymous
supported this idea
·
-
359 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.— SU
Anonymous
supported this idea
·
-
698 votesAnonymous
supported this idea
·
-
412 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
Anonymous
supported this idea
·
-
1,271 votesAnonymous
supported this idea
·
-
629 votes
Repeatedly we're seeing questions on when http/3 will be implemented. http/3 is available in the experimental branch of Nginx, called "main line". This is not a branch that is "stable". Plesk only offers stable software versions for the utmost reliability you can get as reliability is much more important than speed. A fast website is of no use if its webserver crashes or the protocol doesn't work as expected in all cases. Plesk does not offer experimental features. The stable version of Nginx that supports http/3 is expected to become available in April 2024. This is when it makes sense for Plesk to also offer http/3.
From articles that foster the hype about http/3, it sounds as if it can increase a website's speed incredibly much. On average, on real website tests by several reknown sources, the acceleration has been seen at around 0.2 to 0.3 s/page, typically around 12…
Anonymous
supported this idea
·
+1