meillo@0: <?xml version="1.0" standalone='no'?>
meillo@0: <!DOCTYPE spec SYSTEM "man.dtd">
meillo@0: 
meillo@0: <manpage name="masqmail.conf" section="5" desc="masqmail configuration file">
meillo@0: 
meillo@0: <description>
meillo@0: <p>This man page describes the syntax of the main configuration file
meillo@0: of masqmail. Its usual location is <file>/etc/masqmail/masqmail.conf</file></p>
meillo@0: 
meillo@0: <p>The configuration consists of lines of the form</p>
meillo@0: 
meillo@0: <p><opt>val</opt> = <arg>expression</arg></p>
meillo@0: 
meillo@0: <p>Where <opt>val</opt> is a variable name and <arg>expression</arg> a string,
meillo@0: which can be quoted with '"'. If the expression is on multiple lines
meillo@0: or contains characters other than letters, digits or the characters
meillo@0: '.', '-', '_', '/', it <em>must</em> be quoted. You can use quotes inside quotes
meillo@0: by escaping them with a backslash.</p>
meillo@0: 
meillo@0: <p>Each val has a <i>type</i>, which can be boolean, numeric, string
meillo@0: or list. A boolean variable can be set with one of the values 'on',
meillo@0: 'yes', and 'true' or 'off', 'no' and 'false'. List items are separated
meillo@0: with ';'. For some values patterns (like '*','?') can be used. The
meillo@0: spaces before and after the '=' are optional.</p>
meillo@0: 
meillo@0: <p>Most lists (exceptions: <opt>local_hosts</opt>,
meillo@0: <opt>local_nets</opt>, <opt>listen_addresses</opt>, <opt>online_routes</opt> and <opt>online_gets</opt>) accept
meillo@0: files. These will be recognized by a leading slash '/'. The contents
meillo@0: of these files will be included at the position of the file name,
meillo@0: there can be items or other files before and after the file entry. The
meillo@0: format of the files is different though, within these files each entry
meillo@0: is on another line. (And not separated by semicolons). This makes it
meillo@0: easy to include large lists which are common in different
meillo@0: configuration files, so they do not have to appear in every
meillo@0: configuration file.</p>
meillo@0: 
meillo@0: <p>Blank lines and lines starting with '#' are ignored.</p>
meillo@0: 
meillo@0: </description>
meillo@0: 
meillo@0: <options>
meillo@0: <option>
meillo@0: <p><opt>run_as_user = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, masqmail runs with the user id of the user who
meillo@0: invoked it and never changes it. This is for debugging purposes 
meillo@0: <em>only</em>. If the user is not root, masqmail will not be able to
meillo@0: listen on a port &lt; 1024 and will not be able to deliver local mail
meillo@0: to others than the user.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>use_syslog = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, masqmail uses syslogd for logging. It uses facility
meillo@0: MAIL. You still have to set <opt>log_dir</opt> for debug files.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>debug_level = <arg>n</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set the debug level. Valid values are 0 to 6, increasing it further
meillo@0: makes no difference. Be careful if you set this as high as 5 or higher,
meillo@0: the logs may very soon fill your hard drive.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mail_dir = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>The directory where local mail is stored,
meillo@0: usually <file>/var/spool/mail</file> or <file>/var/mail</file>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>spool_dir = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>The directory where masqmail stores its spool files (and later also
meillo@0: other stuff). It <em>must</em> have a subdirectory <file>input</file>.
meillo@0: Masqmail needs read and write permissions for this
meillo@0: directory. I suggest to use <file>/var/spool/masqmail</file>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>host_name = <arg>string</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>This is used in different places: Masqmail identifies itself in the
meillo@0: greeting banner on incoming connections and in the HELO/EHLO command
meillo@0: for outgoing connections with this name, it is used in the Received:
meillo@0: header and to qualify the sender of a locally originating message.</p>
meillo@0: 
meillo@0: <p>If the string begins with a slash '/', it it assumed that it is a
meillo@0: filename, and the first line of this file will be used. Usually this will
meillo@0: be '/etc/mailname' to make masqmail conform to Debian policies.</p>
meillo@0: 
meillo@0: <p>It is <em>not</em> used to find whether an address is local.
meillo@0: Use <opt>local_hosts</opt> for that.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>remote_port = <arg>n</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>The remote port number to be used. This defaults to port 25.</p>
meillo@0: <p>This option is deprecated. Use <opt>host_name</opt> in the route
meillo@0: configuration instead. See <manref name="masqmail.route" section="5"
meillo@0: href="masqmail.route.5.html"/>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>local_hosts = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A semicolon ';' separated list of hostnames which are considered
meillo@0: local. Normally you set it to "localhost;foo;foo.bar.com" if your host
meillo@0: has the fully qualified domain name 'foo.bar.com'.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>local_nets = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A semicolon ';' separated list of hostnames which are on the
meillo@0: 'local' net. Delivery to these hosts is attempted immediately. You can
meillo@0: use patterns with '*', eg. "*.bar.com".</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>local_addresses = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A semicolon ';' separated list of fully qualified email-addresses
meillo@0: which are considered local although their domain name part is not in
meillo@0: the list of <opt>local_hosts</opt>. </p>
meillo@0: <p>For example: There are two people working at your
meillo@0: LAN: person1@yourdomain and person2@yourdomain. But there are
meillo@0: other persons @yourdomain which are NOT local. So you can not put
meillo@0: yourdomain to the list of local_hosts. If person1 now wants
meillo@0: to write to person2@yourdomain and this mail should not leave the LAN
meillo@0: then you can put</p>
meillo@0: <p>local_addresses = "person1@yourdomain;person2@yourdomain"</p>
meillo@0: <p>to your masqmail.conf.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>not_local_addresses = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A semicolon ';' separated list of fully qualified email-addresses
meillo@0: which are considered not local although their domain name part is in
meillo@0: the list of <opt>local_hosts</opt>. </p>
meillo@0: <p>This ist the opposite of the previous case. The majority of addresses
meillo@0: of a specific domain are local. But some users are not. With this
meillo@0: option you can easily exclude these users.</p>
meillo@0: <p>Example:</p>
meillo@0: <p>local_hosts = "localhost;myhost;mydomain.net"</p>
meillo@0: <p>not_local_addresses = "eric@mydomain.net"</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>listen_addresses = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A semicolon ';' separated list of interfaces on which connections
meillo@0: will be accepted. An interface ist defined by a hostname, optionally
meillo@0: followed by a colon ':' and a number for the port. If this is left out,
meillo@0: port 25 will be used.</p>
meillo@0: <p>You can set this to "localhost:25;foo:25" if your hostname is 'foo'.</p>
meillo@0: <p>Note that the names are resolved to IP addreses. If your host has
meillo@0: different names which resolve to the same IP, use only one of them,
meillo@0: otherwise you will get an error message.
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>do_save_envelope_to = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set to true, a possibly existing Envelope-to: header in an
meillo@0: incoming mail which is received via either pop3 or smtp will be saved as
meillo@0: an X-Orig-Envelope-to: header.</p>
meillo@0: <p>This is useful if you retrieve mail from a pop3 server with either masqmail
meillo@0: or fetchmail, and the server supports Envelope-to: headers, and you want to make use
meillo@0: of those with a mail filtering tool, eg. procmail. It cannot be preserved because
meillo@0: masqmail sets such a header by itself.</p>
meillo@0: <p>Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>do_relay = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set to false, mail with a return path that is not local and a
meillo@0: destination that is also not local will not be accepted via smtp and a 550
meillo@0: reply will be given. Default is true.</p>
meillo@0: <p>Note that this will not protect you from spammers using open relays, but from
meillo@0: users unable to set their address in their mail clients.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>do_queue = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, mail will not be delivered immediately when
meillo@0: accepted. Same as calling masqmail with the <opt>-odq</opt> option.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>online_routes.<arg>name</arg> = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: 
meillo@0: <p>Replace <arg>name</arg> with a name to identify a connection. Set this
meillo@0: to a filename (or a list of filenames) for the special route configuration for that
meillo@0: connection. You will use that name to call masqmail with the
meillo@0:  <opt>-qo</opt> option every time a connection to your ISP is set
meillo@0: up.</p>
meillo@0: 
meillo@0: <p>Example: Your ISP has the name <i>FastNet</i>. Then you write the
meillo@0: following line in the main configuration:</p>
meillo@0: 
meillo@0: <p><opt>online_routes.FastNet</opt> = <arg>"/etc/masqmail/fastnet.route"</arg></p>
meillo@0: 
meillo@0: <p><file>/etc/masqmail/fastnet.route</file> is the route configuration
meillo@0: file, see <manref name="masqmail.route" section="5" href="masqmail.route.5.html"/>. As soon as a link to FastNet has been set up, you
meillo@0: call masqmail <opt>-qo</opt> <arg>FastNet</arg>. Masqmail will then
meillo@0: read the specified file and send the mails.</p>
meillo@0: 
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>connect_route.<arg>name</arg> = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Old name for <opt>online_routes</opt>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>local_net_route = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>This is similar to <opt>online_routes.<arg>name</arg></opt> but for the
meillo@0: local net. Recipient addresses that are in <b>local_nets</b> will be
meillo@0: routed using this route configuration. Main purpose is to define a
meillo@0: mail server with <b>mail_host</b> in your local network. In simple
meillo@0: environments this can be left unset. If unset, a default route
meillo@0: configuration will be used.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>alias_file = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set this to the location of your alias file. If unset, no aliasing
meillo@0: will be done.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>alias_local_caseless = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, local parts in the alias file will be matched
meillo@0: disregarding upper/lower case.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>pipe_fromline = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, a from line will be prepended to the output stream whenever
meillo@0: a pipe command is called after an alias expansion. Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>pipe_fromhack = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, each line beginning with 'From ' is replaced with '>From ' whenever
meillo@0: a pipe command is called after an alias expansion. You probably want this if you have
meillo@0: set <opt>pipe_fromline</opt> above. Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mbox_default = <arg>string</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>The default local delivery method. Can be one of mbox, mda or
meillo@0: maildir (the latter only if maildir support is enabled at compile
meillo@0: time). Default is mbox. You can override this for each user by using
meillo@0: the <opt>mbox_users</opt>, <opt>mda_users</opt> or <opt>maildir_users</opt> options
meillo@0: (see below).
meillo@0: </p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mbox_users = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A list of users which wish delivery to an mbox style mail folder.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mda_users = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A list of users which wish local delivery to an mda. You have to
meillo@0: set <opt>mda</opt> (see below) as well.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>maildir_users = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>A list of users which wish delivery to a qmail style maildir. The
meillo@0: path to maildir is ~/Maildir/. The maildir will be created if it
meillo@0: does not exist.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mda = <arg>expand string</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If you want local delivery to be transferred to an mda (Mail
meillo@0: Delivery Agent), set this to a command. The argument will be expanded
meillo@0: on delivery time, you can use variables beginning with a '$' sign,
meillo@0: optionally enclosed in curly braces. Variables you can use are:</p>
meillo@0: <p>uid - the unique message id. This is not necessarily identical with
meillo@0: the Message ID as given in the Message ID: header.</p>
meillo@0: <p>received_host - the host the mail was received from</p>
meillo@0: <p>ident - the ident, this is either the ident delivered by the ident
meillo@0: protocol or the user id of the sender if the message was received locally.</p>
meillo@0: <p>return_path_local - the local part of the return path (sender).</p>
meillo@0: <p>return_path_domain - the domain part of the return path (sender).</p>
meillo@0: <p>return_path - the complete return path (sender).</p>
meillo@0: <p>rcpt_local - the local part of the recipient.</p>
meillo@0: <p>rcpt_domain - the domain part of the recipient.</p>
meillo@0: <p>rcpt - the complete recipient address.</p>
meillo@0: <p>Example:</p><p>mda="/usr/bin/procmail -Y -d ${rcpt_local}"</p>
meillo@0: <p>For the mda, as for pipe commands, a few environment variables will
meillo@0: be set as well. See <manref name="masqmail" section="8"
meillo@0: href="masqmail.8.html"/>. To use environment variables for the mda,
meillo@0: the '$' sign has to be escaped with a backslash, otherwise they will
meillo@0: be tried to be expanded with the internal variables.</p>
meillo@0: 
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mda_fromline = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, a from line will be prepended to the output stream whenever
meillo@0: a message is delivered to an mda. Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mda_fromhack = <arg>boolean</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, each line beginning with 'From ' is replaced with '>From ' whenever
meillo@0: a message is delivered to an mda. You probably want this if you have
meillo@0: set <opt>mda_fromline</opt> above. Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>online_detect = <arg>string</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Defines the method MasqMail uses to detect whether there is
meillo@0: currently an online connection. It can have the
meillo@0: values <opt>file</opt>, <opt>pipe</opt> or <opt>mserver</opt>.</p>
meillo@0: 
meillo@0: <p>When it is set to <opt>file</opt>, MasqMail first checks for the
meillo@0: existence of <opt>online_file</opt> (see below) and if it exists, it reads
meillo@0: it. The content of the file should be the name of the current
meillo@0: connection as defined with <opt>connect_route.<arg>name</arg></opt> (without
meillo@0: a trailing newline character).</p>
meillo@0: 
meillo@0: <p>When it is set to <opt>pipe</opt>, MasqMail calls the executable given by
meillo@0: the <opt>online_pipe</opt> option (see below) and reads the current online
meillo@0: status from its standard output.</p>
meillo@0: 
meillo@0: <p>When it is set to <opt>mserver</opt>, MasqMail connects to the
meillo@0: masqdialer server using the value of <opt>mserver_iface</opt> and asks it
meillo@0: whether a connection exists and for the name, which should be the name
meillo@0: of the current connection as defined with <opt>connect_route.<arg>name</arg></opt>.</p>
meillo@0: 
meillo@0: <p>No matter how MasqMail detects the online status, only messages
meillo@0: that are accepted at online time will be delivered using the
meillo@0: connection. The spool still has to be emptied with masqmail <opt>-qo</opt>
meillo@0: <arg>connection</arg>.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>online_file = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>This is the name of the file checked for when MasqMail determines
meillo@0: whether it is online. The file should only exist when there is
meillo@0: currently a connection. Create it in your ip-up script with eg.</p>
meillo@0: 
meillo@0: <p>echo -n &lt;name&gt; &gt; /tmp/connect_route</p>
meillo@0: <p>chmod 0644 /tmp/connect_route</p>
meillo@0: 
meillo@0: <p>Do not forget to delete it in your ip-down script.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>online_pipe = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>This is the name of the executable which will be called to determine
meillo@0: the online status. This executable should just print the name oif the current
meillo@0: connection to the standard output and return a zero status code. masqmail assumes
meillo@0: it is offline if the script returns with a non zero status. Simple example:</p>
meillo@0: 
meillo@0: <p>#!/bin/sh</p>
meillo@0: <p></p>
meillo@0: <p>[ -e /tmp/connect_route ] || exit 1</p>
meillo@0: <p>cat /tmp/connect_route</p>
meillo@0: <p>exit 0</p>
meillo@0: 
meillo@0: <p>Of course, instead of the example above you could as well use <opt>file</opt> as
meillo@0: the online detection method, but you can do something more sophisticated.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mserver_iface = <arg>interface</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>The interface the masqdialer server is listening to. Usually this
meillo@0: will be "localhost:224" if mserver is running on the same host as
meillo@0: masqmail. But using this option, you can also let masqmail run on
meillo@0: another host by setting <opt>mserver_iface</opt> to another hostname,
meillo@0: eg. "foo:224".</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>get.<arg>name</arg> = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Replace <arg>name</arg> with a name to identify a get
meillo@0: configuration. Set this to a filename for the get configuration. These
meillo@0: files will be used to retrieve mail when called with the -g option.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>online_gets.<arg>name</arg> = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Replace <arg>name</arg> with a name to identify an online
meillo@0: configuration. Set this to a filename (or a list of filenames) for the get configuration. These
meillo@0: files will be used to retrieve mail when called with the -go option.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>ident_trusted_nets = <arg>list</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p><arg>list</arg> is a list of networks of the form a.b.c.d/e
meillo@0: (eg. 192.168.1.0/24), from which the ident given by the ident protocol
meillo@0: will be trusted, so a user can delete his mail from the queue if the
meillo@0: ident is identical to his login name.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>errmsg_file = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set this to a template which will be used to generate delivery failure
meillo@0: reports. Variable parts within the template begin with a dollar sign and
meillo@0: are identical to those which can be used as arguments for the mda command,
meillo@0: see <opt>mda</opt> above. Additional information can be included with
meillo@0: @failed_rcpts, @msg_headers and @msg_body, these <b>must</b> be at the
meillo@0: beginning of a line and will be replaced with the list of the failed recipients,
meillo@0: the message headers and the message body of the failed message.</p>
meillo@0: <p>Default is /usr/share/masqmail/tpl/failmsg.tpl.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>warnmsg_file = <arg>file</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Set this to a template which will be used to generate delivery warning
meillo@0: reports. It uses the same mechanisms for variables as <opt>errmsg_file</opt>,
meillo@0: see above.
meillo@0: </p>
meillo@0: <p>Default is /usr/share/masqmail/tpl/warnmsg.tpl.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>warn_intervals</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Set this to a list of time intervals, at which delivery warnings (starting
meillo@0: with the receiving time of the message) shall be generated.</p>
meillo@0: <p>A warning will only be generated just after an attempt to deliver the
meillo@0: mail and if that attempt failed temporarily. So a warning may be generated after
meillo@0: a longer time, if there was no attempt before.</p>
meillo@0: <p>Default is "1h;4h;8h;1d;2d;3d"</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>max_defer_time</opt> = <arg>time</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is the maximum time, in which a temporarily failed mail will be kept
meillo@0: in the spool. When this time is exceeded, it will be handled as a delivery failure,
meillo@0: and the message will be bounced.</p>
meillo@0: <p>The excedence of this time will only be noticed if the message was actually
meillo@0: tried to be delivered. If, for example, the message can only be delivered when
meillo@0: online, but you have not been online for that time, no bounce will be generated.</p>
meillo@0: <p>Default is 4d (4 days)</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>log_user = <arg>name</arg></opt></p>
meillo@0: <optdesc>
meillo@0: <p>Replace <arg>name</arg> with a valid local or remote mail address.</p>
meillo@0: <p>If this option is not empty, then a copy of every mail,
meillo@0: that passes trough the masqmail system will also be sent to the
meillo@0: given mail address.</p>
meillo@0: <p>For example you can feed your mails into a program like <i>hypermail</i> for
meillo@0: archiving purpose by placing an appropriate pipe command in masqmail.alias</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: </options>
meillo@0: 
meillo@0: <section name = "Author">
meillo@0: <p>masqmail was written by Oliver Kurth
meillo@0: &lt;oku@masqmail.cx&gt;</p><p>You will find the newest version of
meillo@0: masqmail at <url href="http://masqmail.cx/masqmail/"/> or search for it
meillo@0: in freshmeat (<url href="http://www.freshmeat.net"/>). There is also a mailing list,
meillo@0: you will find information about it at masqmails main site.</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "Bugs">
meillo@0: <p>You should report them to the mailing list.</p>
meillo@0: </section>
meillo@0: 
meillo@0: <section name = "See also">
meillo@0: <p>
meillo@0: <manref name="masqmail" section="8" href="masqmail.8.html"/>, <manref name="masqmail.route" section="5" href="masqmail.route.5.html"/>, <manref name="masqmail.get" section="5" href="masqmail.get.5.html"/>
meillo@0: </p>
meillo@0: </section>
meillo@0: 
meillo@0: 
meillo@0: <section name = "Comments">
meillo@0: <p>This man page was written using <manref name="xml2man" section="1"
meillo@0: href="http://masqmail.cx/xml2man/"/> by the same
meillo@0: author.</p>
meillo@0: </section>
meillo@0: 
meillo@0: </manpage>
meillo@0: