1July 25, 2001() July 25, 2001()
2
3
4
6 spamass-milter - sendmail milter for passing emails through SpamAssas‐
7 sin
8
10 spamass-milter -p socket [-b|-B spamaddress] [-d debugflags] [-D host]
11 [-e defaultdomain] [-f] [-i networks] [-m] [-M] [-P pidfile] [-r nn]
12 [-u defaultuser] [-x] [-- spamc flags ...]
13
15 The spamass-milter utility is a sendmail milter that checks and modi‐
16 fies incoming email messages with SpamAssassin.
17
18 The following options are available:
19
20 -p socket
21 Specifies the pathname of a socket to create for communication
22 with sendmail. If it is removed, sendmail will not be able to
23 access the milter. This may cause messages to bounce, queue, or
24 be passed through unmiltered, depending on the parameters in
25 sendmail's .cf file.
26
27 -b spamaddress
28 Redirects tagged spam to the specified email address. All enve‐
29 lope recipients are removed, and inserted into the message as
30 `X-Spam-Orig-To:' headers.
31
32 -B spamaddress
33 Same as -b, except the original recipients are retained. Only
34 one of -b and -B may be used.
35
36 -d debugflags
37 Enables logging. debugflags is a comma-separated list of
38 tokens:
39
40 func Entry and exit of internal functions.
41
42 misc Other non-verbose logging.
43
44 net Lookups of the ignored netblocks list.
45
46 poll Low-level I/O to the child spamc process.
47
48 rcpt Recipient processing.
49
50 spamc High-level I/O to the child spamc process.
51
52 str Calls to field lookup and string comparison functions.
53
54 uori Calls to the update_or_insert function.
55
56 1 (historical) Same as func,misc.
57
58 2 (historical) Same as func,misc,poll.
59
60 3 (historical) Same as func,misc,poll,str,uori.
61
62 -D host
63 Connects to a remote spamd server on host, instead of using one
64 on localhost. This option is deprecated; use -- -d host
65 instead.
66
67 -e defaultdomain
68 Pass the full user@domain address to spamc. The default is to
69 pass only the username part on the assumption that all users are
70 local. This flag is useful if you are using an SQL (or other
71 username) backend with spamassassin and have listed the full
72 address there. If the recipient name has no domain part (if the
73 recipient is on the local machine for example), defaultdomain is
74 added. Requires the -u flag.
75
76 -f Causes spamass-milter to fork into the background.
77
78 -i networks
79 Ignores messages if the originating IP is in the network(s)
80 listed. The message will be passed through without calling Spa‐
81 mAssassin at all. networks is a comma-separated list, where
82 each element can be either an IP address (nnn.nnn.nnn.nnn), a
83 CIDR network (nnn.nnn.nnn.nnn/nn), or a network/netmask pair
84 (nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn). Multiple -i flags will
85 append to the list. For example, if you list all your internal
86 networks, no outgoing emails will be filtered.
87
88 -m Disables modification of the `Subject:' and `Content-Type:'
89 headers and message body. This is useful when SpamAssassin is
90 configured with `"defang_mime' 0" and `"report_header' 1" , or
91 when SA is simply used to add headers for postprocessing later.
92 Updating the body through the milter interface can be slow for
93 large messages.
94
95 -M Like -m, but also disables creation of any SpamAssassin `X-
96 Spam-*' headers as well. Both tagged and untagged mail gets
97 passed through unchanged. To be useful, this option should be
98 used with the -r, -b, or -B flags. If -b is used, the `X-Spam-
99 Orig-To:' headers will still be added.
100
101 -P pidfile
102 Create the file pidfile, containing the processid of the milter.
103
104 -r nn Reject scanned email if it greater than or equal to nn. If -1,
105 reject scanned email if SpamAssassin tags it as spam (useful if
106 you are also using the -u flag, and users have changed their
107 required_hits value).
108
109 For example, if you usually use procmail to redirect tagged
110 email into a separate folder just in case of false positives,
111 you can use -r 15 and reject flagrant spam outright while still
112 receiving low-scoring messages.
113
114 -u defaultuser
115 Pass the username part of the first recipient to spamc with the
116 -u flag. This allows user preferences files to be used. If the
117 message is addressed to multiple recipients, the username
118 defaultuser is passed instead.
119
120 Note that spamass-milter does not know whether an email is
121 incoming or outgoing, so a message from <user1@localdomain.com>
122 to <user2@yahoo.com> will make spamass-milter pass -u user2 to
123 spamc.
124
125 -x Pass the recipient address through sendmail -bv, which will per‐
126 form virtusertable and alias expansion. The resulting username
127 is then passed to spamc. Requires the -u flag.
128
129 -- spamc flags ...
130 Pass all remaining options to spamc. This allows you to connect
131 to a remote spamd with -d or -p.
132
134 /usr/bin/spamc
135 client interface to SpamAssassin
136
138 spamassassin(1), spamd(1)
139
141 "Georg C. F. Greve" <greve@gnu.org>
142
143 "Dan Nelson" <dnelson@allantgroup.com>
144
145
146
147 July 25, 2001()