Bitpalast GmbH
My feedback
16 results found
-
2 votes
Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
In the meantime, you may consider scheduling Plesk's major updates for days/times when backup jobs are not expected to run.
-- SH
Bitpalast GmbH
shared this idea
·
-
1 vote
Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
Bitpalast GmbH
shared this idea
·
-
2 votesBitpalast GmbH
supported this idea
·
-
25 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. Thanks in advance!
— rk
An error occurred while saving the comment Bitpalast GmbH
supported this idea
·
-
3 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.
—
IGBitpalast GmbH
supported this idea
·
-
18 votesBitpalast GmbH
supported this idea
·
-
3 votes
Thank you for your idea! 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
An error occurred while saving the comment Bitpalast GmbH
commented
I've needed a feature to add domains in bulk for years. Normally customers do not only buy a single domain, but three or more. With the current feature, I must iterate through all domains separately. It will be much better to paste a list of domains into text field and let the user interface iterate through them to create domains.
It is possible to delete domains in bulk, so why not also make it possible to create them in bulk.
Bitpalast GmbH
supported this idea
·
-
42 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.
—
IGBitpalast GmbH
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.Bitpalast GmbH
supported this idea
·
An error occurred while saving the comment Bitpalast GmbH
commented
We've been exporting the Roundcube database manually into a subscription account daily so that these are being backed up along with the daily full server backup that Plesk does.
-
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.
—
IGAn error occurred while saving the comment Bitpalast GmbH
commented
Recently we went through significant testing efforts on several servers with a very high number of domains and email users that can be considered representative. Among all ranging from Thunderbird, Outlook, Android Mail, Apple Mail, iPhone Mail we found that the only viable solution to the "failed auth" issue caused by DIGEST-MD5 password mechanism is to remove the "digest-md5" entry from Dovecot as mentioned in the FAQs.
Please vote for this feature! It's a truly important feature to implement, because this will save hundreds of thousands of admins a lot of trouble with users that use mail apps where the auth mechanism cannot be freely picked.
Bitpalast GmbH
supported this idea
·
-
1,295 votesBitpalast GmbH
supported this idea
·
-
13 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 Bitpalast GmbH
commented
I have tested this with Plesk Obsidian. Actually, when you place a "permit_dnswl_client" command into the /etc/postfix/main.cf file similar to this:
smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, permit_dnswl_client list.dnswl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client xbl.someblacklist.org, reject_rbl_client someotherblacklist.org
you can still update the mail server configuration through Plesk GUI and the configuration remains in place. This is true even when you edit the "DNS zones for DNSBL service" field in Plesk. So as a workaround for the time being I suggest to edit /etc/postfix/main.cf once manually.
Bitpalast GmbH
supported this idea
·
-
144 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.
—
IGBitpalast GmbH
supported this idea
·
An error occurred while saving the comment Bitpalast GmbH
commented
This can be a very useful feature, because some users end to overdraw their webspace quota sharply, resulting in many additional GB to be stored in backups, too. In such cases it would be very good to be able to exclude such user accounts from the backup until the users reduce their web space usage to what's been agreed on in their webspace contract.
-
29 votesBitpalast GmbH
supported this idea
·
-
2 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.
—
IGBitpalast GmbH
supported this idea
·
An error occurred while saving the comment Bitpalast GmbH
commented
It is currently possible to install the product on unsupported databases, e.g. MariaDB 10.2. Users don't notice this until they need a function that does not work correctly with the wrong database version.
It should not be possible to install Plesk on a system that is using a database server that is unsupported by the Plesk version.
-
12 votesBitpalast GmbH
supported this idea
·
An error occurred while saving the comment Bitpalast GmbH
commented
I would like to add this from our point of view: We have different hosting plans. In the cheap hosting plan, users ought not to be able to use SSL at all. However, users must always be able to decide the type of hosting they want, e.g if a domain is redirect or a web space. The problem is that when hosting settings are allowed for the user, SSL is allowed, too. To enforce disabling SSL, hosting settings must be disabled for the user. The later cannot be done, because users must be able to configure that themselves.
So we end up with not being able to limit SSL usage by the user, losing and important upselling argument in sales.
Hi guys, please check the comments in https://support.plesk.com/hc/en-us/articles/13499859483799-Mail-sent-to-Postfix-default-accounts-localhost-localdomain-is-routed-to-Plesk-Administrator-s-email . I'm seeing the same on our servers recently for which I filed ticket 95352337. Support was very helpful as always, yet I think this could deserve attention as a feature, because now that spammers started targeting Plesk users via these aliases, they won't stop. It could become a global issue for Plesk systems.