Marian Feiler
My feedback
65 results found
-
22 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.
—
IGMarian Feiler
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…
Marian Feiler
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
Marian Feiler
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.
—
IGMarian Feiler
supported this idea
·
-
64 votes
Look at this solution for Postfix – http://webmasters.stackexchange.com/questions/57746/plesk-email-journaling
But anyway, thank you for your input! We will consider this suggestion in upcoming releases if it will be popular.
Everyone, please continue voting for this feature and add your comments if you consider it important.
—
IGMarian Feiler
supported this idea
·
-
77 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
Marian Feiler
supported this idea
·
-
164 votesMarian Feiler
supported this idea
·
-
427 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.
—
IGMarian Feiler
supported this idea
·
-
698 votesMarian Feiler
supported this idea
·
-
89 votes
"1. Ability to control [DKIM] key length 1024Bit or 2048Bit (server wide)"
is available since Plesk 18.0.55, published August 29th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18055
"4. Ability to change the [DKIM] selector"
is available since Plesk 18.0.56, published Ocotber 10th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18056
Stay in the loop for more to come.
-- PD
Marian Feiler
supported this idea
·
-
23 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.
—
IGMarian Feiler
supported this idea
·
-
448 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Marian Feiler
supported this idea
·
-
21 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.—
IGMarian Feiler
supported this idea
·
-
24 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.
—
IGMarian Feiler
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.
Marian Feiler
supported this idea
·
-
27 votesMarian Feiler
supported this idea
·
-
46 votes
These suggestions look quite reasonable. We encourage other WPT users to join and let us know what other security improvements you’d like us to implement in WPT.
—AK
Marian Feiler
supported this idea
·
-
25 votes
In the initital feature request it was not clear that the focus was on a regex driven, variable redirect that depends on source URLs and should be able to provide a mapping between source and target. It is also requested that these redirects shall be done on the front-end web server level, not as an Apache .htaccess solution.
We have re-opened the request as per user comment it was clarified thoroughly. 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.
-- PD
Marian Feiler
supported this idea
·
-
27 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.
—ETMarian Feiler
supported this idea
·
-
35 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
Upd: We’re happy to announce that DMARC support is now available in Plesk Onyx. You can enable DMARC to check incoming mail on a Linux-based server (using any mail server supported by Plesk) or on a Windows-based server (using SmarterMail only). For more information about DMARC, see https://docs.plesk.com/release-notes/onyx/whats-new/#s17
Notice, that the request remained opened and please continue voting for this feature if you consider it important.
Marian Feiler
supported this idea
·
