meillo@0: <?xml version="1.0" standalone='no'?>
meillo@0: <!DOCTYPE spec SYSTEM "man.dtd">
meillo@0: 
meillo@0: <manpage name="masqmail.route" section="5" desc="masqmail route configuration file">
meillo@0: 
meillo@0: <description>
meillo@0: <p>This man page describes the syntax of the route configuration files
meillo@0: of <manref name = "masqmail" section="8" href="masqmail.8.html"/>. Their usual locations are in <file>/etc/masqmail/</file>.</p>
meillo@0: </description>
meillo@0: 
meillo@0: <options>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>protocol</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p><arg>string</arg> can be one of 'smtp' or 'pipe', default is
meillo@0: 'smtp'. If set to 'smtp', mail will be sent with the SMTP protocol to
meillo@0: its destination. If set to 'pipe', you also have to set 'pipe'
meillo@0: to a command, the message will then be piped to a program. See option 'pipe' below.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>mail_host</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is preferably the mail server of your ISP. All outgoing
meillo@0: messages will be sent to this host which will distribute them to their
meillo@0: destinations. If you do not set this mails will be sent
meillo@0: directly. Because the mail server is probably 'near' to you, mail
meillo@0: transfer will be much faster if you use it.</p>
meillo@0: <p>You can optionally give a port number following the host name
meillo@0: and a colon, eg mail_host="mail.foo.com:25".</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>resolve_list</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Specify the method how the domain of the server is resolved. Possible values are
meillo@0: dns_mx, dns_a, byname. For 'dns_mx', the domain is assumed to be an MX
meillo@0: pointer to a list of host names, these will be tried each in order
meillo@0: (lowest preference value first, equal preference values in random
meillo@0: order). For 'dns_a', the domain is assumed to be an A pointer. For
meillo@0: 'byname', the library function <manref name="gethostbyname" section="3"/> will be used.</p>
meillo@0: <p>The default is "dns_mx;dns_a;byname".</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>connect_error_fail</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, a connection error will cause a mail delivery to
meillo@0: fail, ie. it will be bounced. If it is unset, it will just be defered.</p>
meillo@0: <p>Default is false. The reason for this is that masqmail is designed
meillo@0: for non permanent internet connections, where such errors may occur
meillo@0: quite often, and a bounce would be annoying.</p>
meillo@0: <p>For the default local_net route is is set to true.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>helo_name</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Set the name given with the HELO/EHLO command. If this is not
meillo@0: set, <opt>host_name</opt> from <file>masqmail.conf</file> will be used, if
meillo@0: the <opt>do_correct_helo</opt> option (see below) is unset.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>do_correct_helo</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, masqmail tries to look up your host name as it
meillo@0: appears on the internet and sends this in the HELO/EHLO command. Some
meillo@0: servers are so picky that they want this. Which is really
meillo@0: crazy. It just does not make any sense to lie about ones own identity,
meillo@0: because it can always be looked up by the server. Nobody should
meillo@0: believe in the name given by HELO/EHLO anyway. If this is not
meillo@0: set, <opt>host_name</opt> from <file>masqmail.conf</file> or as given with
meillo@0: the <opt>helo_name</opt> (see above) will be used.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>do_pipelining</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set to false, masqmail will not use ESMTP PIPELINING, even
meillo@0: if the server announces that it is able to cope with it. Default is true.</p>
meillo@0: <p>You do not want to set this to false unless the mail setup on the
meillo@0: remote server side is really broken. Keywords: wingate.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>allowed_mail_locals</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is a semicolon ';' separated list of local parts which will be
meillo@0: allowed to send mail through this connection. If unset
meillo@0: and <opt>not_allowed_mail_locals</opt> is also unset, all users are
meillo@0: allowed.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>not_allowed_mail_locals</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is a semicolon ';' separated list of local parts which will be
meillo@0: not allowed to send mail through this connection. Local
meillo@0: parts in this list will not be allowed to use this route even if they
meillo@0: are part of <opt>allowed_mail_locals</opt> (see above).</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>allowed_return_paths</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is a semicolon ';' separated list of addresses. Messages which
meillo@0: have one one of these addresses as the return path will be used using
meillo@0: this route (if not also in <opt>not_allowed_return_paths</opt> or an item
meillo@0: in <opt>not_allowed_mail_locals</opt> matches).</p>
meillo@0: <p>Patterns containing '?' and '*' can be used. The special item "&lt;&gt;" matches
meillo@0: the null sender address (eg. failure notices or delivery notifications).</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>not_allowed_return_paths</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is a semicolon ';' separated list of addresses. Messages which
meillo@0: have one one of these addresses as the return path will <em>not</em> be used using
meillo@0: this route (even if also in <opt>allowed_return_paths</opt> or an item
meillo@0: in <opt>allowed_mail_locals</opt> matches).</p>
meillo@0: <p>Patterns containing '?' and '*' can be used. The special item "&lt;&gt;" matches
meillo@0: the null sender address (eg. failure notices or delivery notifications).</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>allowed_rcpt_domains</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>A list of recipient domains where mail will be sent to. This is for
meillo@0: example useful if you use this route configuration when connected to
meillo@0: another LAN via ppp. Patterns containing '?' and '*' can be used.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>not_allowed_rcpt_domains</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>A list of recipient domains where mail will <em>not</em> be sent
meillo@0: to. This is for example useful if you send mail directly (<opt>mail_host</opt> is
meillo@0: not set) and you know of hosts that will not accept mail from you
meillo@0: because they use a dialup list (eg. <url href="http://maps.vix.com/dul/"/>. If any domain
meillo@0: matches both <opt>allowed_rcpt_domains</opt> and <opt>not_allowed_rcpt_domains</opt>,
meillo@0: mail will not be sent to this domain. Patterns containing '?' and '*' can be used.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>set_h_from_domain</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Replace the domain part in 'From:' headers with this value. This
meillo@0: may be useful if you use a private, outside unknown address on your
meillo@0: local LAN and want this to be replaced by the domain of the address of
meillo@0: your email addrsss on the internet. Note that this is different to <opt>
meillo@0: set_return_path_domain</opt>, see below.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>set_return_path_domain</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Sets the domain part of the envelope from address. Some hosts check
meillo@0: whether this is the same as the net the connection is coming from. If
meillo@0: not, they reject the mail because they suspect spamming. It should be
meillo@0: a valid address, because some mail servers also check
meillo@0: that. You can also use this to set it to your usual address on the
meillo@0: internet and put a local address only known on your LAN in the
meillo@0: configuration of your mailer. Only the domain part will
meillo@0: be changed, the local part remains unchanged. Use <opt>
meillo@0: map_return_path_addresses</opt> for rewriting local parts.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>map_h_from_addresses</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is similar to <opt>set_h_from_domain</opt>, but more flexible. Set
meillo@0: this to a list which maps local parts to a full RFC 822 compliant
meillo@0: email address, the local parts (the <em>keys</em>) are separated from
meillo@0: the addresses (the <em>values</em>) by colons (':').</p>
meillo@0: 
meillo@0: <p>Example:</p>
meillo@0: 
meillo@0: <p>map_h_from_addresses = "john: John Smith &lt;jsmith@mail.academic.edu&gt;;
meillo@0: charlie: Charlie Miller &lt;cmiller@mx.commercial.com&gt;"</p>
meillo@0: <p>You can use patterns, eg. * as keys.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>map_h_reply_to_addresses</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Same as <opt>map_h_from_addresses</opt>, but for the 'Reply-To:' header.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>map_h_mail_followup_to_addresses</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Same as <opt>map_h_from_addresses</opt>, but for the 'Mail-Followup-To:'
meillo@0: header. Useful when replying to mailing lists.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>map_return_path_addresses</opt> = <arg>list</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This is similar to <opt>set_return_path_domain</opt>, but more
meillo@0: flexible. Set this to a list which maps local parts to a full RFC 821
meillo@0: compliant email address, the local parts (the keys) are
meillo@0: separated from the addresses (the values) by colons
meillo@0: (':'). Note that this option takes RFC 821 addresses
meillo@0: while <opt>map_h_from_addresses</opt> takes RFC 822 addresses. The
meillo@0: most important difference is that RFC 821 addresses have no full
meillo@0: name.</p>
meillo@0: 
meillo@0: <p>Example:</p>
meillo@0: <p>
meillo@0: map_return_path_addresses =
meillo@0: "john: &lt;jsmith@mail.academic.edu&gt;;
meillo@0: charlie: &lt;cmiller@mx.commercial.com&gt;"
meillo@0: </p>
meillo@0: <p>You can use patterns, eg. * as keys.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>expand_h_sender_address</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>This sets the domain of the sender address as given by the Sender:
meillo@0: header to the same address as in the envelope return path address
meillo@0: (which can be set by either <opt>set_return_path_domain</opt> or <opt>map_return_path_addresses</opt>).
meillo@0: This is for mail clients (eg. Microsoft Outlook) which use this address as the sender
meillo@0: address. Though they should use the From: address, see RFC
meillo@0: 821. If <manref name="fetchmail" section="1" href="http://www.fetchmail.org"/> encounters an unqualified Sender:
meillo@0: address, it will be expanded to the domain of the pop server, which is
meillo@0: almost never correct. Default is true.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>expand_h_sender_domain</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Like <opt>expand_h_sender_address</opt>, but sets the domain only.
meillo@0: Deprecated, will be removed in a later version.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>last_route</opt> = <arg>boolean</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If this is set, a mail which would have been delivered using this
meillo@0: route, but has failed temporarily, will not be tried to be delivered
meillo@0: using the next route.</p>
meillo@0: <p>If you have set up a special route with filters using the lists
meillo@0: 'allowed_rcpt_domains', 'allowed_return_paths', and
meillo@0: 'allowed_mail_locals' or their complements (not_), and the mail
meillo@0: passing these rules should be delivered using this route only, you
meillo@0: should set this to 'true'. Otherwise the mail would be passed to the
meillo@0: next route (if any), unless that route has rules which prevent
meillo@0: that.</p>
meillo@0: <p>Default is false.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>auth_name</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Set the authentication type for ESMTP AUTH authentification.
meillo@0: Currently only 'cram-md5' and 'login' are supported.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>auth_login</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Your account name for ESMTP AUTH authentification.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>auth_secret</opt> = <arg>string</arg></p>
meillo@0: <optdesc>
meillo@0: <p>Your secret for ESMTP AUTH authentification.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>pop3_login</opt> = <arg>file</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If your Mail server requires SMTP-after-POP, set this to a
meillo@0: get configuration (see <manref name="masqmail.get" section="5" href="masqmail.get.5.html"/>).
meillo@0: If you login to the POP server
meillo@0: before you send, this is not necessary.</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>wrapper</opt> = <arg>command</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If set, instead of opening a connection to a remote server, <arg>command</arg> will
meillo@0: be called and all traffic will be piped to its
meillo@0: stdin and from its stdout. Purpose is to tunnel ip traffic, eg. for ssl.</p>
meillo@0: <p>Example for ssl tunneling:</p>
meillo@0: <p>wrapper="/usr/bin/openssl s_client -quiet -connect pop.gmx.net:995 2>/dev/null"</p>
meillo@0: </optdesc>
meillo@0: </option>
meillo@0: 
meillo@0: <option>
meillo@0: <p><opt>pipe</opt> = <arg>command</arg></p>
meillo@0: <optdesc>
meillo@0: <p>If set, and protocol is set to 'pipe', <arg>command</arg> will be
meillo@0: called and the message will be piped to its stdin. Purpose is to use
meillo@0: gateways to uucp, fax, sms or whatever else.</p>
meillo@0: <p>You can use variables to give as arguments to the command, these
meillo@0: are the same as for the mda in the main configuration, see <manref
meillo@0: name="masqmail.conf" section="5" href="masqmail.conf.5.html"/>.</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, and protocol is set to 'pipe', a from line will be prepended to the output stream whenever
meillo@0: a pipe command is called. 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, and protocol is set to 'pipe', each line beginning with 'From '
meillo@0: is replaced with '>From ' whenever a pipe command is called. 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: </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.conf" section="5" href="masqmail.conf.5.html"/>, <manref name="masqmail.get" section="5" href="masqmail.get.5.html"/>
meillo@0: </p>
meillo@0: </section>
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: