Redis

My feedback

  1. 22 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      4 comments  ·  Feature Suggestions » Backup / Restore  ·  Flag idea as inappropriate…  ·  Admin →
      Redis supported this idea  · 
    • 240 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        25 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
        Redis supported this idea  · 
      • 316 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          35 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
          Redis commented  · 

          Actually this is possible by commandline. I would suggest for plesk developers to set an option like that of "Secure plesk panel" with the ability to let the admin chose at plesk installation, or in settings in the following way:
          1) I setup my server that is named mainserver.domain.tld
          2) Plesk asks me to secure the panel, I select the checkbox, letsencrypt will generate a certificate for mainserver.domain.tld
          3) Plesk asks me which subdomain should use for the mail subscriptions: I input MAILSUBDOMAIN as a name or whatever I like
          4) Plesk uses letsencrypt with option --expand to expand certificate for mainserver.domain.tld to include mailsubdomain.domain.tld
          5) Everytime I create a new domain in plesk, plesk will automatically expand the existing certificate for mainserver.domain.tld and mailsubdomain.domain.tld adding mailsubdomain.domain2.tld mailsubdomain.domain3.tld etc up to 100 domains that it's the letsencrypt domain limitation(If I'm not mistaken)
          6) Plesk assigns this ssl to the plesk panel and mail server automatically every time it is renewed and keeps in database the list of existing domains, so it gets renewed with all the mailname.*.tld

          This way you have a standard that is used for mail service, and doesn't abuse letsencrypt.
          All the domains mailsubdomain.*.tld will be virtual and redirected to one single directory for letsencrypt acme challenge. If someone opens mailsubdomain.domain.tld in the browser, it gets redirected to webmail(sort of alias)
          All the rest of the domains remain like it is now.

          That is my suggestion of how I think it would be the easiest way to implement, without too much hassle.

          Redis supported this idea  · 
        • 404 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            124 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

            Redis supported this idea  · 
          • 733 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              75 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
              Redis supported this idea  · 
            • 190 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                19 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
                Redis supported this idea  · 
              • 90 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  17 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
                  Redis supported this idea  · 
                • 645 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

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

                    Plesk currently offers two high-quality anti-viruses and other related services like WAF. Integrating another anti-virus solution is an expensive undertaking, so we’d like you to let us know which ClamAV features are missing in anti-viruses and services already available in Plesk. This will help us properly evaluate and prioritize this request.

                    —AK

                    Redis supported this idea  · 

                  Feedback and Knowledge Base