841 results found

1. General email filters

   Please add functionality to configure general email filters in Plesk.
   The same functionality is implemented in cPanel:
   https://documentation.cpanel.net/display/CKB/How+to+Configure+Mail+Filters

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Mail  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Possibility to downgrade WorpdPress version via WP-toolkit

   I'd like to suggest a feature implementation to downgrade WordPress core version using wp-toolkit , as at the moment just update is possible.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Extensions  ·  Delete…  ·  Admin →
   declined  ·  IgorG responded

   Upd: Sorry, we are closing the request as no information was provided for over a month.

   —
   
IG

3. More speed: Asynchronous User Interface

   In practice I find working on domains, aliases and email addresses, in Plesk 12.5 tedious and slow. Adding domains, quickly moving aliases to another domain, or changing email addresses, it just all takes a lot of time. Most of the time I'm simply waiting for the UI to respond. What a waste of time.

   This is not because of a slow server or connection. The reason seems to be that Plesk does all the work on the server before it refreshes the UI and accepts new input.

   I would prefer it if user input would be seperated from the actual changes made to the server. Just allow me to quickly do things, without having to wait every time for everything to complete. That would be great. I mean, that's what Plesk is for, isn't it?

   If you want to do this right, it should be implemented for the whole interface of plesk. Preferably the UI should reflect any changes immeadiately, so it should have a complete abstract model of the server. Changes could then be buffered in a command queue, and executed in the background.

   This idea is not new: http://old.alexmaccaw.com//posts/async_ui

   In practice I find working on domains, aliases and email addresses, in Plesk 12.5 tedious and slow. Adding domains, quickly moving aliases to another domain, or changing email addresses, it just all takes a lot of time. Most of the time I'm simply waiting for the UI to respond. What a waste of time.

   This is not because of a slow server or connection. The reason seems to be that Plesk does all the work on the server before it refreshes the UI and accepts new input.

   I would prefer it if user input would be seperated from the actual… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Upd: Sorry, we are closing the request as no information were provided for over a month.
   —
   IG

4. "keep secure" should be ON by default for any new Service Plan.

   We and many other companies sell "Reseller accounts", each reseller has its own service plans. We can't control how they create their service plans and if they enable "keep secured" in their plan.

   So in that case, there should be a global keep-secured solution that has nothing to do with resellers' plans.

   An admin should have the option to enable "keep secured" globally so that any newly created domain will be secured once it's pointed to the server DNS. Something similar is working flawlessly in CPANEL. CPANEL users basically do not need to actively install an SSL by Let's Encrypt. It is installed automatically.

   By developing this feature, you will make the overall experience better. Hosting companies who are migrating websites constantly don't need to watch when the DNS will be propagated, it will however be done by the already existing cron job keep-secured.php.

   We and many other companies sell "Reseller accounts", each reseller has its own service plans. We can't control how they create their service plans and if they enable "keep secured" in their plan.

   So in that case, there should be a global keep-secured solution that has nothing to do with resellers' plans.

   An admin should have the option to enable "keep secured" globally so that any newly created domain will be secured once it's pointed to the server DNS. Something similar is working flawlessly in CPANEL. CPANEL users basically do not need to actively install an SSL by Let's Encrypt.… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Business Logic  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   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

5. Add global option to control default value of "Search Indexing Enabled" and "Debugging" for newly created site

   We've WordPress development company and use Plesk for managing lots of staging servers for projects under development.
   All domains are created automatically via API as part of the project's start process, and, of course, all instances that are under development should not be indexed during the development stage (as it will affect the page index of the site in production).
   By default, "Search Indexing" option is enabled, and this is quite inconvenient and error prone for us (as it requires manual setup of the created instance).
   Adding global server-wide configuration option for WP Toolkit that will control such default behavior (for compatibility reasons, the default value will be true, of course) - will let us ensure that no domain which was created for the development will be indexed.

   We've WordPress development company and use Plesk for managing lots of staging servers for projects under development.
   All domains are created automatically via API as part of the project's start process, and, of course, all instances that are under development should not be indexed during the development stage (as it will affect the page index of the site in production).
   By default, "Search Indexing" option is enabled, and this is quite inconvenient and error prone for us (as it requires manual setup of the created instance).
   Adding global server-wide configuration option for WP Toolkit that will… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   e 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

