Setup policyd on Zimbra 8.8.x to rate limit the number of messages each account can send with smtp-auth Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!POSTFIX: Limiting the rate at which a particular user can send emailNetwork Hardware supports SMTP, but no AUTH information… Need to Send emails through SMTP with AUTHMX record for one domain so that other domain can send with the same fromHow can I prevent Postfix to send messages waiting in the incoming / active queue for more than 1 day?What could cause Mailman to drop messages after moderator approval?How can I disable sending mail through postfix smtp with out authPostfix SMTP Server fails to send messages to anyone outside the domainHow does zimbra procedes with sending email to the same domain if zimbra is configured to relay the messages to a proxy serverSetup Postfix with SMTP-AUTH over SASL2 with SASLDB for users to send emailsWhich parameters of zimbra or postfix limit the number or rate of emailing

Should I use a zero-interest credit card for a large one-time purchase?

How to react to hostile behavior from a senior developer?

Can a new player join a group only when a new campaign starts?

また usage in a dictionary

What are the out-of-universe reasons for the references to Toby Maguire-era Spider-Man in ITSV

An adverb for when you're not exaggerating

Old style "caution" boxes

What does "lightly crushed" mean for cardamon pods?

Is this homebrew Lady of Pain warlock patron balanced?

Did MS DOS itself ever use blinking text?

What's the meaning of "fortified infraction restraint"?

If my PI received research grants from a company to be able to pay my postdoc salary, did I have a potential conflict interest too?

Why didn't Eitri join the fight?

Is "Reachable Object" really an NP-complete problem?

Do I really need recursive chmod to restrict access to a folder?

Can an alien society believe that their star system is the universe?

Is CEO the profession with the most psychopaths?

Do jazz musicians improvise on the parent scale in addition to the chord-scales?

Why wasn't DOSKEY integrated with COMMAND.COM?

How can I use the Python library networkx from Mathematica?

Is there a kind of relay only consumes power when switching?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Fantasy story; one type of magic grows in power with use, but the more powerful they are, they more they are drawn to travel to their source



Setup policyd on Zimbra 8.8.x to rate limit the number of messages each account can send with smtp-auth



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!POSTFIX: Limiting the rate at which a particular user can send emailNetwork Hardware supports SMTP, but no AUTH information… Need to Send emails through SMTP with AUTHMX record for one domain so that other domain can send with the same fromHow can I prevent Postfix to send messages waiting in the incoming / active queue for more than 1 day?What could cause Mailman to drop messages after moderator approval?How can I disable sending mail through postfix smtp with out authPostfix SMTP Server fails to send messages to anyone outside the domainHow does zimbra procedes with sending email to the same domain if zimbra is configured to relay the messages to a proxy serverSetup Postfix with SMTP-AUTH over SASL2 with SASLDB for users to send emailsWhich parameters of zimbra or postfix limit the number or rate of emailing



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I'm running Zimbra 8.8.9 and I'm trying to rate limit the number of messages that a single user can send over smtp after authenticating with smtp-auth.
The purpose is to limit the damage in case one of the passwords of my users is guessed/obtained by a spammer.



Zimbra ships CBPolicyD (www.policyd.org) as part of zimbra-mta package, but it's disabled by default.



I followed the howto at https://wiki.zimbra.com/wiki/How-to_for_cbpolicyd and enabled policyd with:



zmprov ms zimbra.mydomain.tld +zimbraServiceInstalled cbpolicyd
zmprov ms zimbra.mydomain.tld +zimbraServiceEnabled cbpolicyd


I also activated the web interface:



 sudo -s
cd /opt/zimbra/data/httpd/htdocs
ln -s ../../../common/share/webui


and setup Zimbra's Apache to serve this new dir:



  • edit /opt/zimbra/conf/httpd.conf

  • add Alias /webui /opt/zimbra/common/share/webui/ to the end of the file

  • restart Zimbra

I edited the config file at /opt/zimbra/common/share/webui/includes/config.php to point to the proper sqlite db:



 $DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";


and finally added a cronjob to periodically cleanup the tracking database at the end of zimbra's crontab:



 # ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART
0 * * * * cat /opt/zimbra/log/clean_cbpolicyd_daily.sql | sqlite3 /opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb


I couldn't find a step-by-step example of how to setup the rate limiting using policyd webui and the interface is far from intuitive to use.



How do I have policyd count emails sent by each account and rate limit them?










