masqmail-0.2

annotate docs/masqmail.conf.5 @ 41:5432f13c7e58

find changesets by author, revision, files, or words in the commit message
updated ChangeLog and NEWS
author meillo@marmaro.de
date Mon, 10 May 2010 12:26:54 +0200
parents 4fee89792559
children 03817f849106
rev   line source
meillo@40 1 .TH masqmail.conf 5 2010-05-07 masqmail-0.3.0 "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@34 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@34 22 Each val 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@34 25 For some values patterns (like `*',`?') can be used.
meillo@34 26 The spaces before 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@34 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@34 33 The format of the files is different though, within these files each entry is on another line.
meillo@34 34 (And 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@34 66 \fBmail_dir = \fIfile\fR
meillo@0 67
meillo@34 68 The directory where local mail is stored, usually \fI/var/spool/mail\fR or \fI/var/mail\fR.
meillo@0 69
meillo@0 70 .TP
meillo@34 71 \fBspool_dir = \fIfile\fR
meillo@0 72
meillo@34 73 The directory where masqmail stores its spool files (and later also other stuff).
meillo@34 74 It must have a subdirectory \fIinput\fR.
meillo@34 75 Masqmail needs read and write permissions for this directory.
meillo@34 76 I suggest to use \fI/var/spool/masqmail\fR.
meillo@0 77
meillo@0 78 .TP
meillo@34 79 \fBhost_name = \fIstring\fR
meillo@0 80
meillo@34 81 This is used in different places: Masqmail identifies itself in the greeting banner
meillo@34 82 on incoming connections and in the HELO/EHLO command for outgoing connections with this name,
meillo@34 83 it is used in the Received: header and to qualify the sender of a locally originating message.
meillo@0 84
meillo@34 85 If the string begins with a slash `/', it it assumed that it is a filename,
meillo@34 86 and the first line of this file will be used.
meillo@34 87 Usually this will be `/etc/mailname' to make masqmail conform to Debian policies.
meillo@0 88
meillo@34 89 It is not used to find whether an address is local. Use \fBlocal_hosts\fR for that.
meillo@0 90
meillo@0 91 .TP
meillo@34 92 \fBremote_port = \fIn\fR
meillo@0 93
meillo@0 94 The remote port number to be used. This defaults to port 25.
meillo@0 95
meillo@34 96 This option is deprecated.
meillo@34 97 Use \fBhost_name\fR in the route configuration instead.
meillo@34 98 See \fBmasqmail.route(5)\fR.
meillo@34 99
meillo@0 100 .TP
meillo@34 101 \fBlocal_hosts = \fIlist\fR
meillo@0 102
meillo@34 103 A semicolon `;' separated list of hostnames which are considered local.
meillo@34 104 Normally you set it to "localhost;foo;foo.bar.com" if your host has the
meillo@34 105 fully qualified domain name `foo.bar.com'.
meillo@0 106
meillo@0 107 .TP
meillo@34 108 \fBlocal_nets = \fIlist\fR
meillo@0 109
meillo@34 110 A semicolon `;' separated list of hostnames which are on the `local' net.
meillo@34 111 Delivery to these hosts is attempted immediately.
meillo@34 112 You can use patterns with `*', e.g. "*.bar.com".
meillo@0 113
meillo@0 114 .TP
meillo@34 115 \fBlocal_addresses = \fIlist\fR
meillo@0 116
meillo@34 117 A semicolon `;' separated list of fully qualified email-addresses which are
meillo@34 118 considered local although their domain name part is not in the list of \fBlocal_hosts\fR.
meillo@0 119
meillo@34 120 For example: There are two people working at your LAN: person1@yourdomain and person2@yourdomain.
meillo@34 121 But there are other persons @yourdomain which are NOT local.
meillo@34 122 So you can not put yourdomain to the list of local_hosts.
meillo@34 123 If person1 now wants to write to person2@yourdomain and this mail should not leave the LAN then you can put
meillo@0 124
meillo@0 125 local_addresses = "person1@yourdomain;person2@yourdomain"
meillo@0 126
meillo@0 127 to your masqmail.conf.
meillo@34 128
meillo@0 129 .TP
meillo@34 130 \fBnot_local_addresses = \fIlist\fR
meillo@0 131
meillo@34 132 A semicolon `;' separated list of fully qualified email-addresses which are
meillo@34 133 considered not local although their domain name part is in the list of \fBlocal_hosts\fR.
meillo@0 134
meillo@34 135 This is the opposite of the previous case.
meillo@34 136 The majority of addresses of a specific domain are local.
meillo@34 137 But some users are not.
meillo@34 138 With this option you can easily exclude these users.
meillo@0 139
meillo@0 140 Example:
meillo@0 141
meillo@0 142 local_hosts = "localhost;myhost;mydomain.net"
meillo@0 143
meillo@0 144 not_local_addresses = "eric@mydomain.net"
meillo@34 145
meillo@0 146 .TP
meillo@34 147 \fBlisten_addresses = \fIlist\fR
meillo@0 148
meillo@34 149 A semicolon `;' separated list of interfaces on which connections will be accepted.
meillo@34 150 An interface ist defined by a hostname, optionally followed by a colon `:' and a number for the port.
meillo@34 151 If this is left out, port 25 will be used.
meillo@0 152
meillo@34 153 You can set this to "localhost:25;foo:25" if your hostname is `foo'.
meillo@0 154
meillo@34 155 Note that the names are resolved to IP addreses.
meillo@34 156 If your host has different names which resolve to the same IP,
meillo@34 157 use only one of them, otherwise you will get an error message.
meillo@0 158
meillo@0 159 .TP
meillo@34 160 \fBdo_save_envelope_to = \fIboolean\fR
meillo@0 161
meillo@34 162 If this is set to true, a possibly existing Envelope-to: header in an incoming mail
meillo@34 163 which is received via either pop3 or smtp will be saved as an X-Orig-Envelope-to: header.
meillo@0 164
meillo@34 165 This is useful if you retrieve mail from a pop3 server with either masqmail or fetchmail,
meillo@34 166 and the server supports Envelope-to: headers,
meillo@34 167 and you want to make use of those with a mail filtering tool, e.g. procmail.
meillo@34 168 It cannot be preserved because masqmail sets such a header by itself.
meillo@0 169
meillo@0 170 Default is false.
meillo@34 171
meillo@0 172 .TP
meillo@34 173 \fBdo_relay = \fIboolean\fR
meillo@0 174
meillo@34 175 If this is set to false, mail with a return path that is not local and a destination
meillo@34 176 that is also not local will not be accepted via smtp and a 550 reply will be given.
meillo@34 177 Default is true.
meillo@0 178
meillo@34 179 Note that this will not protect you from spammers using open relays,
meillo@34 180 but from users unable to set their address in their mail clients.
meillo@0 181
meillo@0 182 .TP
meillo@34 183 \fBdo_queue = \fIboolean\fR
meillo@0 184
meillo@34 185 If this is set, mail will not be delivered immediately when accepted.
meillo@34 186 Same as calling masqmail with the \fB\-odq\fR option.
meillo@0 187
meillo@0 188 .TP
meillo@34 189 \fBonline_routes.\fIname\fR = \fIlist\fR
meillo@0 190
meillo@34 191 Replace \fIname\fR with a name to identify a connection.
meillo@34 192 Set this to a filename (or a list of filenames) for the special route configuration for that connection.
meillo@34 193 You will use that name to call masqmail with the \fB\-qo\fR option every time a
meillo@34 194 connection to your ISP is set up.
meillo@0 195
meillo@34 196 Example: Your ISP has the name FastNet.
meillo@34 197 Then you write the following line in the main configuration:
meillo@0 198
meillo@34 199 \fBonline_routes.FastNet\fR = \fI"/etc/masqmail/fastnet.route"\fR
meillo@0 200
meillo@34 201 \fI/etc/masqmail/fastnet.route\fR is the route configuration file, see \fBmasqmail.route(5)\fR.
meillo@34 202 As soon as a link to FastNet has been set up, you call masqmail \fB\-qo \fIFastNet\fR.
meillo@34 203 Masqmail will then read the specified file and send the mails.
meillo@0 204
meillo@0 205 .TP
meillo@34 206 \fBconnect_route.\fIname\fR = \fIlist\fR
meillo@0 207
meillo@34 208 Old name for \fBonline_routes\fR.
meillo@0 209
meillo@0 210 .TP
meillo@34 211 \fBlocal_net_route = \fIfile\fR
meillo@0 212
meillo@34 213 This is similar to \fBonline_routes.\fIname\fR but for the local net.
meillo@34 214 Recipient addresses that are in local_nets will be routed using this route configuration.
meillo@34 215 Main purpose is to define a mail server with mail_host in your local network.
meillo@34 216 In simple environments this can be left unset.
meillo@34 217 If unset, a default route configuration will be used.
meillo@0 218
meillo@0 219 .TP
meillo@34 220 \fBalias_file = \fIfile\fR
meillo@0 221
meillo@34 222 Set this to the location of your alias file.
meillo@34 223 If unset, no aliasing will be done.
meillo@0 224
meillo@0 225 .TP
meillo@34 226 \fBalias_local_caseless = \fIboolean\fR
meillo@0 227
meillo@0 228 If this is set, local parts in the alias file will be matched disregarding upper/lower case.
meillo@34 229
meillo@0 230 .TP
meillo@34 231 \fBpipe_fromline = \fIboolean\fR
meillo@0 232
meillo@34 233 If this is set, a from line will be prepended to the output stream whenever
meillo@34 234 a pipe command is called after an alias expansion.
meillo@34 235 Default is false.
meillo@0 236
meillo@0 237 .TP
meillo@34 238 \fBpipe_fromhack = \fIboolean\fR
meillo@0 239
meillo@34 240 If this is set, each line beginning with `From ' is replaced with `>From '
meillo@34 241 whenever a pipe command is called after an alias expansion.
meillo@34 242 You probably want this if you have set \fBpipe_fromline\fR above.
meillo@34 243 Default is false.
meillo@0 244
meillo@0 245 .TP
meillo@34 246 \fBmbox_default = \fIstring\fR
meillo@0 247
meillo@34 248 The default local delivery method.
meillo@34 249 Can be one of mbox, mda or maildir (the latter only if maildir support is enabled at compile time).
meillo@34 250 Default is mbox.
meillo@34 251 You can override this for each user by using the \fBmbox_users\fR, \fBmda_users\fR,
meillo@34 252 or \fBmaildir_users\fR options (see below).
meillo@0 253
meillo@0 254 .TP
meillo@34 255 \fBmbox_users = \fIlist\fR
meillo@0 256
meillo@0 257 A list of users which wish delivery to an mbox style mail folder.
meillo@34 258
meillo@0 259 .TP
meillo@34 260 \fBmda_users = \fIlist\fR
meillo@0 261
meillo@34 262 A list of users which wish local delivery to an mda.
meillo@34 263 You have to set \fBmda\fR (see below) as well.
meillo@0 264
meillo@0 265 .TP
meillo@34 266 \fBmaildir_users = \fIlist\fR
meillo@0 267
meillo@34 268 A list of users which wish delivery to a qmail style maildir.
meillo@34 269 The path to maildir is ~/Maildir/.
meillo@34 270 The maildir will be created if it does not exist.
meillo@0 271
meillo@0 272 .TP
meillo@34 273 \fBmda = \fIexpand string\fR
meillo@0 274
meillo@34 275 If you want local delivery to be transferred to an mda (Mail Delivery Agent),
meillo@34 276 set this to a command.
meillo@34 277 The argument will be expanded on delivery time,
meillo@34 278 you can use variables beginning with a dolloar sign `$', optionally enclosed in curly braces.
meillo@34 279 Variables you can use are:
meillo@0 280
meillo@34 281 uid - the unique message id.
meillo@34 282 This is not necessarily identical with the Message ID as given in the Message ID: header.
meillo@0 283
meillo@0 284 received_host - the host the mail was received from
meillo@0 285
meillo@34 286 ident - the ident, this is either the ident delivered by the ident protocol
meillo@34 287 or the user id of the sender if the message was received locally.
meillo@0 288
meillo@0 289 return_path_local - the local part of the return path (sender).
meillo@0 290
meillo@0 291 return_path_domain - the domain part of the return path (sender).
meillo@0 292
meillo@0 293 return_path - the complete return path (sender).
meillo@0 294
meillo@0 295 rcpt_local - the local part of the recipient.
meillo@0 296
meillo@0 297 rcpt_domain - the domain part of the recipient.
meillo@0 298
meillo@0 299 rcpt - the complete recipient address.
meillo@0 300
meillo@0 301 Example:
meillo@0 302
meillo@16 303 mda="/usr/bin/procmail \-Y \-d ${rcpt_local}"
meillo@0 304
meillo@34 305 For the mda, as for pipe commands, a few environment variables will be set as well.
meillo@34 306 See \fBmasqmail(8)\fR.
meillo@34 307 To use environment variables for the mda, the dollar sign `$' has to be escaped with a backslash,
meillo@34 308 otherwise they will be tried to be expanded with the internal variables.
meillo@34 309
meillo@0 310 .TP
meillo@34 311 \fBmda_fromline = \fIboolean\fR
meillo@0 312
meillo@34 313 If this is set, a from line will be prepended to the output stream whenever
meillo@34 314 a message is delivered to an mda.
meillo@34 315 Default is false.
meillo@0 316
meillo@0 317 .TP
meillo@34 318 \fBmda_fromhack = \fIboolean\fR
meillo@0 319
meillo@34 320 If this is set, each line beginning with `From ' is replaced with `>From '
meillo@34 321 whenever a message is delivered to an mda.
meillo@34 322 You probably want this if you have set \fBmda_fromline\fR above.
meillo@34 323 Default is false.
meillo@0 324
meillo@0 325 .TP
meillo@34 326 \fBonline_detect = \fIstring\fR
meillo@0 327
meillo@34 328 Defines the method masqmail uses to detect whether there is currently an online connection.
meillo@34 329 It can have the values \fBfile\fR, \fBpipe\fR, or \fBmserver\fR.
meillo@0 330
meillo@34 331 When it is set to \fBfile\fR, masqmail first checks for the existence of \fBonline_file\fR
meillo@34 332 (see below) and if it exists, it reads it.
meillo@34 333 The content of the file should be the name of the current connection as defined
meillo@34 334 with \fBconnect_route.\fIname\fR (trailing whitespace is removed).
meillo@0 335
meillo@34 336 When it is set to \fBpipe\fR, masqmail calls the executable given by the
meillo@34 337 \fBonline_pipe\fR option (see below) and reads the current online status from its standard output.
meillo@0 338
meillo@34 339 When it is set to \fBmserver\fR, masqmail connects to the masqdialer server
meillo@34 340 using the value of \fBmserver_iface\fR and asks it whether a connection exists and for the name,
meillo@34 341 which should be the name of the current connection as defined with \fBconnect_route.\fIname\fR.
meillo@0 342
meillo@34 343 No matter how masqmail detects the online status,
meillo@34 344 only messages that are accepted at online time will be delivered using the connection.
meillo@34 345 The spool still has to be emptied with masqmail \fB\-qo\fIconnection\fR.
meillo@0 346
meillo@0 347 .TP
meillo@34 348 \fBonline_file = \fIfile\fR
meillo@0 349
meillo@34 350 This is the name of the file checked for when masqmail determines whether it is online.
meillo@34 351 The file should only exist when there is currently a connection.
meillo@34 352 Create it in your ip-up script with e.g.
meillo@0 353
meillo@37 354 echo \-n <name> > /var/run/masqmail/masqmail-route
meillo@0 355
meillo@37 356 chmod 0644 /var/run/masqmail/masqmail-route
meillo@0 357
meillo@0 358 Do not forget to delete it in your ip-down script.
meillo@34 359
meillo@0 360 .TP
meillo@34 361 \fBonline_pipe = \fIfile\fR
meillo@0 362
meillo@34 363 This is the name of the executable which will be called to determine the online status.
meillo@34 364 This executable should just print the name of the current connection to
meillo@34 365 the standard output and return a zero status code.
meillo@34 366 masqmail assumes it is offline if the script returns with a non zero status.
meillo@34 367 Simple example:
meillo@0 368
meillo@0 369 #!/bin/sh
meillo@0 370
meillo@37 371 [ \-e /var/run/masqmail/masqmail-route ] || exit 1
meillo@0 372
meillo@37 373 cat /var/run/masqmail/masqmail-route
meillo@0 374
meillo@0 375 exit 0
meillo@0 376
meillo@34 377 Of course, instead of the example above you could as well use \fBfile\fR as
meillo@34 378 the online detection method, but you can do something more sophisticated.
meillo@34 379
meillo@0 380 .TP
meillo@34 381 \fBmserver_iface = \fIinterface\fR
meillo@0 382
meillo@34 383 The interface the masqdialer server is listening to.
meillo@34 384 Usually this will be "localhost:224" if mserver is running on the same host as masqmail.
meillo@34 385 But using this option, you can also let masqmail run on another host by setting
meillo@34 386 \fBmserver_iface\fR to another hostname, e.g. "foo:224".
meillo@0 387
meillo@0 388 .TP
meillo@34 389 \fBget.\fIname\fR = \fIfile\fR
meillo@0 390
meillo@34 391 Replace \fIname\fR with a name to identify a get configuration.
meillo@34 392 Set this to a filename for the get configuration.
meillo@34 393 These files will be used to retrieve mail when called with the \-g option.
meillo@0 394
meillo@0 395 .TP
meillo@34 396 \fBonline_gets.\fIname\fR = \fIlist\fR
meillo@0 397
meillo@34 398 Replace \fIname\fR with a name to identify an online configuration.
meillo@34 399 Set this to a filename (or a list of filenames) for the get configuration.
meillo@34 400 These files will be used to retrieve mail when called with the \-go option.
meillo@0 401
meillo@0 402 .TP
meillo@34 403 \fBident_trusted_nets = \fIlist\fR
meillo@0 404
meillo@34 405 \fIlist\fR is a list of networks of the form a.b.c.d/e (e.g. 192.168.1.0/24),
meillo@34 406 from which the ident given by the ident protocol will be trusted,
meillo@34 407 so a user can delete his mail from the queue if the ident is identical to his login name.
meillo@0 408
meillo@0 409 .TP
meillo@34 410 \fBerrmsg_file = \fIfile\fR
meillo@0 411
meillo@34 412 Set this to a template which will be used to generate delivery failure reports.
meillo@34 413 Variable parts within the template begin with a dollar sign and are identical
meillo@34 414 to those which can be used as arguments for the mda command, see \fBmda\fR above.
meillo@34 415 Additional information can be included with @failed_rcpts, @msg_headers and @msg_body,
meillo@34 416 these must be at the beginning of a line and will be replaced with the list of the failed recipients,
meillo@34 417 the message headers and the message body of the failed message.
meillo@0 418
meillo@0 419 Default is /usr/share/masqmail/tpl/failmsg.tpl.
meillo@34 420
meillo@0 421 .TP
meillo@34 422 \fBwarnmsg_file = \fIfile\fR
meillo@0 423
meillo@34 424 Set this to a template which will be used to generate delivery warning reports.
meillo@34 425 It uses the same mechanisms for variables as \fBerrmsg_file\fR, see above.
meillo@0 426
meillo@0 427 Default is /usr/share/masqmail/tpl/warnmsg.tpl.
meillo@34 428
meillo@0 429 .TP
meillo@34 430 \fBwarn_intervals\fR = \fIlist\fR
meillo@0 431
meillo@34 432 Set this to a list of time intervals, at which delivery warnings
meillo@34 433 (starting with the receiving time of the message) shall be generated.
meillo@0 434
meillo@34 435 A warning will only be generated just after an attempt to deliver the mail
meillo@34 436 and if that attempt failed temporarily.
meillo@34 437 So a warning may be generated after a longer time, if there was no attempt before.
meillo@0 438
meillo@0 439 Default is "1h;4h;8h;1d;2d;3d"
meillo@34 440
meillo@0 441 .TP
meillo@34 442 \fBmax_defer_time\fR = \fItime\fR
meillo@0 443
meillo@34 444 This is the maximum time, in which a temporarily failed mail will be kept in the spool.
meillo@34 445 When this time is exceeded, it will be handled as a delivery failure,
meillo@34 446 and the message will be bounced.
meillo@0 447
meillo@34 448 The excedence of this time will only be noticed if the message was actually tried to be delivered.
meillo@34 449 If, for example, the message can only be delivered when online,
meillo@34 450 but you have not been online for that time, no bounce will be generated.
meillo@0 451
meillo@0 452 Default is 4d (4 days)
meillo@34 453
meillo@0 454 .TP
meillo@34 455 \fBlog_user = \fIname\fR
meillo@0 456
meillo@34 457 Replace \fIname\fR with a valid local or remote mail address.
meillo@0 458
meillo@34 459 If this option is not empty, then a copy of every mail,
meillo@34 460 that passes trough the masqmail system will also be sent to the given mail address.
meillo@0 461
meillo@34 462 For example you can feed your mails into a program like hypermail
meillo@34 463 for archiving purpose by placing an appropriate pipe command in masqmail.alias
meillo@0 464
meillo@34 465
meillo@0 466 .SH AUTHOR
meillo@0 467
meillo@34 468 Masqmail was written by Oliver Kurth.
meillo@34 469 It is now maintained by Markus Schnalke <meillo@marmaro.de>.
meillo@0 470
meillo@34 471 You will find the newest version of masqmail at \fBhttp://prog.marmaro.de/masqmail/\fR.
meillo@26 472 There is also a mailing list, you will find information about it at masqmail's main site.
meillo@0 473
meillo@34 474
meillo@0 475 .SH BUGS
meillo@0 476
meillo@34 477 Please report bugs to the mailing list.
meillo@34 478
meillo@0 479
meillo@0 480 .SH SEE ALSO
meillo@0 481
meillo@34 482 \fBmasqmail(8)\fR, \fBmasqmail.route(5)\fR, \fBmasqmail.get(5)\fR