rev |
line source |
meillo@134
|
1 .TH masqmail.conf 5 2010-07-06 masqmail-0.2.25 "File Formats"
|
meillo@34
|
2
|
meillo@0
|
3 .SH NAME
|
meillo@0
|
4 masqmail.conf \- masqmail configuration file
|
meillo@34
|
5
|
meillo@34
|
6
|
meillo@0
|
7 .SH DESCRIPTION
|
meillo@0
|
8
|
meillo@34
|
9 This man page describes the syntax of the main configuration file of masqmail.
|
meillo@34
|
10 Its usual location is \fI/etc/masqmail/masqmail.conf\fR
|
meillo@0
|
11
|
meillo@0
|
12 The configuration consists of lines of the form
|
meillo@0
|
13
|
meillo@34
|
14 \fBval\fR = \fIexpression\fR
|
meillo@0
|
15
|
meillo@34
|
16 Where \fBval\fR is a variable name and \fIexpression\fR a string,
|
meillo@34
|
17 which can be quoted with double quotes `"'.
|
meillo@34
|
18 If the expression is on multiple lines or contains characters other than letters,
|
meillo@174
|
19 digits or the characters `.', `-', `_', `/', ';', '@', ':', it must be quoted.
|
meillo@34
|
20 You can use quotes inside quotes by escaping them with a backslash.
|
meillo@0
|
21
|
meillo@174
|
22 Each \fBval\fP has a type, which can be boolean, numeric, string or list.
|
meillo@34
|
23 A boolean variable can be set with one of the values `on', `yes', and `true' or `off', `no' and `false'.
|
meillo@34
|
24 List items are separated with semicolons `;'.
|
meillo@174
|
25 For some values, patterns (like `*',`?') can be used.
|
meillo@174
|
26 The spaces in front of and after the equal sign `=' are optional.
|
meillo@0
|
27
|
meillo@34
|
28 Most lists (exceptions: \fBlocal_hosts\fR, \fBlocal_nets\fR, \fBlisten_addresses\fR,
|
meillo@139
|
29 \fBonline_routes\fR, and \fBonline_gets\fR) accept files.
|
meillo@34
|
30 These will be recognized by a leading slash `/'.
|
meillo@34
|
31 The contents of these files will be included at the position of the file name,
|
meillo@34
|
32 there can be items or other files before and after the file entry.
|
meillo@174
|
33 The format of the files is different though, within these files each entry is on another line
|
meillo@174
|
34 and the entries are not separated by semicolons.
|
meillo@34
|
35 This makes it easy to include large lists which are common in different configuration files,
|
meillo@34
|
36 so they do not have to appear in every configuration file.
|
meillo@0
|
37
|
meillo@34
|
38 Blank lines and lines starting with a hash `#' are ignored.
|
meillo@34
|
39
|
meillo@0
|
40
|
meillo@0
|
41 .SH OPTIONS
|
meillo@34
|
42
|
meillo@0
|
43 .TP
|
meillo@34
|
44 \fBrun_as_user = \fIboolean\fR
|
meillo@0
|
45
|
meillo@34
|
46 If this is set, masqmail runs with the user id of the user who invoked it and never changes it.
|
meillo@34
|
47 This is for debugging purposes only.
|
meillo@34
|
48 If the user is not root, masqmail will not be able to listen on a port < 1024
|
meillo@34
|
49 and will not be able to deliver local mail to others than the user.
|
meillo@0
|
50
|
meillo@0
|
51 .TP
|
meillo@34
|
52 \fBuse_syslog = \fIboolean\fR
|
meillo@0
|
53
|
meillo@34
|
54 If this is set, masqmail uses syslogd for logging.
|
meillo@34
|
55 It uses facility MAIL.
|
meillo@34
|
56 You still have to set \fBlog_dir\fR for debug files.
|
meillo@0
|
57
|
meillo@0
|
58 .TP
|
meillo@34
|
59 \fBdebug_level = \fIn\fR
|
meillo@0
|
60
|
meillo@34
|
61 Set the debug level.
|
meillo@34
|
62 Valid values are 0 to 6, increasing it further makes no difference.
|
meillo@34
|
63 Be careful if you set this as high as 5 or higher, the logs may very soon fill your hard drive.
|
meillo@0
|
64
|
meillo@0
|
65 .TP
|
meillo@44
|
66 \fBlog_dir = \fIfile\fR
|
meillo@44
|
67
|
meillo@174
|
68 The directory where logs are stored, if syslog is not used.
|
meillo@174
|
69 Debug files are always stored in this directory if debugging is enabled.
|
meillo@44
|
70 \fI/var/log/masqmail\fR is a common value.
|
meillo@44
|
71 \fIfile\fR must be an absolute path.
|
meillo@44
|
72
|
meillo@44
|
73 .TP
|
meillo@34
|
74 \fBmail_dir = \fIfile\fR
|
meillo@0
|
75
|
meillo@34
|
76 The directory where local mail is stored, usually \fI/var/spool/mail\fR or \fI/var/mail\fR.
|
meillo@44
|
77 \fIfile\fR must be an absolute path.
|
meillo@0
|
78
|
meillo@0
|
79 .TP
|
meillo@34
|
80 \fBspool_dir = \fIfile\fR
|
meillo@0
|
81
|
meillo@34
|
82 The directory where masqmail stores its spool files (and later also other stuff).
|
meillo@34
|
83 It must have a subdirectory \fIinput\fR.
|
meillo@34
|
84 Masqmail needs read and write permissions for this directory.
|
meillo@34
|
85 I suggest to use \fI/var/spool/masqmail\fR.
|
meillo@44
|
86 \fIfile\fR must be an absolute path.
|
meillo@0
|
87
|
meillo@0
|
88 .TP
|
meillo@133
|
89 \fBlock_dir = \fIfile\fR
|
meillo@133
|
90
|
meillo@133
|
91 The directory where masqmail stores its lock files.
|
meillo@133
|
92 Masqmail needs read and write permissions for this directory.
|
meillo@133
|
93 By default it is a directory ``lock'' inside of \fIspool_dir\fP.
|
meillo@133
|
94 \fIfile\fR must be an absolute path.
|
meillo@133
|
95
|
meillo@133
|
96 .TP
|
meillo@34
|
97 \fBhost_name = \fIstring\fR
|
meillo@0
|
98
|
meillo@34
|
99 This is used in different places: Masqmail identifies itself in the greeting banner
|
meillo@34
|
100 on incoming connections and in the HELO/EHLO command for outgoing connections with this name,
|
meillo@34
|
101 it is used in the Received: header and to qualify the sender of a locally originating message.
|
meillo@0
|
102
|
meillo@34
|
103 If the string begins with a slash `/', it it assumed that it is a filename,
|
meillo@34
|
104 and the first line of this file will be used.
|
meillo@34
|
105 Usually this will be `/etc/mailname' to make masqmail conform to Debian policies.
|
meillo@0
|
106
|
meillo@34
|
107 It is not used to find whether an address is local. Use \fBlocal_hosts\fR for that.
|
meillo@0
|
108
|
meillo@0
|
109 .TP
|
meillo@34
|
110 \fBremote_port = \fIn\fR
|
meillo@0
|
111
|
meillo@0
|
112 The remote port number to be used. This defaults to port 25.
|
meillo@0
|
113
|
meillo@34
|
114 This option is deprecated.
|
meillo@34
|
115 Use \fBhost_name\fR in the route configuration instead.
|
meillo@34
|
116 See \fBmasqmail.route(5)\fR.
|
meillo@34
|
117
|
meillo@0
|
118 .TP
|
meillo@34
|
119 \fBlocal_hosts = \fIlist\fR
|
meillo@0
|
120
|
meillo@34
|
121 A semicolon `;' separated list of hostnames which are considered local.
|
meillo@34
|
122 Normally you set it to "localhost;foo;foo.bar.com" if your host has the
|
meillo@34
|
123 fully qualified domain name `foo.bar.com'.
|
meillo@0
|
124
|
meillo@0
|
125 .TP
|
meillo@34
|
126 \fBlocal_nets = \fIlist\fR
|
meillo@0
|
127
|
meillo@34
|
128 A semicolon `;' separated list of hostnames which are on the `local' net.
|
meillo@34
|
129 Delivery to these hosts is attempted immediately.
|
meillo@34
|
130 You can use patterns with `*', e.g. "*.bar.com".
|
meillo@0
|
131
|
meillo@0
|
132 .TP
|
meillo@34
|
133 \fBlocal_addresses = \fIlist\fR
|
meillo@0
|
134
|
meillo@34
|
135 A semicolon `;' separated list of fully qualified email-addresses which are
|
meillo@34
|
136 considered local although their domain name part is not in the list of \fBlocal_hosts\fR.
|
meillo@0
|
137
|
meillo@34
|
138 For example: There are two people working at your LAN: person1@yourdomain and person2@yourdomain.
|
meillo@34
|
139 But there are other persons @yourdomain which are NOT local.
|
meillo@34
|
140 So you can not put yourdomain to the list of local_hosts.
|
meillo@34
|
141 If person1 now wants to write to person2@yourdomain and this mail should not leave the LAN then you can put
|
meillo@0
|
142
|
meillo@0
|
143 local_addresses = "person1@yourdomain;person2@yourdomain"
|
meillo@0
|
144
|
meillo@0
|
145 to your masqmail.conf.
|
meillo@34
|
146
|
meillo@0
|
147 .TP
|
meillo@34
|
148 \fBnot_local_addresses = \fIlist\fR
|
meillo@0
|
149
|
meillo@34
|
150 A semicolon `;' separated list of fully qualified email-addresses which are
|
meillo@34
|
151 considered not local although their domain name part is in the list of \fBlocal_hosts\fR.
|
meillo@0
|
152
|
meillo@34
|
153 This is the opposite of the previous case.
|
meillo@34
|
154 The majority of addresses of a specific domain are local.
|
meillo@34
|
155 But some users are not.
|
meillo@34
|
156 With this option you can easily exclude these users.
|
meillo@0
|
157
|
meillo@0
|
158 Example:
|
meillo@0
|
159
|
meillo@0
|
160 local_hosts = "localhost;myhost;mydomain.net"
|
meillo@0
|
161
|
meillo@0
|
162 not_local_addresses = "eric@mydomain.net"
|
meillo@34
|
163
|
meillo@0
|
164 .TP
|
meillo@34
|
165 \fBlisten_addresses = \fIlist\fR
|
meillo@0
|
166
|
meillo@34
|
167 A semicolon `;' separated list of interfaces on which connections will be accepted.
|
meillo@34
|
168 An interface ist defined by a hostname, optionally followed by a colon `:' and a number for the port.
|
meillo@34
|
169 If this is left out, port 25 will be used.
|
meillo@0
|
170
|
meillo@34
|
171 You can set this to "localhost:25;foo:25" if your hostname is `foo'.
|
meillo@0
|
172
|
meillo@34
|
173 Note that the names are resolved to IP addreses.
|
meillo@34
|
174 If your host has different names which resolve to the same IP,
|
meillo@34
|
175 use only one of them, otherwise you will get an error message.
|
meillo@0
|
176
|
meillo@0
|
177 .TP
|
meillo@34
|
178 \fBdo_save_envelope_to = \fIboolean\fR
|
meillo@0
|
179
|
meillo@34
|
180 If this is set to true, a possibly existing Envelope-to: header in an incoming mail
|
meillo@34
|
181 which is received via either pop3 or smtp will be saved as an X-Orig-Envelope-to: header.
|
meillo@0
|
182
|
meillo@34
|
183 This is useful if you retrieve mail from a pop3 server with either masqmail or fetchmail,
|
meillo@34
|
184 and the server supports Envelope-to: headers,
|
meillo@34
|
185 and you want to make use of those with a mail filtering tool, e.g. procmail.
|
meillo@34
|
186 It cannot be preserved because masqmail sets such a header by itself.
|
meillo@0
|
187
|
meillo@0
|
188 Default is false.
|
meillo@34
|
189
|
meillo@0
|
190 .TP
|
meillo@34
|
191 \fBdo_relay = \fIboolean\fR
|
meillo@0
|
192
|
meillo@34
|
193 If this is set to false, mail with a return path that is not local and a destination
|
meillo@34
|
194 that is also not local will not be accepted via smtp and a 550 reply will be given.
|
meillo@34
|
195 Default is true.
|
meillo@0
|
196
|
meillo@34
|
197 Note that this will not protect you from spammers using open relays,
|
meillo@34
|
198 but from users unable to set their address in their mail clients.
|
meillo@0
|
199
|
meillo@0
|
200 .TP
|
meillo@34
|
201 \fBdo_queue = \fIboolean\fR
|
meillo@0
|
202
|
meillo@34
|
203 If this is set, mail will not be delivered immediately when accepted.
|
meillo@34
|
204 Same as calling masqmail with the \fB\-odq\fR option.
|
meillo@0
|
205
|
meillo@0
|
206 .TP
|
meillo@34
|
207 \fBonline_routes.\fIname\fR = \fIlist\fR
|
meillo@0
|
208
|
meillo@34
|
209 Replace \fIname\fR with a name to identify a connection.
|
meillo@34
|
210 Set this to a filename (or a list of filenames) for the special route configuration for that connection.
|
meillo@34
|
211 You will use that name to call masqmail with the \fB\-qo\fR option every time a
|
meillo@34
|
212 connection to your ISP is set up.
|
meillo@0
|
213
|
meillo@34
|
214 Example: Your ISP has the name FastNet.
|
meillo@34
|
215 Then you write the following line in the main configuration:
|
meillo@0
|
216
|
meillo@139
|
217 \fBonline_routes.FastNet\fR = \fI"/etc/masqmail/fastnet.route"\fR
|
meillo@0
|
218
|
meillo@34
|
219 \fI/etc/masqmail/fastnet.route\fR is the route configuration file, see \fBmasqmail.route(5)\fR.
|
meillo@34
|
220 As soon as a link to FastNet has been set up, you call masqmail \fB\-qo \fIFastNet\fR.
|
meillo@34
|
221 Masqmail will then read the specified file and send the mails.
|
meillo@0
|
222
|
meillo@0
|
223 .TP
|
meillo@34
|
224 \fBconnect_route.\fIname\fR = \fIlist\fR
|
meillo@0
|
225
|
meillo@34
|
226 Old name for \fBonline_routes\fR.
|
meillo@0
|
227
|
meillo@0
|
228 .TP
|
meillo@34
|
229 \fBlocal_net_route = \fIfile\fR
|
meillo@0
|
230
|
meillo@34
|
231 This is similar to \fBonline_routes.\fIname\fR but for the local net.
|
meillo@34
|
232 Recipient addresses that are in local_nets will be routed using this route configuration.
|
meillo@34
|
233 Main purpose is to define a mail server with mail_host in your local network.
|
meillo@34
|
234 In simple environments this can be left unset.
|
meillo@34
|
235 If unset, a default route configuration will be used.
|
meillo@0
|
236
|
meillo@0
|
237 .TP
|
meillo@34
|
238 \fBalias_file = \fIfile\fR
|
meillo@0
|
239
|
meillo@34
|
240 Set this to the location of your alias file.
|
meillo@34
|
241 If unset, no aliasing will be done.
|
meillo@0
|
242
|
meillo@0
|
243 .TP
|
meillo@34
|
244 \fBalias_local_caseless = \fIboolean\fR
|
meillo@0
|
245
|
meillo@0
|
246 If this is set, local parts in the alias file will be matched disregarding upper/lower case.
|
meillo@34
|
247
|
meillo@0
|
248 .TP
|
meillo@34
|
249 \fBpipe_fromline = \fIboolean\fR
|
meillo@0
|
250
|
meillo@34
|
251 If this is set, a from line will be prepended to the output stream whenever
|
meillo@34
|
252 a pipe command is called after an alias expansion.
|
meillo@34
|
253 Default is false.
|
meillo@0
|
254
|
meillo@0
|
255 .TP
|
meillo@34
|
256 \fBpipe_fromhack = \fIboolean\fR
|
meillo@0
|
257
|
meillo@34
|
258 If this is set, each line beginning with `From ' is replaced with `>From '
|
meillo@34
|
259 whenever a pipe command is called after an alias expansion.
|
meillo@34
|
260 You probably want this if you have set \fBpipe_fromline\fR above.
|
meillo@34
|
261 Default is false.
|
meillo@0
|
262
|
meillo@0
|
263 .TP
|
meillo@34
|
264 \fBmbox_default = \fIstring\fR
|
meillo@0
|
265
|
meillo@34
|
266 The default local delivery method.
|
meillo@34
|
267 Can be one of mbox, mda or maildir (the latter only if maildir support is enabled at compile time).
|
meillo@34
|
268 Default is mbox.
|
meillo@34
|
269 You can override this for each user by using the \fBmbox_users\fR, \fBmda_users\fR,
|
meillo@34
|
270 or \fBmaildir_users\fR options (see below).
|
meillo@0
|
271
|
meillo@0
|
272 .TP
|
meillo@34
|
273 \fBmbox_users = \fIlist\fR
|
meillo@0
|
274
|
meillo@0
|
275 A list of users which wish delivery to an mbox style mail folder.
|
meillo@34
|
276
|
meillo@0
|
277 .TP
|
meillo@34
|
278 \fBmda_users = \fIlist\fR
|
meillo@0
|
279
|
meillo@34
|
280 A list of users which wish local delivery to an mda.
|
meillo@34
|
281 You have to set \fBmda\fR (see below) as well.
|
meillo@0
|
282
|
meillo@0
|
283 .TP
|
meillo@34
|
284 \fBmaildir_users = \fIlist\fR
|
meillo@0
|
285
|
meillo@34
|
286 A list of users which wish delivery to a qmail style maildir.
|
meillo@34
|
287 The path to maildir is ~/Maildir/.
|
meillo@34
|
288 The maildir will be created if it does not exist.
|
meillo@0
|
289
|
meillo@0
|
290 .TP
|
meillo@34
|
291 \fBmda = \fIexpand string\fR
|
meillo@0
|
292
|
meillo@34
|
293 If you want local delivery to be transferred to an mda (Mail Delivery Agent),
|
meillo@34
|
294 set this to a command.
|
meillo@34
|
295 The argument will be expanded on delivery time,
|
meillo@34
|
296 you can use variables beginning with a dolloar sign `$', optionally enclosed in curly braces.
|
meillo@34
|
297 Variables you can use are:
|
meillo@0
|
298
|
meillo@34
|
299 uid - the unique message id.
|
meillo@34
|
300 This is not necessarily identical with the Message ID as given in the Message ID: header.
|
meillo@0
|
301
|
meillo@0
|
302 received_host - the host the mail was received from
|
meillo@0
|
303
|
meillo@34
|
304 ident - the ident, this is either the ident delivered by the ident protocol
|
meillo@34
|
305 or the user id of the sender if the message was received locally.
|
meillo@0
|
306
|
meillo@0
|
307 return_path_local - the local part of the return path (sender).
|
meillo@0
|
308
|
meillo@0
|
309 return_path_domain - the domain part of the return path (sender).
|
meillo@0
|
310
|
meillo@0
|
311 return_path - the complete return path (sender).
|
meillo@0
|
312
|
meillo@0
|
313 rcpt_local - the local part of the recipient.
|
meillo@0
|
314
|
meillo@0
|
315 rcpt_domain - the domain part of the recipient.
|
meillo@0
|
316
|
meillo@0
|
317 rcpt - the complete recipient address.
|
meillo@0
|
318
|
meillo@0
|
319 Example:
|
meillo@0
|
320
|
meillo@16
|
321 mda="/usr/bin/procmail \-Y \-d ${rcpt_local}"
|
meillo@0
|
322
|
meillo@34
|
323 For the mda, as for pipe commands, a few environment variables will be set as well.
|
meillo@34
|
324 See \fBmasqmail(8)\fR.
|
meillo@34
|
325 To use environment variables for the mda, the dollar sign `$' has to be escaped with a backslash,
|
meillo@34
|
326 otherwise they will be tried to be expanded with the internal variables.
|
meillo@34
|
327
|
meillo@0
|
328 .TP
|
meillo@34
|
329 \fBmda_fromline = \fIboolean\fR
|
meillo@0
|
330
|
meillo@34
|
331 If this is set, a from line will be prepended to the output stream whenever
|
meillo@34
|
332 a message is delivered to an mda.
|
meillo@34
|
333 Default is false.
|
meillo@0
|
334
|
meillo@0
|
335 .TP
|
meillo@34
|
336 \fBmda_fromhack = \fIboolean\fR
|
meillo@0
|
337
|
meillo@34
|
338 If this is set, each line beginning with `From ' is replaced with `>From '
|
meillo@34
|
339 whenever a message is delivered to an mda.
|
meillo@34
|
340 You probably want this if you have set \fBmda_fromline\fR above.
|
meillo@34
|
341 Default is false.
|
meillo@0
|
342
|
meillo@0
|
343 .TP
|
meillo@34
|
344 \fBonline_detect = \fIstring\fR
|
meillo@0
|
345
|
meillo@34
|
346 Defines the method masqmail uses to detect whether there is currently an online connection.
|
meillo@112
|
347 It can have the values \fIfile\fR, \fIpipe\fR, or \fImserver\fR.
|
meillo@0
|
348
|
meillo@112
|
349 When it is set to \fIfile\fR, masqmail first checks for the existence of \fBonline_file\fR
|
meillo@34
|
350 (see below) and if it exists, it reads it.
|
meillo@34
|
351 The content of the file should be the name of the current connection as defined
|
meillo@34
|
352 with \fBconnect_route.\fIname\fR (trailing whitespace is removed).
|
meillo@0
|
353
|
meillo@112
|
354 When it is set to \fIpipe\fR, masqmail calls the executable given by the
|
meillo@34
|
355 \fBonline_pipe\fR option (see below) and reads the current online status from its standard output.
|
meillo@0
|
356
|
meillo@112
|
357 When it is set to \fImserver\fR, masqmail connects to the masqdialer server
|
meillo@34
|
358 using the value of \fBmserver_iface\fR and asks it whether a connection exists and for the name,
|
meillo@34
|
359 which should be the name of the current connection as defined with \fBconnect_route.\fIname\fR.
|
meillo@92
|
360 \fBThe mserver detection method is OBSOLETE.\fR
|
meillo@92
|
361 See mserver_iface for a note on how to replace it.
|
meillo@0
|
362
|
meillo@34
|
363 No matter how masqmail detects the online status,
|
meillo@34
|
364 only messages that are accepted at online time will be delivered using the connection.
|
meillo@34
|
365 The spool still has to be emptied with masqmail \fB\-qo\fIconnection\fR.
|
meillo@0
|
366
|
meillo@0
|
367 .TP
|
meillo@34
|
368 \fBonline_file = \fIfile\fR
|
meillo@0
|
369
|
meillo@34
|
370 This is the name of the file checked for when masqmail determines whether it is online.
|
meillo@34
|
371 The file should only exist when there is currently a connection.
|
meillo@34
|
372 Create it in your ip-up script with e.g.
|
meillo@0
|
373
|
meillo@92
|
374 echo "connection-name" >/var/run/masqmail/masqmail-route
|
meillo@0
|
375
|
meillo@37
|
376 chmod 0644 /var/run/masqmail/masqmail-route
|
meillo@0
|
377
|
meillo@0
|
378 Do not forget to delete it in your ip-down script.
|
meillo@34
|
379
|
meillo@0
|
380 .TP
|
meillo@34
|
381 \fBonline_pipe = \fIfile\fR
|
meillo@0
|
382
|
meillo@34
|
383 This is the name of the executable which will be called to determine the online status.
|
meillo@34
|
384 This executable should just print the name of the current connection to
|
meillo@34
|
385 the standard output and return a zero status code.
|
meillo@34
|
386 masqmail assumes it is offline if the script returns with a non zero status.
|
meillo@34
|
387 Simple example:
|
meillo@0
|
388
|
meillo@0
|
389 #!/bin/sh
|
meillo@0
|
390
|
meillo@37
|
391 [ \-e /var/run/masqmail/masqmail-route ] || exit 1
|
meillo@0
|
392
|
meillo@37
|
393 cat /var/run/masqmail/masqmail-route
|
meillo@0
|
394
|
meillo@0
|
395 exit 0
|
meillo@0
|
396
|
meillo@129
|
397 Of course, instead of the example above you could as well use \fIfile\fR as
|
meillo@34
|
398 the online detection method, but you can do something more sophisticated.
|
meillo@34
|
399
|
meillo@0
|
400 .TP
|
meillo@34
|
401 \fBmserver_iface = \fIinterface\fR
|
meillo@0
|
402
|
meillo@92
|
403 \fBThis option is OBSOLETE\fP, use
|
meillo@92
|
404
|
meillo@92
|
405 online_method=pipe
|
meillo@92
|
406
|
meillo@92
|
407 online_pipe="/usr/bin/mservdetect localhost 222"
|
meillo@92
|
408
|
meillo@92
|
409 instead.
|
meillo@92
|
410
|
meillo@34
|
411 The interface the masqdialer server is listening to.
|
meillo@34
|
412 Usually this will be "localhost:224" if mserver is running on the same host as masqmail.
|
meillo@34
|
413 But using this option, you can also let masqmail run on another host by setting
|
meillo@34
|
414 \fBmserver_iface\fR to another hostname, e.g. "foo:224".
|
meillo@0
|
415
|
meillo@0
|
416 .TP
|
meillo@34
|
417 \fBget.\fIname\fR = \fIfile\fR
|
meillo@0
|
418
|
meillo@34
|
419 Replace \fIname\fR with a name to identify a get configuration.
|
meillo@34
|
420 Set this to a filename for the get configuration.
|
meillo@34
|
421 These files will be used to retrieve mail when called with the \-g option.
|
meillo@0
|
422
|
meillo@0
|
423 .TP
|
meillo@34
|
424 \fBonline_gets.\fIname\fR = \fIlist\fR
|
meillo@0
|
425
|
meillo@34
|
426 Replace \fIname\fR with a name to identify an online configuration.
|
meillo@34
|
427 Set this to a filename (or a list of filenames) for the get configuration.
|
meillo@34
|
428 These files will be used to retrieve mail when called with the \-go option.
|
meillo@0
|
429
|
meillo@0
|
430 .TP
|
meillo@34
|
431 \fBident_trusted_nets = \fIlist\fR
|
meillo@0
|
432
|
meillo@34
|
433 \fIlist\fR is a list of networks of the form a.b.c.d/e (e.g. 192.168.1.0/24),
|
meillo@34
|
434 from which the ident given by the ident protocol will be trusted,
|
meillo@34
|
435 so a user can delete his mail from the queue if the ident is identical to his login name.
|
meillo@0
|
436
|
meillo@0
|
437 .TP
|
meillo@34
|
438 \fBerrmsg_file = \fIfile\fR
|
meillo@0
|
439
|
meillo@34
|
440 Set this to a template which will be used to generate delivery failure reports.
|
meillo@34
|
441 Variable parts within the template begin with a dollar sign and are identical
|
meillo@34
|
442 to those which can be used as arguments for the mda command, see \fBmda\fR above.
|
meillo@34
|
443 Additional information can be included with @failed_rcpts, @msg_headers and @msg_body,
|
meillo@34
|
444 these must be at the beginning of a line and will be replaced with the list of the failed recipients,
|
meillo@34
|
445 the message headers and the message body of the failed message.
|
meillo@0
|
446
|
meillo@0
|
447 Default is /usr/share/masqmail/tpl/failmsg.tpl.
|
meillo@34
|
448
|
meillo@0
|
449 .TP
|
meillo@34
|
450 \fBwarnmsg_file = \fIfile\fR
|
meillo@0
|
451
|
meillo@34
|
452 Set this to a template which will be used to generate delivery warning reports.
|
meillo@34
|
453 It uses the same mechanisms for variables as \fBerrmsg_file\fR, see above.
|
meillo@0
|
454
|
meillo@0
|
455 Default is /usr/share/masqmail/tpl/warnmsg.tpl.
|
meillo@34
|
456
|
meillo@0
|
457 .TP
|
meillo@34
|
458 \fBwarn_intervals\fR = \fIlist\fR
|
meillo@0
|
459
|
meillo@34
|
460 Set this to a list of time intervals, at which delivery warnings
|
meillo@34
|
461 (starting with the receiving time of the message) shall be generated.
|
meillo@0
|
462
|
meillo@34
|
463 A warning will only be generated just after an attempt to deliver the mail
|
meillo@34
|
464 and if that attempt failed temporarily.
|
meillo@34
|
465 So a warning may be generated after a longer time, if there was no attempt before.
|
meillo@0
|
466
|
meillo@0
|
467 Default is "1h;4h;8h;1d;2d;3d"
|
meillo@34
|
468
|
meillo@0
|
469 .TP
|
meillo@34
|
470 \fBmax_defer_time\fR = \fItime\fR
|
meillo@0
|
471
|
meillo@34
|
472 This is the maximum time, in which a temporarily failed mail will be kept in the spool.
|
meillo@34
|
473 When this time is exceeded, it will be handled as a delivery failure,
|
meillo@34
|
474 and the message will be bounced.
|
meillo@0
|
475
|
meillo@34
|
476 The excedence of this time will only be noticed if the message was actually tried to be delivered.
|
meillo@34
|
477 If, for example, the message can only be delivered when online,
|
meillo@34
|
478 but you have not been online for that time, no bounce will be generated.
|
meillo@0
|
479
|
meillo@0
|
480 Default is 4d (4 days)
|
meillo@34
|
481
|
meillo@0
|
482 .TP
|
meillo@34
|
483 \fBlog_user = \fIname\fR
|
meillo@0
|
484
|
meillo@34
|
485 Replace \fIname\fR with a valid local or remote mail address.
|
meillo@0
|
486
|
meillo@44
|
487 If this option is set, then a copy of every mail,
|
meillo@44
|
488 that passes through the masqmail system will also be sent to the given mail address.
|
meillo@0
|
489
|
meillo@34
|
490 For example you can feed your mails into a program like hypermail
|
meillo@34
|
491 for archiving purpose by placing an appropriate pipe command in masqmail.alias
|
meillo@0
|
492
|
meillo@117
|
493 .TP
|
meillo@117
|
494 \fBmax_msg_size\fR = \fIbytes\fR
|
meillo@117
|
495
|
meillo@117
|
496 This option sets the maximum size in bytes masqmail will accept for delivery.
|
meillo@117
|
497 This value is advertised to the SMTP client by the `SIZE' message during SMTP
|
meillo@117
|
498 session setup.
|
meillo@117
|
499 Clients pretending to send, or actually send,
|
meillo@117
|
500 more than \fIbytes\fR will get a 552 error message.
|
meillo@117
|
501
|
meillo@120
|
502 `0' means no fixed maximum size limit is in force.
|
meillo@120
|
503
|
meillo@120
|
504 Default is 0 (= unlimited).
|
meillo@117
|
505
|
meillo@134
|
506 .TP
|
meillo@134
|
507 \fBdefer_all\fR = \fIboolean\fR
|
meillo@134
|
508
|
meillo@134
|
509 If set to true, masqmail replies with ``421 service temporarily unavailable''
|
meillo@134
|
510 to any SMTP request and shuts the connection down.
|
meillo@134
|
511 Note: This option is for debugging purposes only.
|
meillo@134
|
512
|
meillo@134
|
513 Default: false
|
meillo@134
|
514
|
meillo@34
|
515
|
meillo@0
|
516 .SH AUTHOR
|
meillo@0
|
517
|
meillo@34
|
518 Masqmail was written by Oliver Kurth.
|
meillo@34
|
519 It is now maintained by Markus Schnalke <meillo@marmaro.de>.
|
meillo@0
|
520
|
meillo@95
|
521 You will find the newest version of masqmail at \fBhttp://marmaro.de/prog/masqmail/\fR.
|
meillo@26
|
522 There is also a mailing list, you will find information about it at masqmail's main site.
|
meillo@0
|
523
|
meillo@34
|
524
|
meillo@0
|
525 .SH BUGS
|
meillo@0
|
526
|
meillo@34
|
527 Please report bugs to the mailing list.
|
meillo@34
|
528
|
meillo@0
|
529
|
meillo@0
|
530 .SH SEE ALSO
|
meillo@0
|
531
|
meillo@34
|
532 \fBmasqmail(8)\fR, \fBmasqmail.route(5)\fR, \fBmasqmail.get(5)\fR
|