From 4e3b33870a02f49506ef78e4937160af3f7fc4a9 Mon Sep 17 00:00:00 2001 From: Matt Simerson Date: Sat, 23 Mar 2013 02:16:49 -0400 Subject: [PATCH] naughty: improve POD --- plugins/naughty | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/plugins/naughty b/plugins/naughty index f8ea233..491bb8a 100644 --- a/plugins/naughty +++ b/plugins/naughty @@ -30,8 +30,8 @@ For efficiency, other plugins should skip processing naughty connections. Plugins like SpamAssassin and DSPAM can benefit from using naughty connections to train their filters. -Since so many connections are from blacklisted IPs, naughty significantly -reduces the resources required to disposing of them. Over 80% of my +Since many connections are from blacklisted IPs, naughty significantly +reduces the resources required to dispose of them. Over 80% of my connections are disposed of after after a few DNS queries (B or one DB query (B) and 0.01s of compute time. @@ -56,7 +56,7 @@ deployment models. When a user authenticates, the naughty flag on their connection is cleared. This is to allow users to send email from IPs that fail connection tests such -as B. Keep in mind that if I is set, connections will +as B. Note that if I is set, connections will not get the chance to authenticate. To allow clients a chance to authenticate, I works well. @@ -86,7 +86,7 @@ Solutions are to make sure B is listed before rcpt_ok in config/plugins or set naughty to run in a phase after the one you wish to complete. In this case, use data instead of rcpt to disconnect after rcpt_ok. The latter is particularly useful if your rcpt plugins skip naughty testing. In that case, -any recipient is accepted for naughty connections, which prevents spammers +any recipient is accepted for naughty connections, which inhibits spammers from detecting address validity. =head2 reject_type [ temp | perm | disconnect ]