944 results found

1. Add rate-limiting rules to Fail2Ban

   Please implement a rule for rate-limiting requests from outside resources and include it into Fail2Ban's default ruleset.

   5 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  ·  Security  ·  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. Add IgnoreHosts options to Plesk`s DMARC implementation

   Currently it is possible to whitelist only domain with IgnoreMailFrom parameter. However there could be false-positive DMARC failures (in case sender's strict policy and mail going throughout relay) due to which it could be useful to have option to whitelist specific network. It would be nice having this option available

   12 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

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

   We are closing the current request due to low demand and lack of reasonable explanation on why "IgnoreHost" is required over SRS.

   
   

   Please use Tools & Settings > Mail Server Settings > SPF local rules to configure an SPF record which will be used by Plesk to validate emails (including emails from an intermediate anti-spam solution). See KB article for mode details (https://support.plesk.com/hc/en-us/articles/360022753174) and Plesk documentation.

   
   

   -- SH

3. Allow the use of LetsEncrypt for default certificates

   I would like to be able to use the Let's Encrypt extension to add new certs to the "list of certificates in server pool" and make use of a Let's Encrypt (LE) cert as the "default certificate" for domains that have not added their own specific certificate.

   I thought this was already possible, but was incorrect. I added a LE cert on the Tools/Settings > SSL/TLS Certificates page, and made it the default certificate.

   However, I used a different certificate to secure the Panel and the mail server. It appears, in that case, the LE cert will never be renewed.

   I would like to have the LE certificate renewed if it's set as the default cert even if it is not used to secure the Panel or the mail server.

   I don't consider using LE certs a good idea to secure the mail server because some e-mail clients, especially Apple clients, break when the cert is changed or renewed, causing end user support problems. Due to this, I use a different cert, that lasts for 2 years, to secure the mail server, to avoid that issue happening frequently (every 90 days). See...

   https://support.plesk.com/hc/en-us/articles/115004756974-Mail-users-with-iOS-and-MacOS-devices-cannot-access-mail-after-certificate-renewal-on-Plesk-server-Cannot-Verify-Server-Identity

   Thanks for your consideration.

   I would like to be able to use the Let's Encrypt extension to add new certs to the "list of certificates in server pool" and make use of a Let's Encrypt (LE) cert as the "default certificate" for domains that have not added their own specific certificate.

   I thought this was already possible, but was incorrect. I added a LE cert on the Tools/Settings > SSL/TLS Certificates page, and made it the default certificate.

   However, I used a different certificate to secure the Panel and the mail server. It appears, in that case, the LE cert will never be renewed.

   … 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  ·  Web / SSL  ·  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

4. Different notification settings for available WordPress updates: Plugin, Theme or WordPress core

   Email notifications to customers are sent on every available WordPress update, that's far too much. My clients don't take them for important anymore and don't update at all. I suggest to fine tune available settings in Tools & Settings > Notifications > APS application updates (customer’s digest): Different notification options if the available update is a WordPress Core update, a plugin update or a theme update. So for example the plugin and theme update notification could be turned off for customers, but WordPress core update notifications would be still sent.

   Another suggestion would be an option to cutomize the FREQUENZY (= e.g. once a week, once a month) for sent digest mails, as it was already asked for in this here (and closed as already available, but it's NOT available):

   https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/6034455-stop-wordpress-toolkit-emails-going-out-every-nigh
   https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/6665897-wordpress-update-notification-e-mails-adjust-mai

   Email notifications to customers are sent on every available WordPress update, that's far too much. My clients don't take them for important anymore and don't update at all. I suggest to fine tune available settings in Tools & Settings > Notifications > APS application updates (customer’s digest): Different notification options if the available update is a WordPress Core update, a plugin update or a theme update. So for example the plugin and theme update notification could be turned off for customers, but WordPress core update notifications would be still sent.

   Another suggestion would be an option to cutomize the… more

   20 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

   6 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

   Thanks for submitting this suggestion. It definitely looks useful, so we’ll consider adding it in upcoming Plesk / WPT updates.

   Everyone, please continue to vote for this feature so we could evaluate its popularity.

   —AK

5. Add an ability to change mail queue lifetime from control panel

   Currently, it is only possible to change mail queue lifetime from CLI. It would be useful to be able to set this from Plesk UI as well.

   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  ·  Panel/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

6. Ability to automatically delete a mail after being forwarded using the XML API

   Give to the XML API in the node forwarding, an option to automatically delete a mail after being forwarded.

   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

   1 comment  ·  API  ·  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
   more input required  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Forwarded emails (by a forwarding configuration in the mail server) are not stored. Could you please describe the start situation from where you forward an email? Is it truly mail forwarding or is it sending an email to a recipient that resides in the mailbox?

   -- PD

7. Add SSH2 extension to PHP default extensions to improve security

   Hi,

   Please consider add SSH2 extension to PHP default available extensions.

   To be able to use FTP over SSH (SFTP) the SSH2 extension must be installed on PHP.

   IN SHORT: SFTP (SSH2 EXTENSION) = SECURITY

   SFTP means secure file transfer via Secure Shell (or SSH), hence the name SSH File Transfer Protocol (SFTP). The two devices (server and client) communicate via a single channel, that of SSH, in which the remote file management commands are sent and where the file transfer takes place. By default, the only port required for SFTP is 22, the same as SSH.

   SFTP implements the same specifications at the cryptographic level supported by SSH, also TLS 1.3.

   WHAT ARE FTP AND SFTP:

   FTP is the traditional file transfer protocol. It’s a basic way of using the Internet to share files. SFTP (or Secure File Transfer Protocol) is an alternative to FTP that also allows you to transfer files, but adds a layer of security to the process. SFTP uses SSH (or secure shell) encryption to protect data as it’s being transferred. This means data is not exposed to outside entities on the Internet when it is sent to another party.

   Businesses often choose SFTP solutions due to enhanced security. However, many others still rely on FTP to facilitate data transfers. To better understand which file sharing option can meet your company’s needs, let’s look at the differences between SFTP vs. FTP. Understanding how these file transfer options differ will help you choose which option is best to transfer your data. There are three key areas in which SFTP vs. FTP differ: encryption, firewalls, and potential vulnerabilities.

   ENCRYPTION:

   Transferring data is a vital, day-to-day task for many businesses. While some data transfers may not require protection, other files may house sensitive information – information that is too sensitive to fall into the wrong hands. This is why encrypting your data is essential. Encryption scrambles data, making it decipherable only by the sender and the recipient, ensuring that even if a file is intercepted, it won’t be intelligible to any unintended parties.

   So, how does encryption impact your choice between SFTP vs. FTP? The traditional file transfer protocol (FTP) is a simple way of transferring data, but it offers nothing in terms of data protection. Files are transferred without encryption, making data readable for anyone who intercepts it. While this is fine if you’re just sending unimportant files, this could lead to major data compromises if you’re sending crucial data.

   SFTP, in contrast, offers a secure shell protecting files. Because files are encrypted, you don’t have to worry about data falling into the wrong hands. This is the ideal mode of transfer for any file that you want to protect. SFTP uses an encrypted type of fingerprint technology to first verify host keys before any data transfer has taken place.

   In terms of compliance, encryption makes a huge difference. If your organization is subject to compliance standards (including, but not limited to, the ones listed below), you could face serious consequences if you fail to encrypt data:

   HIPAA
   ITAR
   PCI-DSS
   SOX
   GLBA

   Encryption isn’t just a feature offered by SFTP that’s nice to have. It’s an essential step you should take to protect your data. If you fail to comply with these standards, your business could be subject to some serious fines.

   FIREWALLS:

   Another way in which FTP and SFTP differ is how channels are used. When you send files via FTP, this protocol needs to open multiple channels in order to complete the transfer. While the client and software negotiate these channels automatically, the client-side firewalls need to open multiple ports. Opening multiple channels can also open the client’s firewalls to vulnerability.

   SFTP presents a more secure process for the client-side firewall. Only port 22 will need to be open to send and receive data. This simplifies firewall configurations and is a better choice in terms of file sharing security.

   VULNERABILITIES:

   In addition to encryption and firewalls, SFTP beats FTP in terms of potential vulnerabilities, too. Any vulnerability can potentially be exploited and turned into a data breach. When it comes to inherent vulnerabilities in the file transfer process, FTP has a number of prominent ones.

   The first vulnerability is that FTP is prone to human error. Sending a file to the wrong recipient or sending the wrong file altogether can lead to some serious problems for your company. With a greater level of security provided by SFTP, you can minimize the potential for human error. You can also take steps to promote a culture of security awareness within your business to reduce the potential for human error.

   Intercepting data is simple with FTP, too. All it takes is the right tools and a little bit of knowledge to take advantage of these vulnerabilities. Even the most amateur hackers can intercept an FTP transfer. Sensitive data is often worth too much to risk a breach.

   Again, host keys can present vulnerabilities. Unlike SFTP which uses host keys to verify a recipient's identity before a transfer takes place, FTP does not. This is yet another way FTP transfers are less secure. All it takes is one accidental transfer to a wrong recipient for a file to be compromised.

   When it comes to secure data transfers, SFTP is your best option. You can feel confident that encryption measures are up to compliance standards, and you’re avoiding the inherent vulnerabilities of FTP transfers.

   Thanks to ftptoday(dot)com for this documents:
   - What are FTP and SFTP;
   - Encryption;
   - Firewalls;
   - Vulnerabilities.

   Thanks in advance for the support.

   Hi,

   Please consider add SSH2 extension to PHP default available extensions.

   To be able to use FTP over SSH (SFTP) the SSH2 extension must be installed on PHP.

   IN SHORT: SFTP (SSH2 EXTENSION) = SECURITY

   SFTP means secure file transfer via Secure Shell (or SSH), hence the name SSH File Transfer Protocol (SFTP). The two devices (server and client) communicate via a single channel, that of SSH, in which the remote file management commands are sent and where the file transfer takes place. By default, the only port required for SFTP is 22, the same as SSH.

   SFTP implements the… more

   33 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  ·  Web / PHP  ·  Delete…  ·  Admin →
   completed  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Since Plesk Obsidian 18.0.49 that was published December 20th, 2022, the Plesk PHP configuration page in "Tools & Settings" has a new option where you can easily install PHP PECL packages. The SSH2 extension is a PECL package as described in https://pecl.php.net/package/ssh2. It can be installed right out of the Plesk user surface using the new PECL installer.

   -- PD

8. Can you increase the number of allowable blacklist addresses in control panel from 100 to 2000?

   You have a limit to the number of blacklist email addresses which is clearly not enough as I am getting spam continuously.
   I keep adding them to blacklist but because I am already at 100 entries they just keep coming.
   It is very annoying.
   Please take this into consideration.
   Thanks

   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 →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

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

9. Option when forwarding mail not to include original message just a notification that there is a message to be read..

   I would like to be able to send a noitfication to my work account that I have mail. I do not want my work address to see the content of that mail.
   In the forward options smb/email-address/edit/id/xxx
   On the Forwarding tab. Include a checkbox that says something like Notify but do not include message content. The default should be unchecked withno change to the current functionality. When checked on receipt of an email a different message should be sent to the addresses specified in the list box labeled "Forward incoming messages to the following email address" saying that an email has been recieved and the senders address. It is important that the subject and the body are not sent.

   I would like to be able to send a noitfication to my work account that I have mail. I do not want my work address to see the content of that mail.
   In the forward options smb/email-address/edit/id/xxx
   On the Forwarding tab. Include a checkbox that says something like Notify but do not include message content. The default should be unchecked withno change to the current functionality. When checked on receipt of an email a different message should be sent to the addresses specified in the list box labeled "Forward incoming messages to the following e… 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  ·  Delete…  ·  Admin →
   declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   We are closing the request due to lack of demand over the years. We still value your feedback and we would like to thank you for the suggestion.

   
   

   -- SH

10. Prevent Postfix from modifying "From" Header for authenticated users.to mail address that doesn't belong to them

    An authenticated SMTP user (e.g., user1@example.com) is able to send emails with a different "Mail From" address (such as user2@example.com), even though both addresses belong to the same domain. This behavior is undesired, as it allows users to impersonate other valid users within the domain.

    Our goal is to prevent this kind of spoofing by enforcing a match between the authenticated SMTP identity and the actual sender address.

    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  ·  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

11. Plesk API: Allow displaying / using of [last login] & [number of failed login attempts since last successful login]

    When it comes to e-mail accounts the API can only be used for getting the quota.
    Please consider implementing ways of getting time of last successful login + failed login attempts since last successful login.

    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  ·  Documentation  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

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

12. Import existing accounts from SmarterMail remote to Plesk

    We have a remote server for mail with SmarterMail. We have a problem, when the clients creates an account from SmarterMail, there is no automatic script or something from Plesk that synchronises all the accounts.

    5 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  ·  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
    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

13. check passwords against Pwned Passwords API

    Plesk should check user typed passwords against Pwned Passwords API

    https://haveibeenpwned.com/API/v2

    that way you could further improve systems running Plesk against Brute-Force attacks - and Dictionary attacks

    WordFence plugin for WordPress is already offering this, checking WordPress administrator passwords against https://haveibeenpwned.com/API/v2

    it shouldn't be too much work to compare Plesk password hash between Plesk and https://haveibeenpwned.com/API/

    I would like to use this feature for all services (FTP, E-Mail, Plesk, WordPress, etc.)

    It makes a lot of sense to do this, there are no drawbacks
    it should be option that users can enable/disable
    if you don't need it, you can disable it
    leave it enabled, your server will be more secure

    Plesk should check user typed passwords against Pwned Passwords API

    https://haveibeenpwned.com/API/v2

    that way you could further improve systems running Plesk against Brute-Force attacks - and Dictionary attacks

    WordFence plugin for WordPress is already offering this, checking WordPress administrator passwords against https://haveibeenpwned.com/API/v2

    it shouldn't be too much work to compare Plesk password hash between Plesk and https://haveibeenpwned.com/API/

    I would like to use this feature for all services (FTP, E-Mail, Plesk, WordPress, etc.)

    It makes a lot of sense to do this, there are no drawbacks
    it should be option that users can enable/disable
    if you don't need it, you… more

    8 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  ·  Security  ·  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. Ability to create custom MX records via DNS Templates with <domain> placeholder in the middle

    Ability to create custom MX records via DNS Templates with <domain> placeholder in the middle of the value.

    For example, currently, it is not possible to create a record via DNS Templates:
    <domain>. MX mx.<domain>.example.com

    It can be useful for setting up an external mail service with a hostname based on a domain name.

    6 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

    3 comments  ·  DNS  ·  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.
    —
    IG

15. add posibility to secure webmail with Let's Encrypt certificate for the subdomain with 'No web hosting' type

    The issued certificate should be also available for selecting in Domains > subdomain.name > Mail Settings > SSL/TLS certificate for mail

    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

    1 comment  ·  Web / SSL  ·  Delete…  ·  Admin →
    already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Verified that it is possible to create a certificate for the webmail subdomain although the hosting type is set to "no web hosting".

    -- PD

16. Apply mail filters to existing emails in PPE

    At this time, Plesk Premium Email filters use sieve filters, which by default are only applied to new emails.

    An option should exist such as a Run Now button which applies the filter to existing emails like what can be done within Outlook, as can be done through CLI with this method:
    https://shoreless.limited/en/knowledge-base/kb20224071315-reapply-dovecot-sieve-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

    1 comment  ·  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. Upgrade MailEnable in Windows editions to support SSL/TLS

    The Windows edition of Plesk is currently using MailEnable as its E-Mail server and it is a community edition (Standard) which does not support secured services such as SMTP/s, IMAP/s, POP3/s. So its the only problem for us to get PCI compliance unless we buy it ourselves with a higher annually price. The Plesk company may deal with them for upgrading at least to the Professional edition and make it available in licensing with a suitable monthly price.

    6 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  ·  Mail  ·  Delete…  ·  Admin →
    already available  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Good news everyone :)
    Starting Plesk Onyx 17.5 the installation contains Mail Enable 9.10, which supports SSL/TLS in Standard edition.

18. Delete/Reject Option for incoming mail addresses in blacklist

    Add delete/reject option for addresses and or domains in the blacklist. If I've blacklisted a domain, chances are that I don't want anything from that source.

    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

    1 comment  ·  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
    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

19. Add more SSL Options.

    Add 4096 Bit option, along with SHA options SHA1, SHA256 and SHA512 for both "Create" and "Self-Sign"
    It would also be good if we could assign SSL certificates in the panel to ..

    webmail
    mail

    Regards

    Lloyd

    5 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  ·  Delete…  ·  Admin →
    declined  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.

    —

    IG

20. Add option to modify the upload_max_filesize and post_max_size Globally via Plesk Admin

    Add the option to modify the uploadmaxfilesize and postmaxsize Globally via Plesk Admin > Tools & Settings > Mail Server Settings.
    The "Maximum message size" is already a Global setting in "Mail Server Settings" and these 2 settings should also be there.
    Currently the only way to modify these settings in Linux is via a command line in Terminal and Horde, RoundCube, & Kolab all use different php.ini files for these same settings. I believe it would make for a much more user friendly experience if these options were a Global Setting modified preferably via "Plesk Admin > Tools & Settings > Mail Server Settings".

    Add the option to modify the uploadmaxfilesize and postmaxsize Globally via Plesk Admin > Tools & Settings > Mail Server Settings.
    The "Maximum message size" is already a Global setting in "Mail Server Settings" and these 2 settings should also be there.
    Currently the only way to modify these settings in Linux is via a command line in Terminal and Horde, RoundCube, & Kolab all use different php.ini files for these same settings. I believe it would make for a much more user friendly experience if these options were a Global Setting modified preferably via… more

    4 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
    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