Bitpalast GmbH

My feedback

  1. 899 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  177 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast GmbH supported this idea  · 
  2. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    An 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  · 
  3. 48 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Feature Suggestions » Backup / Restore  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast 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.

  4. 89 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Bitpalast GmbH commented  · 

    I can only add that we are seeing a strongly increasing number of attacks coming from IPv6 sources, but we cannot update all our hosts to the latest Plesk, because the risk of too many bugs in early adopter and even early stable version is too high.

    Other providers who are serving many customers, too, will not easily do the update, so we are looking at around a year more waiting time from now at least until an update to 17.9 can be considered. Too long.

    Bitpalast GmbH supported this idea  · 
  5. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast GmbH supported this idea  · 
    An error occurred while saving the comment
    Bitpalast GmbH commented  · 

    I don't think this ought to be a feature request that requires voting. It is a severe security issue that needs to be fixed.

  6. 23 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast GmbH supported this idea  · 
  7. 8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  4 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast 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.

  8. 87 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Bitpalast GmbH supported this idea  · 

Feedback and Knowledge Base