6. Cross-platform migrations of the e-mails

   Add the ability to perform cross-platform migrations of the emails even for external 3rd party mail services.
   For now, it is only possible to use "Mail Importing" feature of the Site Import extension but it only migrates one mailbox at a time.
   The alternative way is to use 3rd party IMAP migration tools to copy email content, or copy it manually but this operation was not tested by Plesk.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Migrations  ·  Delete…  ·  Admin →
   completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Please use Plesk E-Mail Migration Module – https://www.plesk.com/extensions/email-migration/
   —
   IG

7. security headers

   I have to say I was delighted to see that Plesk.com (unlike so many sites) has all its security headers* in order, but it would be really good if this was a thing that could be operated easily from within Plesk given the massive importance of them. It would also tidy up A LOT of the stuff to do with many of the things that people are asking on here with things like X- headers, Pragma and Caching, etc.

   There are a few plugins that are usable for this for Wordpress (probaly other things, but not the admin panel or customer accounts). And that depends on Wordpress users using it and only for their individual sites. Plus they are notoriously problematic for those users who do not know how to use them, and so pulling it back to admin would be much better. One example for Wordpress, to show what I am thinking of (the one I use but have no 'interest'/connection with the maker of, is this one (maybe as an indication of what I would think would be good):

   https://wordpress.org/plugins/gd-security-headers/

   this is comprehensive and powerful, but it is a bit complex compared to some others. Still it would simplify/enhance things a lot compared to just plugging values in manually to the Apache/Nginx/Lightspeed htaccess/etc. editor (the one in that tiny box that is SO problematic to use).

   Here is Plesk's, which whilst not A+ is still much better than most of the web - would be great to see Plesk overtake cPanel and other things like that in doing that, if nothing else, on the Agency Plan

   https://securityheaders.com/?q=plesk.com&followRedirects=on

   • well, no permissions policy, no referers policy, risky contents-security policy, risky access control allow, none of the future-proofing headers, not using HTTP/3, revealing use of Plesk and PHP (and version) and server, still using public caching (but secure cookie policy!), using Lightspeed (which we don't get on the agency plan), no pinning, no brotli, etc. but still, better than GCHQ!

   I have to say I was delighted to see that Plesk.com (unlike so many sites) has all its security headers* in order, but it would be really good if this was a thing that could be operated easily from within Plesk given the massive importance of them. It would also tidy up A LOT of the stuff to do with many of the things that people are asking on here with things like X- headers, Pragma and Caching, etc.

   There are a few plugins that are usable for this for Wordpress (probaly other things, but not the admin panel or… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   We understand that you are asking to add specific headers and maybe to remove others, but the broad range of what could be expected does not allow this to be done in a single feature request. It is also not possible to standardize such settings as the vast number of users all require different settings. All headers can already be individually set, it just needs an individual analysis what makes sense and what does not, tailored to each website.

   -- PD

8. Migration from Enkompass (CPanel for Windows)

   We would really like to move 6 of our Enkompass Servers (CPanel for Windows) to Plesk as CPanel dropped development for enkompass some years ago and we would like an nice migration from Enkompass.

   I could mirror our production environment to a test bed to help with development if need be.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Migrations  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input!
   Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
   —
   IG

9. Improve knowledgebase article on testing prior to DNS migration

   You suggest use of the hosts file to point the domain at HostGator prior to DNS migration. This does not work in most cases for Windows Enterprise shared hosting.

   Further, using the temporary domain solution you support, ASP.Net applications do not work if they require a web.config file (which they almost always do)

   My understanding is that, although you recommend these approaches in your knowledgebase article, you do not actually support them. Assuming the issues above cannot easily be fixed, the documentation needs to provide a warning that they do not work with Windows shared hosting.. Further add a suggestion to use a different (currently unused) test subdomain (that can be pointed at HostGator immediately) for testing rather than the intended domain.That is not ideal, but better than wasting time trying to make it work, especially as some of your support staff seem to be unaware that the techniques cannot work, but under instructions not to investigate.

   You suggest use of the hosts file to point the domain at HostGator prior to DNS migration. This does not work in most cases for Windows Enterprise shared hosting.

   Further, using the temporary domain solution you support, ASP.Net applications do not work if they require a web.config file (which they almost always do)

   My understanding is that, although you recommend these approaches in your knowledgebase article, you do not actually support them. Assuming the issues above cannot easily be fixed, the documentation needs to provide a warning that they do not work with Windows shared hosting.. Further add a suggestion… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Documentation  ·  Delete…  ·  Admin →
   not a feature  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   To solve your issue, please open https://support.plesk.com/hc/en-us/requests/new and file a ticket. Responsible person in Plesk Support will improve KB articles according to your recommendations. We are closing your request as it doesn’t include any software improvement proposal.
   —
   IG

10. Integration of AI to Monitor Errors, SupportBot via Chat GPT Api

    Idea: Server SupportBot :via Chat GPT Api

    Brief Description :

    The Specific Integration of AI to Monitor Errors, via error logs and the status of system services such as CPU Memory and HDD/SSD loads .

    Result :

    to display a notification that
    a) the issue occurred as quickly as possible
    b) to display a possible cause and
    c) display the possible fix

    Overview:
    Integration of ChatGPT API 4.0 with Plesk to enable the development of a chat support bot that provides server support to the Administrator/Server management. this could be incorporated into the Android/iPhone App .

    whereas

    The SupportBot can be designed to handle common server-related issues, such as server performance warnings, taking CPU overload Memory Capacity and HDD getting beyond 75% and checking system status, get the information on what is causing the issue also with the Alert to get a possible Suggestions to resolve

    prompt: check for app/service that is making the system at capacity and return Plesk FAQ. Documents and Other known information about what can be done.and provide notification on what needs to be done

    supportbot would poll server error logs , ChatGPT would have permission to view just the error logs and set a level that activates troubleshooting its already capable of telling what may be wrong from just pasting the prompt what is causing this error in apache and other error logs

    Over time more tracking solutions can be added to look at specific, Security, Updates and more

    Idea: Server SupportBot :via Chat GPT Api

    Brief Description :

    The Specific Integration of AI to Monitor Errors, via error logs and the status of system services such as CPU Memory and HDD/SSD loads .

    Result :

    to display a notification that
    a) the issue occurred as quickly as possible
    b) to display a possible cause and
    c) display the possible fix

    Overview:
    Integration of ChatGPT API 4.0 with Plesk to enable the development of a chat support bot that provides server support to the Administrator/Server management. this could be incorporated into the Android/iPhone App .

    whereas

    The SupportBot… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your visionary idea! We might consider such implementation if the technology needed to do it becomes available. At this time, Chat GPT API is not capable to support the requested implementation.

    Everyone, please continue voting for this feature if you consider it important.

    -- PD

