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