G J Piper

My feedback

  1. 36 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Feature Suggestions » Databases  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  2. 466 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    131 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →

    Could you provide more information about your scenario? In particular, could you explain which settings you want to be automatically discovered and at which step of your scenario?

    UPD: We will evaluate the possibility of adding this functionality in the future releases. Note that this feature also depends on your mailing client.

    —AK

    G J Piper commented  · 

    @analyzer: Each type of client looks for settings in various places, some unique to that client. Some look in a variety of places starting with its preferred address/port then trying others if nothing is found. The difficulty is having the correct settings for your server found in all the places every client may look. Some of the types of settings files allow you to specify a "preferred" configuration, and a secondary configuration in addition -- allowing the end user to choose between them if their client supports it.

    G J Piper commented  · 

    @analyzer: I have several manually created autodiscover/autoconfig setups that specifically preselects/forces POP configuration and does not give the user a choice of IMAP. The user does however have the option of setting up their client manually and using IMAP.

    G J Piper commented  · 

    When this is implemented, it will also need to have the domain name fully customizable for those of us that use Plesk for an email-only server.

    I have the email domains as root domains (domain.tld) on the server, but I have remote DNS handled so that mail.domain.tld is the MX pointing to the server.

    So, if the autodiscover output says that the mail server is at "domain.tld" it will fail. Don't make it fully automatic without the ability to define the server domain manually.

    G J Piper supported this idea  · 
  3. 32 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper commented  · 

    I'd just like to be able to check a box in the Plesk UI, and then be able to enable the built-in iOS VPN setting in my iPhone and have a secure tunneled date stream straight through my server's IP address. Seems like it should be as simple as setting up an email account.

    G J Piper supported this idea  · 
  4. 11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Feature Suggestions » Extensions  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  5. 37 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  6. 43 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  5 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  7. 70 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  8. 379 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
    G J Piper commented  · 

    While this would be a great feature, my understanding is that postfix is incapable of serving certs on multiple hosted domains. Admin: is this incorrect? Would the implementation of this require a migration from postfix to something else?

  9. 48 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Feature Suggestions » FTP  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  10. 7 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  3 comments  ·  Feature Suggestions » Web / PHP  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
    G J Piper commented  · 

    Changing FcgidInitialEnv PP_CUSTOM_PHP_CGI_INDEX from fastcgi to plesk-php72-fastcgi seems to have no effect, even after a server reboot.

    G J Piper commented  · 

    Especially the newest Plesk supported version — PHP 7.2 at this moment.

    G J Piper shared this idea  · 
  11. 66 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
    G J Piper commented  · 

    Yes having a GUI for "fail2ban-client set recidive (un)banip <IP Address>" would be fantastic. Seems like an easy addition since the client already exists.

  12. 30 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  13. 26 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  14. 28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  5 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  15. 917 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  157 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper commented  · 

    I had written a script that would do it about 5 years ago. The trick was to keep the offending users' email from getting more than one email notice at a time. I had it set to run from cron every hour. Every time it ran, it would scan for (real, non-alias) accounts that were up to 95% of quota. For each account that was close to max quota, it would scan all that account's inbox email for a specific code string that gets sent on the bottom of every "notice" email. If it didn't find the string, it would send that account a notice email. If it did find the string, it would skip sending so as to not bombard the user with dozens of notices. It worked pretty well!

    I'm reluctant to dig up this script again as I'd much rather use a Plesk solution for this problem, which I know from my example can be done. I tried briefly to get it working again a year or so ago, but couldn't find an easy way to scan the quotas like I had when I was using a FreeBSD server with command-line quota tools.

    Anyway, this is one way it could be done. Please consider it, Plesk masters. :-)

    G J Piper commented  · 

    This is a must-have item.

    G J Piper supported this idea  · 
  16. 29 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 » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  17. 3 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Usability and UI  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper shared this idea  · 
  18. 19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Feature Suggestions » WordPress Toolkit  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
  19. 401 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper commented  · 

    v2.2.2+ doesn't work for webmail if the domain name isn't hosting a website on the server. Using the extension to encrypt webmail.domain.ext on a strictly mail server isn't possible -- would like it to be! :-) Please make it so.

    G J Piper commented  · 

    We need to make sure the Plesk plugin will allow Let's Encrypt to be used with webmail.domans.tld even when the domain is not hosting a website — only email/webmail.

  20. 5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    G J Piper supported this idea  · 
    G J Piper commented  · 

    Awesome! Thank you.

← Previous 1

Feedback and Knowledge Base