11. Limitation for FTP username

    Presently there is 16-char limitation for FTP username. This hinders migration from obscure hosting systems that use longer usernames.
    Please, consider implementing the feature that would remove this 16-char limitation if Providers opts to do so.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
    completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Increased the maximum length of FTP usernames to 32 characters – https://docs.plesk.com/release-notes/onyx/change-log/#contents-179-preview12
    —
    IG

12. Reload PHP-FPM only once with `/usr/local/psa/bin/php_settings -u` (Plesk 12.5)

    To update custom PHP-FPM pool settings, the command /usr/local/psa/bin/php_settings -u should be used to include any new custom files from /var/www/vhosts/system/*/conf/php.ini

    However, this command seems to reload PHP-FPM for every subscription, which will cause unnecessary downtime on servers with a larger number of subscriptions.

    This behavior was fixed only for the newest version of Plesk Onyx (17.5).
    Unfortunately it was not fixed for Plesk 12.5 yet, which is still supported by Plesk.

    This issue could expectedly be solved quite easily, by modifying the script in /usr/local/psa/bin/php_settings to only perform a single PHP-FPM reload only once, at the end of the script.

    Could this command be modified for Plesk 12.5 so that PHP-FPM will reload only once, with minimal downtime?

    ---

    PS our request on the forum ultimately did not receive a response, see https://talk.plesk.com/threads/usr-local-psa-bin-php_settings-u-reloads-php-fpm-for-every-subscription.342481/

    To update custom PHP-FPM pool settings, the command /usr/local/psa/bin/php_settings -u should be used to include any new custom files from /var/www/vhosts/system/*/conf/php.ini

    However, this command seems to reload PHP-FPM for every subscription, which will cause unnecessary downtime on servers with a larger number of subscriptions.

    This behavior was fixed only for the newest version of Plesk Onyx (17.5).
    Unfortunately it was not fixed for Plesk 12.5 yet, which is still supported by Plesk.

    This issue could expectedly be solved quite easily, by modifying the script in /usr/local/psa/bin/php_settings to only perform a single PHP-FPM reload only once, at the end… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Let’s discuss it on the forum.

    — rk

