comparison xml/dnsbl.in @ 176:4ec928b24bab stable-6-0-10

allow manual whitelisting with stamp 1 to remove a whitelist entry
author carl
date Sun, 23 Sep 2007 14:33:00 -0700
parents e726e1a61ef9
children d6531c702be3
comparison
equal deleted inserted replaced
175:e726e1a61ef9 176:4ec928b24bab
187 then allow spammers to send mail from B (forged) to B. Such autowhite 187 then allow spammers to send mail from B (forged) to B. Such autowhite
188 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
189 configuration files only need to be readable by the dnsbl user. 189 configuration files only need to be readable by the dnsbl user.
190 </para> 190 </para>
191 <para> 191 <para>
192 You can manually add such an autowhite entry, by appending a single
193 text line to the autowhitelist file, using something like
194 <command>echo "$mail 0" >>$autowhitefile</command>.
195 You can manually remove such an autowhite entry, by appending a single
196 text line to the autowhitelist file, using something like
197 <command>echo "$mail 1" >>$autowhitefile</command>.
198 </para>
199 <para>
192 The DNSBL milter reads a text configuration file (dnsbl.conf) on 200 The DNSBL milter reads a text configuration file (dnsbl.conf) on
193 startup, and whenever the config file (or any of the referenced include 201 startup, and whenever the config file (or any of the referenced include
194 files) is changed. The entire configuration file is case insensitive. 202 files) is changed. The entire configuration file is case insensitive.
195 If the configuration cannot be loaded due to a syntax error, the milter 203 If the configuration cannot be loaded due to a syntax error, the milter
196 will log the error and quit. If the configuration cannot be reloaded 204 will log the error and quit. If the configuration cannot be reloaded