Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
accounting [2013-12-06 11:38] rspencer Fix formatting |
accounting [2013-12-06 11:41] (current) rspencer Punctuation fix. |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| __Policy:__\\ | __Policy:__\\ | ||
| - | Track counters using the policy. All mail hitting this policy will be tracked in a single counter | + | Track counters using the policy. All mail hitting this policy will be tracked in a single counter. |
| - | <code>Policy: Default Outbound Policy</code> | + | |
| + | <code> | ||
| + | Policy: Default Outbound Policy | ||
| + | </code> | ||
| ==== Sender ==== | ==== Sender ==== | ||
| Line 15: | Line 18: | ||
| __Sender: IP:/bitmask__\\ | __Sender: IP:/bitmask__\\ | ||
| Track counters using the sending IP masked with the bitmask provided. For instance if the sender's IP is 192.168.0.10 and the bitmask is /24 then the key in the database will be 192.168.0.0/24 and mail coming from that entire class-c or /24 will be tracked. | Track counters using the sending IP masked with the bitmask provided. For instance if the sender's IP is 192.168.0.10 and the bitmask is /24 then the key in the database will be 192.168.0.0/24 and mail coming from that entire class-c or /24 will be tracked. | ||
| - | (Support for IPv6 is included in r493+, v2.1.x) | + | (Support for IPv6 is included in r493+, v2.1.x). |
| Specifying any IPv6 bitmask, 1-128 will apply the bitmask to the sending server's IP address. A sane value for this is /64. When using accounting on both IPv4 and IPv6, please ensure you use the IPv4 policy member 0.0.0.0/0 (or 0/0) and the IPv6 policy member ::/0 to distinguish between the two so you get the bitmask right. | Specifying any IPv6 bitmask, 1-128 will apply the bitmask to the sending server's IP address. A sane value for this is /64. When using accounting on both IPv4 and IPv6, please ensure you use the IPv4 policy member 0.0.0.0/0 (or 0/0) and the IPv6 policy member ::/0 to distinguish between the two so you get the bitmask right. | ||
| Line 45: | Line 48: | ||
| __AccountingPeriod__\\ | __AccountingPeriod__\\ | ||
| - | Period over which to account traffic [Day(0) , Week(1) or Month(2)] | + | Period over which to account traffic [Day(0) , Week(1) or Month(2)]. |
| __MessageCountLimit__\\ | __MessageCountLimit__\\ | ||
| Line 54: | Line 57: | ||
| __Verdict__\\ | __Verdict__\\ | ||
| - | REJECT, ALLOW, HOLD, DEFER, DISCARD, FILTER or REDIRECT | + | REJECT, ALLOW, HOLD, DEFER, DISCARD, FILTER or REDIRECT. |
| - | __Data__\\ | + | __Data__\\. |
| Text that will be sent along with verdict | Text that will be sent along with verdict | ||
| __LastAccounting__\\ | __LastAccounting__\\ | ||
| - | (present in r348+ and v2.1.x) | + | (Present in r348+ and v2.1.x). |
| The first policy matched will be the only one that gets used, if you have 10 policies ranging from 1 to 10 in priority and you set this to 'yes'(1) for the 5th policy, it will not continue through the rest and add up the accounting records as it normally would do. | The first policy matched will be the only one that gets used, if you have 10 policies ranging from 1 to 10 in priority and you set this to 'yes'(1) for the 5th policy, it will not continue through the rest and add up the accounting records as it normally would do. | ||
| + | |||
| defaults to no(0) | defaults to no(0) | ||