13. Enabling anonymous Git read access for a repository

    A developer which has pushed his code to his git repository in plesk (through Local repository on your workstation funcion) is only accesible through authentication. That's OK.

    The developer is ready to make his code publicly available.
    Unfortunately that is not possible but it would be a nice feature to have.

    Maybe not to use the same private repository, but likely in a way to clone it and make it anonymous available only with read acces through http(s) , ex. https://<url>/example.git

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Web  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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.
    —
    IG

14. Is it possible to ship plesk php versions with ZTS enabled?

    The PLESK php versions are compiled without ZTS which makes it impossible to install the pthreads extension to utilize threading. In some scenarios this is a problem because there are actually long running scripts which would benefit from threading due to how php releases memory with it's garbage collector and also it would help reduce load as currently all php scripts run single threaded utilizing the cores fully without being able to split the load over the multicore cpu.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Web / PHP  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. add functionality for pre-install checker to check supported components and prohibit installation on case unsupported components are found

    It would be great to not have an ability to install Plesk on a system that is using a component (database server, e.x.) that is not supported by the Plesk version.
    Please consider implementing the functionality of the pre-install checking of unsupported components. It can prevent issues with Plesk on the servers with unsupported software.
    Such an idea has already been provided once, however, it was too specific (for database servers only): https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/20166910-prohibit-installation-on-unsupported-databases.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  IgorG responded

    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.
    —
    IG

