Me
My feedback
-
67 votesopen discussion · 13 comments · Feature Suggestions » Plesk (general) · Flag idea as inappropriate… · Admin →Me
supported this idea
·
-
99 votesMe
supported this idea
·
-
80 votes
We are building an extension to help you use Composer straight from the Plesk interface. Help us make a better solution for you by taking a survey on how you use Composer.
The survey will take 4-6 minutes:
https://pt-research.typeform.com/to/LyPiPGBeta version of the Extension is available for Plesk Obsidian: https://docs.plesk.com/release-notes/obsidian/whats-new/
Me
supported this idea
·
-
147 votesMe
supported this idea
·
-
95 votes
Thank you for your input. We will see if it’s possible to add a nice-looking and straightforward autoresponder to supported webmail clients. Note that Plesk already does provide this functionality.
Me
supported this idea
·
-
518 votes
Since Plesk Obsidian RC4, users’ Microsoft Outlook and Thunderbird mail clients can now be automatically configured based on entered emails.
https://docs.plesk.com/release-notes/obsidian/change-log/#contents-18-rc40
—
AAMe
supported this idea
·
-
205 votes
Thank you for your input. We will take a look into this functionality. We’d also suggest trying out our Plesk Automation product.
Me
supported this idea
·
-
196 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.
— IB
Me
supported this idea
·
-
281 votes
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
Me
supported this idea
·
-
337 votesopen discussion · 13 comments · Feature Suggestions » Panel/Mail · Flag idea as inappropriate… · Admin →Me
supported this idea
·
-
328 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.
—
IGMe
supported this idea
·
-
366 votesopen discussion ·
AdminSergey L
(Director of Program Management, Plesk International GmbH)
responded
We have serious doubts this function can really increase server security:
1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.
As for concerns that default password requirement is set in “weak”, that fail2ban module is not…
Me
supported this idea
·
-
135 votesMe
supported this idea
·
-
779 votesMe
supported this idea
·
Hi there,
autodiscover is helpful for Thunderbird, Outlook and Apple mail. There is a tool available which helps to achive these features: https://automx.org/en/
Using this tool, you can autoconfigure mail clients for plesk. If your plesk server (hosting the e-mail service) is installed at [anysubdomain.]mydomain.com, use the following steps to use the tool:
1) Create the subdomains autodiscover.mydomain.com and autoconfig.mydomain.com and make sure that automx is working for these two subdomains (according to the instructions of automx, e.g., install the required modules etc.). This also includes the following additional instructions for Apache (both HTTP and HTTPS as well as for autodiscover.mydomain.com and autoconfig.mydomain.com (the last two lines are optional):
ServerAlias autoconfig.*
<IfModule mod_wsgi.c>
WSGIScriptAliasMatch \
(?i)^/.+/(autodiscover|config-v1.1).xml \
/usr/local/lib/automx/automx_wsgi.py
<Directory "/usr/local/lib/automx">
Order allow,deny
Allow from all
</Directory>
</IfModule>
RewriteEngine on
RewriteRule ^$ https://www.mydomain.com/ [R=301,L]
2) Make sure to install & activate SSL certificates for both subdomains.
3) Make sure that the DNS server resolves both subdomains.
4) Edit the default DNS template and add CNAME entries from autoconfig.<domain> to autoconfig.mydomain.com and from autodiscover.<domain> to autodiscover.domain.com.
5) Apply the DNS template to all existing domains in Plesk.
6) Set up an approriate automx.conf file, e.g.,:
[automx]
provider = <your name>
domains = *
[DEFAULT]
account_type = email
account_name = %s (via Your Providername)
account_name_short = %s
display_name = %s
[global]
backend = static
action = settings
smtp = yes
smtp_server = <your-smtp-server-name>
smtp_port = 587
smtp_encryption = starttls
smtp_auth = encrypted
smtp_auth_identity = %s
imap = yes
imap_server = <your-imap-server-name>
imap_port = 993
imap_encryption = auto
imap_auth = encrypted
imap_auth_identity = %s
pop = yes
pop_server = <your-pop-server-name>
pop_port = 995
pop_encryption = auto
pop_auth = encrypted
pop_auth_identity = %s
Now requests to autoconfig.customerdomain.com should be redirected to autoconfig.mydomain.com and automx should server the required settings to the clients.
As a conclusion: with the work of a few hours, this could be enabled for all Plesk customers!