Anonymous
My feedback
10 results found
-
1,298 votes
An error occurred while saving the comment An error occurred while saving the comment Anonymous
commented
Looking at the fact that Plesk Email Security Pro now includes ClamAV, I assume from a change request point of view, Plesk will see this as solved.
However, it is VERY DISAPPOINTING to see again that Plesk failed to follow the community demand having this as an unpaid extension.
Also, from a security standpoint, I think it is socially not acceptable that they require us to pay for it, especially given the fact that they mainly employ open software for this feature.
In addition, the extension has the drawback that greylisting needs to be disabled, which I think is a bad idea.Nevertheless, following https://www.lloyd-day.me/migrate-plesk-to-clamav/, there is quite a simple solution if you want to integrate ClamAV yourself.
By not uninstalling DrWeb (free protection of 10 mailboxes), you can even run both in parallel by adapting the information in step 4 (settings for /etc/postfix/main.cf):With psa_remote and ClamAV, I use:
smtpd_milters = {inet:127.0.0.1:12768, default_action=accept}, { inet:127.0.0.1:3381, protocol=6, default_action=tempfail }
non_smtpd_milters = , inet:127.0.0.1:12768This setting also helps to avoid issues when DrWeb fails to scan e-mails (happens quite frequently)...
Anonymous
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.
—
IGAnonymous
supported this idea
·
-
93 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
Anonymous
supported this idea
·
-
29 votesAnonymous
supported this idea
·
-
10 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
·
-
298 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
I agree with H. Dolderer, this is a must for current systems - also given that in certain combinations of using SSL for Plesk and the corresponding website, it is otherwise impossible to access the admin interface right now!
Also, looking at the implementation effort, this should almost be zero since the same has been done for the webmail system already. Thus, it is disappointing to read a statement like "we might eventually implement this at some point (> 10 years...?) in the future"...An error occurred while saving the comment Anonymous
commented
You're right, it is currently not supported: https://support.plesk.com/hc/en-us/articles/115002810634
However, given the comment from darkdragen, I agree that the service should be secured the same way as it has been done already for the webmail subdomains.
Anonymous
supported this idea
·
-
708 votes
An error occurred while saving the comment Anonymous
commented
Annoying that it is a premium extension only!
Anonymous
supported this idea
·
-
417 votesAnonymous
supported this idea
·
-
544 votesAnonymous
supported this idea
·
-
232 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
·
As mentioned before, clamav can be integrated (at least on Ubuntu) with a few simple steps. Thus, I really wonder what Plesk considers to be the expensive part of integrating this (except for losing people paying for the DrWeb extension).