Mercurial > dnsbl

comparison xml/dnsbl.in @ 6:cea50d98a6cf

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
start work on content url scanner
author carl
date Wed, 21 Apr 2004 22:39:46 -0700
parents 793ac9cc114d
children 2c206836b4cc
comparison
equal deleted inserted replaced
5:793ac9cc114d 6:cea50d98a6cf
16 mail server can use the correct set of DNSBLs for each message. As a 16 mail server can use the correct set of DNSBLs for each message. As a
17 side-effect, it gives us the ability to customize the set of DNSBLs on a 17 side-effect, it gives us the ability to customize the set of DNSBLs on a
18 per-recipient basis, so that fred@example.com could use SPEWS and the 18 per-recipient basis, so that fred@example.com could use SPEWS and the
19 SBL, where all other users @example.com use only the SBL. 19 SBL, where all other users @example.com use only the SBL.
20 20
21 <p>The DNSBL milter reads a text configuration file on startup, and 21 <p>The DNSBL milter reads a text configuration file (dnsbl.conf) on
22 whenever the config file (or any of the referenced include files) is 22 startup, and whenever the config file (or any of the referenced include
23 changed. The entire configuration file is case insensitive. 23 files) is changed. The entire configuration file is case insensitive.
24 24
25 <p>If you are also using the <a 25 <p>If you are also using the <a
26 href="http://www.rhyolite.com/anti-spam/dcc/">DCC</a> milter, there are 26 href="http://www.rhyolite.com/anti-spam/dcc/">DCC</a> milter, there are
27 a few considerations. You may need to whitelist senders from the DCC 27 a few considerations. You may need to whitelist senders from the DCC
28 bulk detector, or from the DNS based lists. Those are two very 28 bulk detector, or from the DNS based lists. Those are two very
46 point for white/blacklisting. 46 point for white/blacklisting.
47 47
48 <p>Consider the case where you have multiple clients, each with their 48 <p>Consider the case where you have multiple clients, each with their
49 own mail servers, and each running their own DCC milters. Each client 49 own mail servers, and each running their own DCC milters. Each client
50 is using the DCC facilities for envelope from/to white/blacklisting. 50 is using the DCC facilities for envelope from/to white/blacklisting.
51 Presumably you can use rsync or scp to fetch copies of these clients DCC 51 Presumably you can use rsync or scp to fetch copies of your clients DCC
52 whiteclnt files on a regular basis. Your mail server, acting as a 52 whiteclnt files on a regular basis. Your mail server, acting as a
53 backup MX for your clients, can use the DNSBL milter, and include those 53 backup MX for your clients, can use the DNSBL milter, and include those
54 client DCC config files. The envelope to white/blacklisting will be 54 client DCC config files. The envelope to white/blacklisting will be
55 global for your system, but the envelope from white/blacklisting will be 55 global for your system, but the envelope from white/blacklisting will be
56 appropriately tagged and used only for the domains controlled by each of 56 appropriately tagged and used only for the domains controlled by each of
122 INPUT_MAIL_FILTER(`dnsbl', `S=local:/var/run/dnsbl/dnsbl.sock, F=T, T=S:30s;R:30s;E:30s') 122 INPUT_MAIL_FILTER(`dnsbl', `S=local:/var/run/dnsbl/dnsbl.sock, F=T, T=S:30s;R:30s;E:30s')
123 </pre> 123 </pre>
124 124
125 Read the sample <a 125 Read the sample <a
126 href="http://www.five-ten-sg.com/dnsbl.conf">var/dnsbl/dnsbl.conf</a> 126 href="http://www.five-ten-sg.com/dnsbl.conf">var/dnsbl/dnsbl.conf</a>
127 file and modify it to fit your configuration. 127 file and modify it to fit your configuration. You can test your
128 configuration files, and see a readable internal dump of them on stderr
129 with
130
131 <pre>
132 cd /var/dnsbl
133 ./dnsbl -c
134 </pre>
135
136 <pre>
128 137
129 138
130 <pre> 139
131 $Id$ 140 $Id$
132 </pre> 141 </pre>
133 </body> 142 </body>
134 </html> 143 </html>