Mercurial > prosody-wiki
changeset 353:2396160dca7c
Fix examples of zone and rate definitions
| author | MWild1@gmail.com |
|---|---|
| date | Thu, 16 May 2013 12:00:24 +0000 |
| parents | 31eb570f6bc0 |
| children | c8aca35f36df |
| files | mod_firewall.wiki |
| diffstat | 1 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/mod_firewall.wiki Mon May 13 20:02:51 2013 +0200 +++ b/mod_firewall.wiki Thu May 16 12:00:24 2013 +0000 @@ -29,7 +29,7 @@ FROM is a condition, and DROP is an action. This is about as simple as it gets. How about heading to the other extreme? Let's demonstrate something more complex that mod_firewall can do for you: {{{ -ZONE myorganisation: staff.myorg.example, support.myorg.example +%ZONE myorganisation: staff.myorg.example, support.myorg.example ENTERING: myorganisation KIND: message @@ -56,7 +56,7 @@ Zones are defined at the top of a script with the following syntax (they are not part of a rule block): {{{ -ZONE myzone: host1, host2, user@host3, foo.bar.example +%ZONE myzone: host1, host2, user@host3, foo.bar.example }}} A host listed in a zone also matches all users on that host (but not subdomains). @@ -168,7 +168,7 @@ First, you must define any rate limits that you are going to use in your script. Here we create a limiter called 'normal' that will allow 2 stanzas per second, and then we define a rule to bounce messages when over this limit. Note that the `RATE` definition is not part of a rule (multiple rules can share the same limiter). {{{ -RATE normal: 2 (burst 3) +%RATE normal: 2 (burst 3) KIND: message LIMIT: normal