Mercurial > dnsbl
comparison xml/dnsbl.in @ 162:c4bce911c276 stable-6-03
don't add auto whitelist for A to A
author | carl |
---|---|
date | Sat, 14 Jul 2007 12:25:17 -0700 |
parents | d384df37491f |
children | 97d7da45fe2a |
comparison
equal
deleted
inserted
replaced
161:d384df37491f | 162:c4bce911c276 |
---|---|
174 This milter can also impose hourly rate limits on the number of | 174 This milter can also impose hourly rate limits on the number of |
175 recipients accepted from SMTP AUTH connections, that would otherwise be | 175 recipients accepted from SMTP AUTH connections, that would otherwise be |
176 allowed to relay thru this mail server with no spam filtering. | 176 allowed to relay thru this mail server with no spam filtering. |
177 </para> | 177 </para> |
178 <para> | 178 <para> |
179 Consider the case of a message from A to B passing thru this milter. | 179 Consider the case of a message from A to B passing thru this milter. If |
180 If that message is not blocked, then we might eventually see a reply | 180 that message is not blocked, then we might eventually see a reply |
181 message from B to A. If the filtering context for A includes an | 181 message from B to A. If the filtering context for A includes an |
182 autowhite entry, then this milter will add an entry in that file to | 182 autowhite entry, and that context does <emphasis>not</emphasis> cover B |
183 whitelist such replies for a configurable time period. Such autowhite | 183 as a recipient, then this milter will add an entry in that file to |
184 whitelist such replies for a configurable time period. Suppose A and B | |
185 are in the same domain, or at least use the same filtering context. In | |
186 that case we don't want to add a whitelist entry for B, since that would | |
187 then allow spammers to send mail from B (forged) to B. Such autowhite | |
184 files need to be writeable by the dnsbl user, where all the other dnsbl | 188 files need to be writeable by the dnsbl user, where all the other dnsbl |
185 configuration files only need to be readable by the dnsbl user. | 189 configuration files only need to be readable by the dnsbl user. |
186 </para> | 190 </para> |
187 <para> | 191 <para> |
188 The DNSBL milter reads a text configuration file (dnsbl.conf) on | 192 The DNSBL milter reads a text configuration file (dnsbl.conf) on |