share|improve this question




























    1















    I'm running Zimbra 8.8.9 and I'm trying to rate limit the number of messages that a single user can send over smtp after authenticating with smtp-auth.
    The purpose is to limit the damage in case one of the passwords of my users is guessed/obtained by a spammer.



    Zimbra ships CBPolicyD (www.policyd.org) as part of zimbra-mta package, but it's disabled by default.



    I followed the howto at https://wiki.zimbra.com/wiki/How-to_for_cbpolicyd and enabled policyd with:



    zmprov ms zimbra.mydomain.tld +zimbraServiceInstalled cbpolicyd
    zmprov ms zimbra.mydomain.tld +zimbraServiceEnabled cbpolicyd


    I also activated the web interface:



     sudo -s
    cd /opt/zimbra/data/httpd/htdocs
    ln -s ../../../common/share/webui


    and setup Zimbra's Apache to serve this new dir:



    • edit /opt/zimbra/conf/httpd.conf

    • add Alias /webui /opt/zimbra/common/share/webui/ to the end of the file

    • restart Zimbra

    I edited the config file at /opt/zimbra/common/share/webui/includes/config.php to point to the proper sqlite db:



     $DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";


    and finally added a cronjob to periodically cleanup the tracking database at the end of zimbra's crontab:



     # ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART
    0 * * * * cat /opt/zimbra/log/clean_cbpolicyd_daily.sql | sqlite3 /opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb


    I couldn't find a step-by-step example of how to setup the rate limiting using policyd webui and the interface is far from intuitive to use.



    How do I have policyd count emails sent by each account and rate limit them?










    share|improve this question
























      1












      1








      1








      I'm running Zimbra 8.8.9 and I'm trying to rate limit the number of messages that a single user can send over smtp after authenticating with smtp-auth.
      The purpose is to limit the damage in case one of the passwords of my users is guessed/obtained by a spammer.



      Zimbra ships CBPolicyD (www.policyd.org) as part of zimbra-mta package, but it's disabled by default.



      I followed the howto at https://wiki.zimbra.com/wiki/How-to_for_cbpolicyd and enabled policyd with:



      zmprov ms zimbra.mydomain.tld +zimbraServiceInstalled cbpolicyd
      zmprov ms zimbra.mydomain.tld +zimbraServiceEnabled cbpolicyd


      I also activated the web interface:



       sudo -s
      cd /opt/zimbra/data/httpd/htdocs
      ln -s ../../../common/share/webui


      and setup Zimbra's Apache to serve this new dir:



      • edit /opt/zimbra/conf/httpd.conf

      • add Alias /webui /opt/zimbra/common/share/webui/ to the end of the file

      • restart Zimbra

      I edited the config file at /opt/zimbra/common/share/webui/includes/config.php to point to the proper sqlite db:



       $DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";


      and finally added a cronjob to periodically cleanup the tracking database at the end of zimbra's crontab:



       # ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART
      0 * * * * cat /opt/zimbra/log/clean_cbpolicyd_daily.sql | sqlite3 /opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb


      I couldn't find a step-by-step example of how to setup the rate limiting using policyd webui and the interface is far from intuitive to use.



      How do I have policyd count emails sent by each account and rate limit them?










      share|improve this question














      I'm running Zimbra 8.8.9 and I'm trying to rate limit the number of messages that a single user can send over smtp after authenticating with smtp-auth.
      The purpose is to limit the damage in case one of the passwords of my users is guessed/obtained by a spammer.



      Zimbra ships CBPolicyD (www.policyd.org) as part of zimbra-mta package, but it's disabled by default.



      I followed the howto at https://wiki.zimbra.com/wiki/How-to_for_cbpolicyd and enabled policyd with:



      zmprov ms zimbra.mydomain.tld +zimbraServiceInstalled cbpolicyd
      zmprov ms zimbra.mydomain.tld +zimbraServiceEnabled cbpolicyd


      I also activated the web interface:



       sudo -s
      cd /opt/zimbra/data/httpd/htdocs
      ln -s ../../../common/share/webui


      and setup Zimbra's Apache to serve this new dir:



      • edit /opt/zimbra/conf/httpd.conf

      • add Alias /webui /opt/zimbra/common/share/webui/ to the end of the file

      • restart Zimbra

      I edited the config file at /opt/zimbra/common/share/webui/includes/config.php to point to the proper sqlite db:



       $DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";


      and finally added a cronjob to periodically cleanup the tracking database at the end of zimbra's crontab:



       # ZIMBRAEND -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRASTART
      0 * * * * cat /opt/zimbra/log/clean_cbpolicyd_daily.sql | sqlite3 /opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb


      I couldn't find a step-by-step example of how to setup the rate limiting using policyd webui and the interface is far from intuitive to use.



      How do I have policyd count emails sent by each account and rate limit them?







      postfix spam zimbra smtp-auth policyd






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 8 '18 at 22:31









      Luca GibelliLuca Gibelli

      2,11011423




      2,11011423




















          1 Answer
          1






          active

          oldest

          votes


















          0














          First of all note that policyd webui is not password protected unless you take additional measures, i.e. add an .htaccess to that dir and add an AllowOverride AuthConfig to httpd.conf:



           <Directory /opt/zimbra/common/share/webui>
          AllowOverride AuthConfig
          </Directory>


          Also note that by default policyd is only available on the cleartext web interface of Zimbra, i.e. http://zimbra.domain.tld:7780/webui/index.php



          Take appropriate steps to secure the web interface.



          Go to http://zimbra.domain.tld:7780/webui/policy-main.php and choose 'Add'.
          Enter the following:



          • Name: smtp-auth-limit

          • Priority: 1

          • Description: anything

          Go back to http://zimbra.domain.tld:7780/webui/policy-main.php and select the new 'smtp-auth-limit' policy then choose Action "Change". Set "Disabled" to "No" and submit.



          Now go back to http://zimbra.domain.tld:7780/webui/policy-main.php again, select 'smtp-auth-limit' again and choose action "Members".



          Enter the following:



          • Source: $*

          • Destination: any

          • Comment: anything

          Now be careful click on "Back to members" not "Back to policies" or you'll get lost.



          If you were careful, select the line with Source "$*" and choose Action "Change".



          If you were not careful, go back to http://zimbra.domain.tld:7780/webui/policy-main.php choose "smtp-auth-limit" policy, Action "Members", select the line with Source "$*" and choose Action "Change".



          Set "Disabled" to "No" and submit.



          Finally go to http://zimbra.domain.ltd:7780/webui/quotas-main.php and choose Action "Add".
          Enter the following:



          • Name: rate limit smtp auth

          • Track: SASLUsername:username

          • Period: 86400

          • Link to policy: choose 'smtp-auth-limit' from the drop-down menu

          • Verdict: Defer (delay)

          • Data: you talk too fast (this message will be shown to the sender)

          • Stop processing here: yes

          Go back to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select the 'smtp-auth-limit' policy, choose Action "Change".
          Set Disabled to "No" and submit.



          Go back once again to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select 'smtp-auth-limit' policy, choose Action "Limits".



          Select Action "Add" and enter the following, assuming you want to allow each account to send a maximum of 200 msgs every 86400 secs:



          • Type: Message Count

          • Counter Limit: 200

          • Comment: anything

          Now be careful, you know the drill, click on "Back to quota limits" or you'll get lost.
          Select the line with Counter Limit = 200 then choose Action "Change".
          Set Disabled to "No" and submit.






          share|improve this answer























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "2"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f934570%2fsetup-policyd-on-zimbra-8-8-x-to-rate-limit-the-number-of-messages-each-account%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            First of all note that policyd webui is not password protected unless you take additional measures, i.e. add an .htaccess to that dir and add an AllowOverride AuthConfig to httpd.conf:



             <Directory /opt/zimbra/common/share/webui>
            AllowOverride AuthConfig
            </Directory>


            Also note that by default policyd is only available on the cleartext web interface of Zimbra, i.e. http://zimbra.domain.tld:7780/webui/index.php



            Take appropriate steps to secure the web interface.



            Go to http://zimbra.domain.tld:7780/webui/policy-main.php and choose 'Add'.
            Enter the following:



            • Name: smtp-auth-limit

            • Priority: 1

            • Description: anything

            Go back to http://zimbra.domain.tld:7780/webui/policy-main.php and select the new 'smtp-auth-limit' policy then choose Action "Change". Set "Disabled" to "No" and submit.



            Now go back to http://zimbra.domain.tld:7780/webui/policy-main.php again, select 'smtp-auth-limit' again and choose action "Members".



            Enter the following:



            • Source: $*

            • Destination: any

            • Comment: anything

            Now be careful click on "Back to members" not "Back to policies" or you'll get lost.



            If you were careful, select the line with Source "$*" and choose Action "Change".



            If you were not careful, go back to http://zimbra.domain.tld:7780/webui/policy-main.php choose "smtp-auth-limit" policy, Action "Members", select the line with Source "$*" and choose Action "Change".



            Set "Disabled" to "No" and submit.



            Finally go to http://zimbra.domain.ltd:7780/webui/quotas-main.php and choose Action "Add".
            Enter the following:



            • Name: rate limit smtp auth

            • Track: SASLUsername:username

            • Period: 86400

            • Link to policy: choose 'smtp-auth-limit' from the drop-down menu

            • Verdict: Defer (delay)

            • Data: you talk too fast (this message will be shown to the sender)

            • Stop processing here: yes

            Go back to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select the 'smtp-auth-limit' policy, choose Action "Change".
            Set Disabled to "No" and submit.



            Go back once again to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select 'smtp-auth-limit' policy, choose Action "Limits".



            Select Action "Add" and enter the following, assuming you want to allow each account to send a maximum of 200 msgs every 86400 secs:



            • Type: Message Count

            • Counter Limit: 200

            • Comment: anything

            Now be careful, you know the drill, click on "Back to quota limits" or you'll get lost.
            Select the line with Counter Limit = 200 then choose Action "Change".
            Set Disabled to "No" and submit.






            share|improve this answer



























              0














              First of all note that policyd webui is not password protected unless you take additional measures, i.e. add an .htaccess to that dir and add an AllowOverride AuthConfig to httpd.conf:



               <Directory /opt/zimbra/common/share/webui>
              AllowOverride AuthConfig
              </Directory>


              Also note that by default policyd is only available on the cleartext web interface of Zimbra, i.e. http://zimbra.domain.tld:7780/webui/index.php



              Take appropriate steps to secure the web interface.



              Go to http://zimbra.domain.tld:7780/webui/policy-main.php and choose 'Add'.
              Enter the following:



              • Name: smtp-auth-limit

              • Priority: 1

              • Description: anything

              Go back to http://zimbra.domain.tld:7780/webui/policy-main.php and select the new 'smtp-auth-limit' policy then choose Action "Change". Set "Disabled" to "No" and submit.



              Now go back to http://zimbra.domain.tld:7780/webui/policy-main.php again, select 'smtp-auth-limit' again and choose action "Members".



              Enter the following:



              • Source: $*

              • Destination: any

              • Comment: anything

              Now be careful click on "Back to members" not "Back to policies" or you'll get lost.



              If you were careful, select the line with Source "$*" and choose Action "Change".



              If you were not careful, go back to http://zimbra.domain.tld:7780/webui/policy-main.php choose "smtp-auth-limit" policy, Action "Members", select the line with Source "$*" and choose Action "Change".



              Set "Disabled" to "No" and submit.



              Finally go to http://zimbra.domain.ltd:7780/webui/quotas-main.php and choose Action "Add".
              Enter the following:



              • Name: rate limit smtp auth

              • Track: SASLUsername:username

              • Period: 86400

              • Link to policy: choose 'smtp-auth-limit' from the drop-down menu

              • Verdict: Defer (delay)

              • Data: you talk too fast (this message will be shown to the sender)

              • Stop processing here: yes

              Go back to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select the 'smtp-auth-limit' policy, choose Action "Change".
              Set Disabled to "No" and submit.



              Go back once again to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select 'smtp-auth-limit' policy, choose Action "Limits".



              Select Action "Add" and enter the following, assuming you want to allow each account to send a maximum of 200 msgs every 86400 secs:



              • Type: Message Count

              • Counter Limit: 200

              • Comment: anything

              Now be careful, you know the drill, click on "Back to quota limits" or you'll get lost.
              Select the line with Counter Limit = 200 then choose Action "Change".
              Set Disabled to "No" and submit.






              share|improve this answer

























                0












                0








                0







                First of all note that policyd webui is not password protected unless you take additional measures, i.e. add an .htaccess to that dir and add an AllowOverride AuthConfig to httpd.conf:



                 <Directory /opt/zimbra/common/share/webui>
                AllowOverride AuthConfig
                </Directory>


                Also note that by default policyd is only available on the cleartext web interface of Zimbra, i.e. http://zimbra.domain.tld:7780/webui/index.php



                Take appropriate steps to secure the web interface.



                Go to http://zimbra.domain.tld:7780/webui/policy-main.php and choose 'Add'.
                Enter the following:



                • Name: smtp-auth-limit

                • Priority: 1

                • Description: anything

                Go back to http://zimbra.domain.tld:7780/webui/policy-main.php and select the new 'smtp-auth-limit' policy then choose Action "Change". Set "Disabled" to "No" and submit.



                Now go back to http://zimbra.domain.tld:7780/webui/policy-main.php again, select 'smtp-auth-limit' again and choose action "Members".



                Enter the following:



                • Source: $*

                • Destination: any

                • Comment: anything

                Now be careful click on "Back to members" not "Back to policies" or you'll get lost.



                If you were careful, select the line with Source "$*" and choose Action "Change".



                If you were not careful, go back to http://zimbra.domain.tld:7780/webui/policy-main.php choose "smtp-auth-limit" policy, Action "Members", select the line with Source "$*" and choose Action "Change".



                Set "Disabled" to "No" and submit.



                Finally go to http://zimbra.domain.ltd:7780/webui/quotas-main.php and choose Action "Add".
                Enter the following:



                • Name: rate limit smtp auth

                • Track: SASLUsername:username

                • Period: 86400

                • Link to policy: choose 'smtp-auth-limit' from the drop-down menu

                • Verdict: Defer (delay)

                • Data: you talk too fast (this message will be shown to the sender)

                • Stop processing here: yes

                Go back to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select the 'smtp-auth-limit' policy, choose Action "Change".
                Set Disabled to "No" and submit.



                Go back once again to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select 'smtp-auth-limit' policy, choose Action "Limits".



                Select Action "Add" and enter the following, assuming you want to allow each account to send a maximum of 200 msgs every 86400 secs:



                • Type: Message Count

                • Counter Limit: 200

                • Comment: anything

                Now be careful, you know the drill, click on "Back to quota limits" or you'll get lost.
                Select the line with Counter Limit = 200 then choose Action "Change".
                Set Disabled to "No" and submit.






                share|improve this answer













                First of all note that policyd webui is not password protected unless you take additional measures, i.e. add an .htaccess to that dir and add an AllowOverride AuthConfig to httpd.conf:



                 <Directory /opt/zimbra/common/share/webui>
                AllowOverride AuthConfig
                </Directory>


                Also note that by default policyd is only available on the cleartext web interface of Zimbra, i.e. http://zimbra.domain.tld:7780/webui/index.php



                Take appropriate steps to secure the web interface.



                Go to http://zimbra.domain.tld:7780/webui/policy-main.php and choose 'Add'.
                Enter the following:



                • Name: smtp-auth-limit

                • Priority: 1

                • Description: anything

                Go back to http://zimbra.domain.tld:7780/webui/policy-main.php and select the new 'smtp-auth-limit' policy then choose Action "Change". Set "Disabled" to "No" and submit.



                Now go back to http://zimbra.domain.tld:7780/webui/policy-main.php again, select 'smtp-auth-limit' again and choose action "Members".



                Enter the following:



                • Source: $*

                • Destination: any

                • Comment: anything

                Now be careful click on "Back to members" not "Back to policies" or you'll get lost.



                If you were careful, select the line with Source "$*" and choose Action "Change".



                If you were not careful, go back to http://zimbra.domain.tld:7780/webui/policy-main.php choose "smtp-auth-limit" policy, Action "Members", select the line with Source "$*" and choose Action "Change".



                Set "Disabled" to "No" and submit.



                Finally go to http://zimbra.domain.ltd:7780/webui/quotas-main.php and choose Action "Add".
                Enter the following:



                • Name: rate limit smtp auth

                • Track: SASLUsername:username

                • Period: 86400

                • Link to policy: choose 'smtp-auth-limit' from the drop-down menu

                • Verdict: Defer (delay)

                • Data: you talk too fast (this message will be shown to the sender)

                • Stop processing here: yes

                Go back to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select the 'smtp-auth-limit' policy, choose Action "Change".
                Set Disabled to "No" and submit.



                Go back once again to http://zimbra.domain.ltd:7780/webui/quotas-main.php and select 'smtp-auth-limit' policy, choose Action "Limits".



                Select Action "Add" and enter the following, assuming you want to allow each account to send a maximum of 200 msgs every 86400 secs:



                • Type: Message Count

                • Counter Limit: 200

                • Comment: anything

                Now be careful, you know the drill, click on "Back to quota limits" or you'll get lost.
                Select the line with Counter Limit = 200 then choose Action "Change".
                Set Disabled to "No" and submit.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Oct 8 '18 at 22:36









                Luca GibelliLuca Gibelli

                2,11011423




                2,11011423



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f934570%2fsetup-policyd-on-zimbra-8-8-x-to-rate-limit-the-number-of-messages-each-account%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

                    Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                    Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020