| 124,13 → 124,14 |
|---|
| loadplugin line, but fixing it is probably not worth the disruption of |
| existing installations.) |
| |
| If two messages from the same /24 network (or IP address, depending on |
| greylistfourthbyte), with the same sender, with the same list of |
| recipient, and with a score below dontgreylistthreshold are seen at |
| least greylistsecs apart, the triplet will be whitelisted and the |
| GREYLIST_ISWHITE rule will be considered to match thenceforth. That |
| will signal to the local_scan library to raise SAtempreject to let the |
| message through, in addition to the negative spam score it carries. |
| If two messages from the same /24 IPv4 network or /64 IPv6 network (or |
| individual IP address, depending on greylistfourthbyte), with the same |
| sender, with the same list of recipient, and with a score below |
| dontgreylistthreshold are seen at least greylistsecs apart, the |
| triplet will be whitelisted and the GREYLIST_ISWHITE rule will be |
| considered to match thenceforth. That will signal to the local_scan |
| library to raise SAtempreject to let the message through, in addition |
| to the negative spam score it carries. |
| |
| Notice that messages can be permanently rejected (score above |
| SApermreject) and still get a triplet whitelisted if the score is |
| 219,4 → 220,4 |
|---|
| file specifies conflicting options, it will prevent SA-Exim from |
| working. For now, you'll have to make sure that it doesn't. |
| |
| -- Magnus Holmgren <holmgren@debian.org>, Sun, 18 Sep 2011 00:11:18 +0200 |
| -- Magnus Holmgren <holmgren@debian.org>, Fri, 22 Jul 2016 09:58:32 +0200 |