forked from SirWumpus/milter-link
-
Notifications
You must be signed in to change notification settings - Fork 0
/
manual.shtml.in
executable file
·1649 lines (1456 loc) · 62.4 KB
/
manual.shtml.in
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN">
<!-- $OpenBSD$ -->
<html>
<head>
<title>
SnertSoft - @PACKAGE_NAME@/@PACKAGE_VERSION@ for Sendmail
</title>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta name="keywords" content="Sendmail milter URI URL blacklist SURBL URIBL junk mail filter antispam anti spam http mailto" />
<meta name="description" content="Extracts URIs from mail message and checks it against one or more URI blacklists." />
<link rel="stylesheet" type="text/css" href="./style.css" />
<script language="JavaScript" type="text/javascript" src="./mailto.js"></script>
</head>
<body>
<div align="center">
<table cellpadding="0" cellspacing="0" border="0" width="700" style="padding: 0px 10px 0px 10px;">
<tr><td>
<a href="http://www.snertsoft.com/">
<img alt="SnertSoft: We Serve Your Server" src="Img/logo-300x74.png" width="300" height="74" border="0" /></a>
<div align="center">
<h1 class="title">
@PACKAGE_NAME@/@PACKAGE_VERSION@
<br/><span class="large">«Find the myth in link!»</span>
</h1>
<br/>
<a href="#">Description & Usage</a> °
<a href="#Installation">Installation & Notes</a> °
<a href="#License">License & Support</a>
</div>
<a name="Warning"></a>
<h3>WARNING</h3>
<p class="warn">
THIS IS MAIL FILTERING SOFTWARE AND WILL BLOCK MAIL THAT FAILS TO PASS A GIVEN SET OF TESTS.
SNERTSOFT AND THE AUTHOR DO NOT ACCEPT ANY RESPONSIBLITY FOR MAIL REJECTED OR POSSIBLE
LOSS OF BUSINESSS THROUGH THE USE OF THIS SOFTWARE. BY INSTALLING THIS SOFTWARE THE CLIENT
UNDERSTANDS AND ACCEPTS THE RISKS INVOLVED.
</p>
<a name="Description"></a>
<h3>Description</h3>
<p>
This <a href="http://www.sendmail.org/">Sendmail</a> mail filter extracts URIs, such http: and mailto: links,
from within text, HTML, and/or MIME encoded messages, can verify if web page links do not work,
and consult with one or more DNS based black lists, such as
<a href="http://www.surbl.org/">SURBL</a>,
<a href="http://www.uribl.com/">URIBL</a>,
and/or <a href="http://www.spamhaus.org/dbl/">SpamHaus DBL</a>
as to whether the domains have appeared in previous instances of spam.
</p>
<!-- Common Milter Options -->
<a name="Usage"></a>
<h3>Usage</h3>
<blockquote style="text-align: left;">
<nobr><code>@PACKAGE_NAME@</code> <span class="syntax">[options ...][arguments ...]</span></nobr>
</blockquote>
<p>
Options can be expressed in four different ways. Boolean options
are expressed as <span class="syntax">+option</span> or <span class="syntax">-option</span> to turn the option on or off
respectively. Numeric, string, and list options are expressed as
<span class="syntax">option=value</span> to set the option or <span class="syntax">option+=value</span> to append to a
list. Note that the <span class="syntax">+option</span> and <span class="syntax">-option</span> syntax are equivalent to
<span class="syntax">option=1</span> and <span class="syntax">option=0</span> respectively. String values containing white
space must be quoted using single (') or double (") quotes. Option
names are case insensitive.
</p>
<p>
Some options, like <span class="syntax">+help</span> or <span class="syntax">-help</span>, are treated as immediate
actions or commands. Unknown options are ignored and not reported.
The first command-line argument is that which does not adhere to
the above option syntax. The special command-line argument <span class="option">--</span> can
be used to explicitly signal an end to the list of options.
</p>
<p>
The default options, as shown below, can be altered by specifying
them on the command-line or within an option <a href="#opt_file">file</a>, which simply
contains command-line options one or more per line and/or on
multiple lines. Comments are allowed and are denoted by a line
starting with a hash (#) character. If the file option is defined
and not empty, then it is parsed first, followed by the command
line options.
</p>
<p>
Note that there may be additional options that are listed in the option summary
given by <span class="syntax">+help</span> or <span class="syntax">-help</span>
that are not described here.
</p>
<a name="suffix_list"></a>
<h3>Suffix Lists</h3>
<p>
The DNS list options, such as <a href="#opt_domain_bl">domain-bl</a>,
<a href="#opt_mail_bl">mail-bl</a>, and <a href="#opt_uri_bl">uri-bl</a>,
take a suffix list argument, which is semi-colon separated string
of DNS list suffixes with optional <tt>/mask</tt> or <tt>:ip return codes</tt> to
select subsets. In place of a single extremely long string, the
<span class="syntax">option+=value</span> syntax above can be used to build
the list incrementally.
</p>
<p>
Aggregate lists, like URIBL or SURBL, return a single A record, where the IP address is a
bit-vector and the <tt>/mask</tt> selects which bits to act on. The <tt>/mask</tt> is
an unsigned 32-bit number in decimal, octal, or hexadecimal form.
</p>
<p>
Return code lists, like SpamHaus, return multiple A records, where each IP is a return code.
A suffix can be followed by colon (:) and a comma separated list of IP4 return codes. For
example, to select only members of the DBL spam and phish lists
(see <a href="http://www.spamhaus.org/faq/section/Spamhaus%20DBL#291">DBL return codes</a>):</p>
<blockquote><tt>domain-bl=dbl.spamhaus.org:127.0.1.2,127.0.1.3</tt></blockquote>
</p>
<a name="Options"></a>
<h3>Options</h3>
<dl>
<!-- MODIFIED B/W listing options + milter-link-body: tag. -->
<a name="opt_access_check_body"></a>
<dt><span class="syntax">-access-check-body</span></dt>
<dd>
When enabled, this option will perform supplemental
<span class="tag">milter-link-body</span> combo tag lookups
for each URI, IP, domain, or mail address found in the message
body.
This allows special B/W list configurations.
</dd>
<a name="opt_access_check_headers"></a>
<dt><span class="syntax">-access-check-headers</span></dt>
<dd>
When enabled, this option will perform extra access-db lookups
with the Sender, From, To, and Cc headers using
<span class="tag">milter-link-from:</span>,
<span class="tag">milter-link-to:</span>, and combo tags,
as described by <a href="#opt_access_map">access-db</a> option.
This allows special B/W list configurations.
</dd>
<a name="opt_access_db"></a>
<dt><span class="syntax">access-db=</span><span class="param">/etc/mail/access.db</span></dt>
<dd>
The type and location of the read-only access key-value map.
It provides a centralised means to black and white list hosts,
domains, mail addresses, etc. The following methods are supported:
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td width="60%" class="param tline bdotted">text!/path/map.txt</td><td width="40%" class="tline bdotted">R/O text file, memory hash</td></tr>
<tr><td width="60%" class="param bdotted">/path/map.db</td><td width="40%" class="bdotted">Berkeley DB hash format</td></tr>
<tr><td width="60%" class="param bdotted">db!/path/map.db</td><td width="40%" class="bdotted">Berkeley DB hash format</td></tr>
<tr><td width="60%" class="param bdotted">db!btree!/path/map.db</td><td width="40%" class="bdotted">Berkeley DB btree format</td></tr>
<tr><td width="60%" class="param bdotted">sql!/path/database</td><td width="40%" class="bdotted">An SQLite3 database</td></tr>
<tr><td width="60%" class="param bdotted">socketmap!host:port</td><td width="40%" class="bdotted">Sendmail style socket-map</td></tr>
<tr><td width="60%" class="param bdotted">socketmap!/path/local/socket</td><td width="40%" class="bdotted">Sendmail style socket-map</td></tr>
<tr><td width="60%" class="param bdotted">socketmap!123.45.67.89:port</td><td width="40%" class="bdotted">Sendmail style socket-map</td></tr>
<tr><td width="60%" class="param bline">socketmap![2001:0DB8::1234]:port</td><td width="40%" class="bline">Sendmail style socket-map</td></tr>
</table>
</blockquote>
<p>
If :port is omitted, the default is 7953.
</p>
<p>
The access-db contains key-value pairs. Lookups are performed
from most to least specific, stopping on the first entry found.
Keys are case-insensitive.
</p>
<a name="access_lookups"></a>
<p>
There are essentially three types of keys used in the <a href="#opt_access_map">access-db</a>.
Many of the tags available will use one or more of these lookup sequences.
</p>
<dl>
<dt>IP Address Lookups</dt>
<dd>
An IP address lookup is typically applied to the connected SMTP client.
It will start with a complete IPv4 or IPv6 address and break it down
on delimiter boundaries from right to left.
<p>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td rowspan="9" width="6%"> </td><th width="47%">IPv6 Lookup</th><th width="47%">IPv4 Lookup</th></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0:0:0:0:1234:5678</td><td><span class="tag">tag:</span>192.0.2.9</td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0:0:0:0:1234</td><td><span class="tag">tag:</span>192.0.2</td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0:0:0:0</td><td><span class="tag">tag:</span>192.0</td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0:0:0</td><td><span class="tag">tag:</span>192</td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0:0</td><td rowspan="4"> </td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8:0</td></tr>
<tr><td><span class="tag">tag:</span>2001:0DB8</td></tr>
<tr><td><span class="tag">tag:</span>2001</td></tr>
</table>
</p>
<p>
Note that the compact form of an IPv6 address, "<code>2001:0DB8::1234:5678</code>", <em>cannot</em> be used.
Only the full IPv6 address format, with all intervening zeros, is currently supported.
</p>
</dd>
<dt>Domain Name Lookups</dt>
<dd>
A domain lookup may be applied to either the connected SMTP client,
where the client's host name found through a <!-- a class="glossary" href="glossary.html#term_PTR" -->DNS PTR</a> record is searched for, or
using the domain portion of an mail address (see below). A domain lookup will try the IP-domain literal
if applicable, then continue with the <!-- a class="glossary" href="glossary.html#term_FQDN" -->FQDN</a>, breaking it down one label
at a time from left to right.
<p>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td rowspan="6" width="6%"> </td><td><span class="tag">tag:</span>[ipv6:2001:0DB8::1234:5678]</td></tr>
<tr><td><span class="tag">tag:</span>[192.0.2.9]</td></tr>
<tr><td><span class="tag">tag:</span>sub.domain.tld</td></tr>
<tr><td><span class="tag">tag:</span>domain.tld</td></tr>
<tr><td><span class="tag">tag:</span>tld</td></tr>
<tr><td><span class="tag">tag:</span></td></tr>
</table>
</p>
<p>
Note that the bare tag is often used to specify system wide defaults.
</p>
</dd>
<dt>Mail Address Lookups</dt>
<dd>
A mail address lookup is similar to a domain lookup, but the search
first starts with a complete mail address, before trying the address's
domain, and finally only the local part of the address.
<p>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr><td rowspan="6" width="6%"> </td><td><span class="tag">tag:</span>account@sub.domain.tld</td></tr>
<tr><td><span class="tag">tag:</span>sub.domain.tld</td></tr>
<tr><td><span class="tag">tag:</span>domain.tld</td></tr>
<tr><td><span class="tag">tag:</span>tld</td></tr>
<tr><td><span class="tag">tag:</span>account@</td></tr>
<tr><td><span class="tag">tag:</span></td></tr>
</table>
</p>
<p>
Note that the bare tag is often used to specify system wide defaults.
</p>
</dd>
</dl>
<a name="access_tags"></a>
<h4>Tags</h4>
<p>
The following list outlines the available tags and their supported key lookups:
</p>
<dl>
<a name="tag_auth"></a>
<dt><span class="tag">@PACKAGE_NAME@-Auth:</span>auth_authen</dt>
<dt><span class="tag">@PACKAGE_NAME@-Auth:</span></dt>
<dd>
Used to black or white list by authenticated user (SMTP AUTH) as given
by the macro <code>{auth_authen}</code>.
The string searched by the pattern list will be the sender's mail address.
The empty form of <span class="tag">@PACKAGE_NAME@-Auth:</span> allows for a
milter specific default only when <code>{auth_authen}</code> is defined.
</dd>
<a name="tag_body"></a>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>ip<span class="tag">:From:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>domain<span class="tag">:From:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>mail<span class="tag">:From:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>ip<span class="tag">:To:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>domain<span class="tag">:To:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>mail<span class="tag">:To:</span>mail</dt>
<dd>
The above are only applied when <a href="#opt_access_check_body">access-check-body</a> is enabled,
followed by the simple <span class="tag">@PACKAGE_NAME@-Body:</span> tags.
Used to black (REJECT) or ignore (OK) domains that make up
mail addresses or URIs found within the header or body content
of a message in combination with a sender or recipient.
</dd>
<a name="tag_body"></a>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>ip</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>domain</dt>
<dt><span class="tag">@PACKAGE_NAME@-Body:</span>mail</dt>
<dd>
Used to black (REJECT) or ignore (OK) domains that make up
mail addresses or URIs found within the header or body content
of a message.
<p>
This can be used to white list domains that are know to be good and so avoid redundant
lookups. Consider listing your own web site that might appear in your signatures, common and
popular sites like <tt>hotmail.com</tt> or <tt>yahoo.com</tt>, etc.
If black listed, the message will be rejected when found in the message body.
See
<a href="#opt_domain_bl">domain-bl</a>,
<a href="#opt_uri_bl">uri-bl</a>,
<a href="#opt_uri_a_bl">uri-a-bl</a>,
<a href="#opt_uri_ns_bl">uri-ns-bl</a>, and
<a href="#opt_uri_ns_a_bl">uri-ns-a-bl</a>
options.
</p>
</dd>
<a name="tag_connect_from"></a>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>ip<span class="tag">:From:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>domain<span class="tag">:From:</span>mail</dt>
<dd>
This set of combination tags are used to black or white list sender
addresses when sent from a given SMTP client. The
sender address can be easily forged and using the <span class="tag">From:</span>
tag by itself could allow spam with a forged address. By adding the
sender's SMTP client as an extra constraint, it is possible to limit
such abuse.
<span class="note">
Note that the lookup variants with blank IP, domain, or mail are not supported.
</span>
</dd>
<a name="tag_connect"></a>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>ip</dt>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>domain</dt>
<dt><span class="tag">Connect:</span>ip</dt>
<dt><span class="tag">Connect:</span>domain</dt>
<dd>
Used to black or white list an SMTP client.
<span class="note">Note that Sendmail also has special semantics for <span class="tag">Connect:</span>.</span>
</dd>
<a name="tag_connect_to"></a>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>ip<span class="tag">:To:</span>mail</dt>
<dt><span class="tag">@PACKAGE_NAME@-Connect:</span>domain<span class="tag">:To:</span>mail</dt>
<dd>
This set of combination tags are used to black or white list recipient
addresses that a given SMTP client may contact. This allows for
finer granularity of control in place of the <span class="tag">To:</span> tag.
<span class="note">
Note that the lookup variants with blank IP, domain, or mail are not supported.
</span>
</dd>
<a name="tag_from_to"></a>
<dt><span class="tag">@PACKAGE_NAME@-From:</span>mail<span class="tag">:To:</span>mail</dt>
<dd>
This set of combination tags are used to black or white list a pair of sender
and recipient addresses. This allows for finer granularity of control in place
of the <span class="tag">To:</span> tag.
<span class="note">
Note that the lookup variants with blank mail elements are not supported.
</span>
</dd>
<a name="tag_from"></a>
<dt><span class="tag">@PACKAGE_NAME@-From:</span>mail</dt>
<dt><span class="tag">From:</span>mail</dt>
<dd>
Used to black or white list a sender's mail address. Black listing using
this tag is fine, but white listing is <em>not</em> recommended as it is too easy
for someone to fake the sender address or domain.
In the case of a +detailed mail address, the left hand side of the +detail is used for the <i>sender@</i> lookup.
<span class="note">Note that Sendmail also has special semantics for <span class="tag">From:</span>.</span>
</dd>
<a name="tag_helo"></a>
<dt><span class="tag">@PACKAGE_NAME@-Helo:</span>domain</dt>
<dd>
Used to black or white list an SMTP client based on the HELO / EHLO argument.
This tag is not recommended for white listing as the HELO argument can be
too easily falsified.
</dd>
<a name="tag_to"></a>
<dt><span class="tag">@PACKAGE_NAME@-To:</span>mail</dt>
<dt><span class="tag">Spam:</span>mail</dt>
<dt><span class="tag">To:</span>mail</dt>
<dd>
Used to black or white list a recipient's mail address.
In the case of a +detailed mail address, the left hand side of the +detail is used for the <i>sender@</i> lookup.
<span class="note">Note that Sendmail also has special semantics for <span class="tag">To:</span> and <span class="tag">Spam:</span>.</span>
</dd>
</dl>
<a name="access_simple_value"></a>
<h4>Action</h4>
<p>
When a key lookup matches, then the value returned is a pattern list, which in
its simplest and most common form is either an action word like
<code>OK</code>, <code>REJECT</code>, etc.;
a numerical value; or some arbitrary string depending on the tag involved. For example:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr valign="top"><td width="41%" class="key tline bdotted"><span class="tag">Connect:</span>192.168.0</td><td width="59%" class="value tline bdotted">OK</td></tr>
<tr valign="top"><td width="41%" class="key bdotted"><span class="tag">Rate-Connect:</span>fsl.com</td><td width="59%" class="value bdotted">17</td></tr>
<tr valign="top"><td width="41%" class="key bline"><span class="tag">Msg-Limit-From:</span>hotmail.com</td><td width="59%" class="value bline">150/30m</td></tr>
</table>
</blockquote>
<a name="access_action_words"></a>
<p>
The action words supported by @PACKAGE_NAME@ are:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr valign="top"><td width="41%" class="value tline bdotted">OK</td><td width="59%" class="tline bdotted">White list, by-pass one or more tests.</td></tr>
<tr valign="top"><td width="41%" class="value bdotted">REJECT</td><td width="59%" class="bdotted">Black list, reject connection, sender, recipient, etc.</td></tr>
<tr valign="top"><td width="41%" class="value bdotted">SKIP</td><td width="59%" class="bdotted">Stop lookup and return no result ie. continue testing.</td></tr>
<tr valign="top"><td width="41%" class="value bline">DUNNO</td><td width="59%" class="bline">Same as SKIP, commonly used by postfix.</td></tr>
</table>
</blockquote>
<a name="access_pattern_lists"></a>
<h4>Pattern Lists</h4>
<p>
In most instances, the above forms of key lookup and values are sufficient. However,
there may be times when finer granularity of control is required, in which case
pattern lists can be used.
A pattern list is a white space separated list of <i class="syntax">pattern-action</i>
pairs followed by an optional default action. The supported types are:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr valign="top"><td class="value bdotted tline" width="41%">[network/cidr]action</td><td class="bdotted tline">Classless Inter-Domain Routing<br/>(only with IP address lookups)</td></tr>
<tr valign="top"><td class="value bdotted">!pattern!action</td><td class="bdotted">Simple fast text matching. <br/></td></tr>
<tr valign="top"><td class="value bline">/regex/action</td><td class="bline">POSIX Extended Regular Expressions.</td></tr>
</table>
</blockquote>
<a name="access_simple_pattern"></a>
<p>
The simple pattern matching, <span class="value">!pattern!</span>,
uses an asterisk (*) for a wildcard, scanning over zero or more characters;
a question-mark (?) matches any single character; a backslash followed by
any character treats that character as a literal. This method always
tries to match the beginning and end of string. For example:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr valign="top"><td class="value bdotted tline" width="41%">!abc!</td><td class="bdotted tline">exact match for 'abc'</td></tr>
<tr valign="top"><td class="value bdotted">!abc*!</td><td class="bdotted">match 'abc' at start of string</td></tr>
<tr valign="top"><td class="value bdotted">!*abc!</td><td class="bdotted">match 'abc' at the end of string</td></tr>
<tr valign="top"><td class="value bdotted">!abc*def!</td><td class="bdotted">match 'abc' at the start and match 'def' at the end, maybe with stuff in between.</td></tr>
<tr valign="top"><td class="value bline">!*abc*def*!</td><td class="bline">find 'abc', then find 'def'</td></tr>
</table>
</blockquote>
<p>
The following is an example using a simple pattern to reject client connections
that originate from a range of IP addresses of an ISP assigned to ADSL customers.
Using a pattern like this allows you to drop connects from the ISP's ADSL, while still
accepting connections from mail and web servers.
</p>
<blockquote><pre>
<span class="key"><span class="tag">Connect:</span>hananet.net</span> <span class="value">!adsl-*-*.usr.hananet.net!REJECT</span>
</pre></blockquote>
<p>
If you know that an ISP's mail and web servers follow a standard naming convention,
you might prefer to only accept mail from those instead. We include web servers here
to handle the case where a web server might have to send a mail response based on
a form being filled in.
</p>
<blockquote><pre>
<span class="key"><span class="tag">Connect:</span>hananet.net</span> <span class="value">!smtp*.hananet.net!OK !www*.hananet.net!OK REJECT</span>
</pre></blockquote>
<a name="access_about_spf"></a>
<p>
Note that <a class="glossary" href="http://tools.ietf.org/html/rfc4408" target="_blank">SPF</a>
was designed to help mail servers identify
originators of mail, so creating patterns as shown in the above two examples
is not normally required. However, SPF is still considered experimental and not
as widely deployed as one might hope.
</p>
<a name="access_regex_pattern"></a>
<p>
The next example, <span class="value">/regex/</span>, uses Extended Regular Expressions to validate the
format of the local-part of an AOL address, which must be between 3 and 16
characters long, can contain dots and RFC 2822 ``atext'' characters except <code>%</code> and <code>/</code>.
The SKIP word allows the one regular expression to validate the format of the address and continue if the
pattern matches; otherwise if the regular expression failed to match, REJECT the suspect aol.com address.
</p>
<blockquote style="font-family: monospace;">
<span class="key"><span class="tag">From:</span>grandma@aol.com</span> <span class="value">OK</span>
<br/><span class="key"><span class="tag">From:</span>aol.com</span> <span class="value">/^[a-zA-Z0-9!#$&'*+=?^_`{|}~.-]{3,16}@aol.com$/SKIP REJECT</span>
</blockquote>
<p>
The discussion of Extended Regular Expressions is vast and complex, well beyond the
scope of this document. There are many on-line tutorials and references available and the book
<a href="http://www.oreilly.com/catalog/regex3/index.html">Mastering Regular Expressions, 3e</a> from O'Reilly covers the topic in depth.
</p>
<p>
If you need to use a pattern list, then try and follow these suggestions:
</p>
<ul>
<li>
A pattern cannot be used as the key in an <a href="#opt_access_db">access-db</a>
lookup. Key-value tables work with constants for the keys using a predefined lookup order
as outlined <a href="#access_lookups">above</a>.
</li>
<li>Use the key lookup as a selector to find a pattern list.</li>
<li>Use simple <a href="#access_simple_pattern">!pattern!</a> matching where possible, as it will be
faster than Extended Regular Expressions, <a href="#access_regex_pattern">/regex/</a>.
</li>
<li>
Avoid using pattern lists with bare tag variants that specify a global default.
It will more often than not cause a lot of unnecessary attempts to match a pattern.
</li>
<li>
Keep your pattern lists short & simple.
</li>
</ul>
<p>
The <span class="tag">@PACKAGE_NAME@-Connect:</span>, <span class="tag">@PACKAGE_NAME@-From:</span>, and
<span class="tag">@PACKAGE_NAME@-To:</span> tags provide a milter specific means to override
the Sendmail and Postfix variants. For example, you normally white list your local network through any and all milters, but
on the odd occasion you might want to actually scan mail from inside going out, without removing the Connect: tag that
allows Sendmail or Postfix to relay for your network or white listing for other milters.
So for example if you have tags like:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td width="65%" class="key"><span class="tag">To:</span>mx.example.com</td><td width="35%" class="value">RELAY</td>
</tr>
</table>
</blockquote>
<p>
You might have to add milter specific overrides in order to make sure the
mail still gets filtered:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr class="syntax">
<td width="65%" class="key"><span class="tag">To:</span>mx.example.com</td><td width="35%" class="value">RELAY</td>
</tr>
<tr class="syntax">
<td class="key"><span class="tag">@PACKAGE_NAME@-To:</span>mx.example.com</td><td class="value">SKIP</td>
</tr>
</table>
</blockquote>
<p>
Some additional examples:
</p>
<blockquote>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr class="syntax" valign="top">
<td width="40%" class="tline key"><span class="tag">@PACKAGE_NAME@-Connect:</span>80.94</td>
<td width="60%" class="tline value" style="text-align: right;">[80.94.96.0/20]OK REJECT</td>
</tr>
<tr class="normal">
<td colspan="2">
<br/>
Accept connections from the netblock 80.94.96.0/20 (80.94.96.0 through to 80.94.111.255) and
rejecting anything else in 80.94.0.0/16.
<br/><br/>
</td>
</tr>
<tr class="syntax" valign="top">
<td width="40%" class="tline key"><span class="tag">@PACKAGE_NAME@-Connect:</span>192.0.2</td>
<td width="60%" class="tline value" style="text-align: right;">/^192\.0\.2\.8[0-9]/OK REJECT</td>
</tr>
<tr class="normal">
<td colspan="2">
<br/>
Accept connections from 192.0.2.80 through to 192.0.2.89, reject everything else in 192.0.2.0/24.
<br/><br/>
</td>
</tr>
<tr class="syntax" valign="top">
<td width="40%" class="tline key"><span class="tag">@PACKAGE_NAME@-From:</span>example.com</td>
<td width="60%" class="tline value" style="text-align: right;">/^john@.+/OK /^fred\+.*@.*/OK REJECT</td>
</tr>
<tr class="normal">
<td colspan="2">
<br/>
Accept mail from <john@example.com> and <fred@example.com> when fred's address
contains a plus-detail in the address. Reject everything else from example.com.
<br/><br/>
</td>
</tr>
<tr class="syntax" valign="top">
<td width="40%" class="tline key"><span class="tag">@PACKAGE_NAME@-To:</span>example.net</td>
<td width="60%" class="tline value" style="text-align: right;">!*+*@*!REJECT !*.smith@*!REJECT /^[0-9].*/REJECT</td>
</tr>
<tr class="normal">
<td colspan="2" class="bline">
<br/>
Reject mail to example.net using a plus-detail address or to any user who's last name is "smith" or addresses
starting with a digit. No default given, so it is assumed to be SKIP.
<br/><br/>
</td>
</tr>
</table>
</blockquote>
</dd>
<!-- end MODIFIED B/W listing options + milter-link-body: tag. -->
<a name="opt_daemon"></a>
<dt><span class="syntax">+daemon</span></dt>
<dd>Start as a background daemon or foreground application.
</dd>
<a name="opt_date_policy"></a>
<dt><span class="syntax">date-policy=</span><span class="param">reject</span></dt>
<dd>
If the date-required check fails,
then apply one of the following policies:
<blockquote>
<table border="0" cellspacing="0" cellpadding="3" width="100%">
<tr valign="top" align="justify">
<td class="tline bline param" width="40%"> none</td>
<td class="tline bline" width="60%">Do nothing.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> tag</td>
<td class="bline">Tag the message subject. See <a href="#opt_subject_tag">subject-tag</a>.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> quarantine</td>
<td class="bline">Quarantine the message. See sendmail's queue management options -qQ and -Q.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> reject</td>
<td class="bline">Reject the message.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> discard</td>
<td class="bline">Discard the message.</td>
</tr>
</table>
</blockquote>
</dd>
<a name="opt_date_required"></a>
<dt><span class="syntax">date-required=</span><span class="param">0</span></dt>
<dd>
Set to one (1) to require a Date header; two (2) requires the header
and that it conform to the RFC 5322 date-time format. Zero (0) disables
the requirement (default).
</dd>
<a name="opt_dns_list_log_file"></a>
<dt><span class="syntax">dns-list-log-file=</span><span class="param"></span></dt>
<dd>
File name used to log DNS list lookup results separate from syslog.
Intended for debugging only.
</dd>
<a name="opt_dns_list_log_what"></a>
<dt><span class="syntax">dns-list-log-what=</span><span class="param"></span></dt>
<dd>
What DNS list lookup results to log. 1 for successful lookups, 2 for
unsuccessful lookups, 3 for both.
</dd>
<a name="opt_dns_max_timeout"></a>
<dt><span class="syntax">dns-max-timeout=</span><span class="param">45</span></dt>
<dd>
Maximum timeout in seconds for a DNS query.
</dd>
<a name="opt_dns_round_robin"></a>
<dt>-<span class="syntax">dns-round-robin</span><span class="param"></span></dt>
<dd>
Set true to query NS servers in round robin order. Set false to
query all the NS servers in parallel.
</dd>
<a name="opt_domain_bl"></a>
<dt><span class="syntax">domain-bl=</span><span class="param">.dbl.spamhaus.org</span></dt>
<dd>
Specify a <a href="#suffix_list">suffix list</a>.
The host or domain name found in a URI is checked against these DNS black
lists. These black lists are assumed to use wildcards entries, so only a
single lookup is done. IP-as-domain in a URI are ignored. See also
<a href="#opt_uri_bl_policy">uri-bl-policy</a>.
</dd>
<a name="opt_file"></a>
<dt><span class="syntax">file=</span><span class="param">/etc/mail/@PACKAGE_NAME@.cf</span></dt>
<dd>Read the option file before command line options. This option is set by default.
To disable the use of an option file, simply say <span class="syntax">file=''</span>
</dd>
<a name="opt_help"></a>
<dt>±<span class="syntax">help</span></dt>
<dd>Write the option summary to standard output and exit.
The output is suitable for use as an option file.
Note that this option may list additional undocumented options.
</dd>
<a name="opt_info"></a>
<dt>±<span class="syntax">info</span></dt>
<dd>
Write the configuration and compile time options to standard output
and exit.
</dd>
<a name="opt_mail_bl"></a>
<dt><span class="syntax">mail-bl=</span><span class="param"></span></dt>
<dd>
Specify a <a href="#suffix_list">suffix list</a>
with mail address black list suffixes to consult. The <code>MAIL FROM:</code>
address and mail addresses found in select headers and the message are MD5
hashed, which are then checked against these black lists.
</dd>
<a name="opt_mail_bl_domains"></a>
<dt><span class="syntax">mail-bl-domains</span>=<span class="param">gmail.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">googlemail.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">hotmail.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">yahoo.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">aol.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">aim.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">live.*</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">ymail.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">rocketmail.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">centrum.cz</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">centrum.sk</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">inmail24.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">libero.it</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">mail2world.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">msn.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">she.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">shuf.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">sify.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">terra.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">tiscali.it</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">virgilio.it</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">voila.fr</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">walla.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">y7mail.com</span></dt>
<dt><span class="syntax">mail-bl-domains</span>+=<span class="param">yeah.net</span></dt>
<dd>
A list of domain glob-like patterns for which to test against mail-bl,
typically free mail services. This reduces the load on public BLs.
Specify * to test all domains, empty list to disable.
</dd>
<a name="opt_mail_bl_headers"></a>
<dt><span class="syntax">mail-bl-headers=</span><span class="param">From;Reply-To</span></dt>
<dd>
A list of mail headers to parse for mail addresses and check against
one or more MAIL BL. Specify the empty list to disable.
</dd>
<a name="opt_mail_bl_max"></a>
<dt><span class="syntax">mail-bl-max=</span><span class="param">10</span></dt>
<dd>
Maximum number of unique mail addresses to check. Specify zero for
unlimited.
</dd>
<a name="opt_mail_bl_policy"></a>
<dt><span class="syntax">mail-bl-policy=</span><span class="param">reject</span></dt>
<dd>
If the message contains a black listed mail address found by
mail-bl, then apply one of the following policies:
<blockquote>
<table border="0" cellspacing="0" cellpadding="3" width="100%">
<tr valign="top" align="justify">
<td class="tline bline param" width="40%"> none</td>
<td class="tline bline" width="60%">Do nothing.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> tag</td>
<td class="bline">Tag the message subject. See <a href="#opt_subject_tag">subject-tag</a>.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> quarantine</td>
<td class="bline">Quarantine the message. See sendmail's queue management options -qQ and -Q.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> reject</td>
<td class="bline">Reject the message.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> discard</td>
<td class="bline">Discard the message.</td>
</tr>
</table>
</blockquote>
</dd>
<a name="opt_milter_socket"></a>
<dt><span class="syntax">milter-socket=</span><span class="param">unix:@snert_socket_file@</span></dt>
<dd>A socket specifier used to communicate between Sendmail and <code>@PACKAGE_NAME@</code>.
Typically a unix named socket or a host:port. This value must match the value specified for
the INPUT_MAIL_FILTER() macro in the sendmail.mc file. The accepted syntax is:
<blockquote>
<dl>
<dt><code>{unix|local}:/path/to/file</code></dt><dd>A named pipe. (default)</dd>
<dt><code>inet:port@{hostname|ip-address}</code></dt><dd>An IPV4 socket.</dd>
<dt><code>inet6:port@{hostname|ip-address}</code></dt><dd>An IPV6 socket.</dd>
</dl>
</blockquote>
</dd>
<a name="opt_milter_timeout"></a>
<dt><span class="syntax">milter-timeout=</span><span class="param">7210</span></dt>
<dd>The sendmail/milter I/O timeout in seconds.</dd>
<a name="opt_links_policy"></a>
<dt><span class="syntax">links-policy=</span><span class="param">tag</span></dt>
<dd>If <a href="#opt_links_test">+links-test</a> finds a broken URL, then apply one of the following policies:
<blockquote>
<table border="0" cellspacing="0" cellpadding="3" width="100%">
<tr valign="top" align="justify">
<td class="tline bline param" width="40%"> none</td>
<td class="tline bline" width="60%">Do nothing.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> tag</td>
<td class="bline">Tag the message subject. See <a href="#opt_subject_tag">subject-tag</a>.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> quarantine</td>
<td class="bline">Quarantine the message. See sendmail's queue management options -qQ and -Q.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> reject</td>
<td class="bline">Reject the message.</td>
</tr>
<tr valign="top" align="justify">
<td class="bline param"> discard</td>
<td class="bline">Discard the message.</td>
</tr>
</table>
</blockquote>
</dd>
<a name="opt_links_test"></a>
<dt><span class="syntax">-links-test</span></dt>
<dd>
Verify each HTTP link in the message body is valid (not broken) and find their corresponding
origin server by following all redirections (not circular). If any link is invalid for any
reason then apply the policy given by <a href="#opt_links_policy">links-policy</a>.
</dd>
<a name="opt_links_timeout"></a>
<dt><span class="syntax">links-timeout=</span><span class="param">60</span></dt>
<dd>Socket timeout used when testing HTTP links, see <a href="#opt_links_test">+links-test</a>.
</dd>
<a name="opt_pid_file"></a>
<dt><span class="syntax">pid-file=</span><span class="param">/var/run/milter/@PACKAGE_NAME@.pid</span></dt>
<dd>The file path of where to save the process-id.
</dd>
<a name="opt_port_list"></a>
<dt><span class="syntax">port-list=</span><span class="param"></span></dt>
<dd>
A list of port numbers corresponding to protocols to test. Some sites
prefer to focus on web and/or email related URI. This option provides
a means to restrict the scope of testing to a specific subset of URI
by port number. An empty list means all URI are tested.
</dd>
<a name="opt_quit"></a>
<dt>±<span class="syntax">quit</span> or <span class="syntax">+quit</span></dt>
<dd>Quit an already running instance of the milter and exit.
This is equivalent to: <nobr><code>kill -QUIT `cat /var/run/milter/@PACKAGE_NAME@.pid`</code></nobr>
</dd>
<a name="opt_restart"></a>
<dt>±<span class="syntax">restart</span> or <span class="syntax">+restart</span></dt>
<dd>Terminate an already running instance of the milter before starting.
</dd>
<a name="opt_run_group"></a>
<dt><span class="syntax">run-group=</span><span class="param">milter</span></dt>
<dd>The process runtime group name to be used when started by root.</dd>
<a name="opt_run_user"></a>
<dt><span class="syntax">run-user=</span><span class="param">milter</span></dt>
<dd>The process runtime user name to be used when started by root.</dd>
<a name="opt_smtp_auth_ok"></a>
<dt><span class="syntax">-smtp-auth-ok</span></dt>
<dd>Allow SMTP authenticated senders to send unscanned mail. See also the
<code>@PACKAGE_NAME@-auth:</code> tag (<a href="#opt_access_db">access-db=</a>)
for finer granularity of control.
</dd>
<a name="opt_subject_tag"></a>
<dt><span class="syntax">subject-tag=</span><span class="param">[SPAM]</span></dt>
<dd>Subject tag prefix for invalid messages. To disable the subject tag specify:
<nobr><span class="syntax">subject-tag=''</span></nobr>.
See also
<a href="#opt_uri_bl_policy">uri-bl-policy</a> and
<a href="#opt_links_policy">links-policy</a>.
</dd>
<!--
<a name="opt_text_vs_inline"></a>
<dt><span class="syntax">-text-vs-inline</span></dt>
<dd>
In a multipart/alternative message, there is typically a basic text/plain representation of any
rich text alternative, such as text/html. One common spam technique, a favourite of pump & dump stock scams,
is to embed inline content, such as images containing a textual message, into a text/html message and leave
the text/plain part empty. This option will detect and apply the policy given by <a href="#opt_policy">policy=</a>.
</dd>
-->
<a name="opt_uri_a_bl"></a>
<dt><span class="syntax">uri-a-bl=</span><span class="param"></span></dt>
<dd>
Specify a <a href="#suffix_list">suffix list</a>
of IP black list suffixes to consult, like <code>.zen.spamhaus.org</code>
The host or domain name found in a URI is used to find its DNS A record
and IP address, which is then checked against these IP DNS black lists.
</dd>
<a name="opt_uri_bl"></a>
<dt><span class="syntax">uri-bl=</span><span class="param">.multi.surbl.org</span></dt>
<dt><span class="syntax">uri-bl+=</span><span class="param">.black.uribl.com</span></dt>
<dd>
Specify a <a href="#suffix_list">suffix list</a>
of domain name black list suffixes to consult, like <code>.multi.surbl.org</code>.
The domain name found in a URI is checked against these DNS black lists.
</dd>
<a name="opt_uri_bl_helo"></a>
<dt><span class="syntax">uri-bl-headers=</span><span class="param">X-Originating-IP</span></dt>
<dd>
A list of mail headers to parse for URI and check using the
<a href="#opt_domain_bl">domain-bl</a>,
<a href="#opt_uri_bl">uri-bl</a>,
<a href="#opt_uri_a_bl">uri-a-bl</a>,
<a href="#opt_uri_ns_bl">uri-ns-bl</a>, and
<a href="#opt_uri_ns_a_bl">uri-ns-a-bl</a>
options.
Specify the empty list to disable.
</dd>
<a name="opt_uri_bl_helo"></a>
<dt><span class="syntax">-uri-bl-helo</span></dt>
<dd>
Test the HELO/EHLO argument using the
<a href="#opt_domain_bl">domain-bl</a>,
<a href="#opt_uri_bl">uri-bl</a>,
<a href="#opt_uri_a_bl">uri-a-bl</a>,
<a href="#opt_uri_ns_bl">uri-ns-bl</a>, and
<a href="#opt_uri_ns_a_bl">uri-ns-a-bl</a>
options. Reject the command if black listed.
</dd>
<a name="opt_uri_bl_policy"></a>
<dt><span class="syntax">uri-bl-policy=</span><span class="param">reject</span></dt>
<dd>