16. Smart Email Log Dashboard

    Currently, Plesk only allows a raw, line-by-line view of mail logs through tools like Mail Log Browser. However, there is no real centralized and user-friendly interface that enables users to easily and clearly review the history of sent and received emails on the server.

    The idea is to provide a global dashboard that groups together all domains and all existing mailboxes, offering a clear and organized chronological view of messages handled by the server. Each row would represent a single message (incoming or outgoing), with the main information immediately visible: sender, recipient, delivery status, spam score, date and time, and email subject.

    Using advanced filters, it should be possible to narrow down the view by domain, by individual mailbox, or by groups of mailboxes, making both detailed and high-level monitoring easier. By clicking on a message, users would access more technical details, such as the sender’s or recipient’s IP address, the Message-ID, any SMTP error codes, and a full description of the error in case of delivery failure.

    A tool like this would be extremely valuable for both system administrators and clients, simplifying the identification of delivery issues and improving transparency and control over email communications. It would represent a major improvement over the current basic log view, delivering a much more modern and efficient user experience.

    Currently, Plesk only allows a raw, line-by-line view of mail logs through tools like Mail Log Browser. However, there is no real centralized and user-friendly interface that enables users to easily and clearly review the history of sent and received emails on the server.

    The idea is to provide a global dashboard that groups together all domains and all existing mailboxes, offering a clear and organized chronological view of messages handled by the server. Each row would represent a single message (incoming or outgoing), with the main information immediately visible: sender, recipient, delivery status, spam score, date and time, and… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Mail  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add option to hide DKIM management

    We haven an external DNS cluster and an external customer panel in which customers can manage things like DNS records etc.

    We have implemented a function through which we can let the customer enable DKIM through the external panel, which enables it on the Plesk server, retrieves the key, and adds the key to the zone on the DNS cluster

    In order to avoid conflicts and confusion we would like to hide the DKIM settings in Plesk for the customer on the subscription level.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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

18. Roundcube Sieve Autoresponder missing DKIM signature

    In the current implementation, sieves autoresponder is using an empty sender address for auto reply.

    We suggest the following config change:

    /etc/dovecot/conf.d/90-plesk-sieve.conf
    

    plugin {
      sieve = ~/.dovecot.sieve
      sieve_dir = ~/sieve
    
      # Horde webmail (Ingo sieve backend) is not aware of RFC 'imap4flags' and
      # 'enotify' extensions. Enable old deprecated ones.
      sieve_extensions = +notify +imapflags
    
      sieve_vacation_send_from_recipient = "yes"   # <- New
    }
    

    This setting ensure that the original recipient is used as envelope sender address for the auto reply, especially required for big providers like google and microsoft. This setting also enables DKIM signing for auto responder to be compliant with SPF / DKIM and DMARC policies.

    In the current implementation, sieves autoresponder is using an empty sender address for auto reply.

    We suggest the following config change:

    /etc/dovecot/conf.d/90-plesk-sieve.conf
    

    plugin {
      sieve = ~/.dovecot.sieve
      sieve_dir = ~/sieve
    
      # Horde webmail (Ingo sieve backend) is not aware of RFC 'imap4flags' and
      # 'enotify' extensions. Enable old deprecated ones.
      sieve_extensions = +notify +imapflags
    
      sieve_vacation_send_from_recipient = "yes"   # <- New
    }
    

    This setting ensure that the original recipient is used as envelope sender address for the auto reply, especially required for big providers like google and microsoft. This setting also enables DKIM signing for auto responder… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Mail  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Option to manange access to extensions for the additional administrators with restricted mode enforced

    It'd be great to have an option to select which extensions are available to the additional administrators with restricted mode enabled and which are not.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    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!     

    
    

    -- 

    IG

20. Welcome-Panel for new customers

    Possibility to add & edit a welcome message or screen for new customers, describe the very first steps and so on. An area above the "Websites & Domains" heading would be enough, but also a welcome screen or dashboard would be a good idea, editable by the server admin (or reseller).
    And a possibility to remove the implemented help screen for switching between classic andactive list. I think for most of my customers this information is quite irrelevant, they'd need more support on other things. Maybe the content of this help screen could be editable by server admin?

    Other possibility (or additional): a help section, editable by the server admin.

    Possibility to add & edit a welcome message or screen for new customers, describe the very first steps and so on. An area above the "Websites & Domains" heading would be enough, but also a welcome screen or dashboard would be a good idea, editable by the server admin (or reseller).
    And a possibility to remove the implemented help screen for switching between classic andactive list. I think for most of my customers this information is quite irrelevant, they'd need more support on other things. Maybe the content of this help screen could be editable by server admin?

    Other… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input!
    Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
    —
    IG