Mercurial > masqmail
annotate man/masqmail.route.5 @ 347:53cf6be5843a
Minor refactoring
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Thu, 14 Jul 2011 11:15:27 +0200 |
parents | fe00f7952a7c |
children | 08932c629849 |
rev | line source |
---|---|
335
ef346dc67514
updated dates and version
markus schnalke <meillo@marmaro.de>
parents:
325
diff
changeset
|
1 .TH masqmail.route 5 2011-08-27 masqmail-0.3.3 "File Formats" |
34 | 2 |
0 | 3 .SH NAME |
4 masqmail.route \- masqmail route configuration file | |
34 | 5 |
6 | |
0 | 7 .SH DESCRIPTION |
8 | |
34 | 9 This man page describes the syntax of the route configuration files of \fBmasqmail (8)\fR. |
10 Their usual locations are in \fI/etc/masqmail/\fR. | |
0 | 11 |
311
e230bcd0f1c6
removed protocol option from route config
meillo@marmaro.de
parents:
291
diff
changeset
|
12 Mail will be sent with the SMTP protocol to its destination, unless |
e230bcd0f1c6
removed protocol option from route config
meillo@marmaro.de
parents:
291
diff
changeset
|
13 `pipe' is given. |
e230bcd0f1c6
removed protocol option from route config
meillo@marmaro.de
parents:
291
diff
changeset
|
14 In this case the message will be piped to the given program. |
0 | 15 |
311
e230bcd0f1c6
removed protocol option from route config
meillo@marmaro.de
parents:
291
diff
changeset
|
16 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
17 .SH ROUTE CONDITIONS |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
18 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
19 .TP |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
20 \fBallowed_senders\fR = \fIlist\fR |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
21 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
22 This is a semicolon `;' separated list of envelope sender addresses. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
23 Messages which have one of these addresses as the return path (= mail |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
24 from) are allowed to use this route |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
25 (if not also in \fBdenied_senders\fR). |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
26 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
27 Glob patterns containing `?' and `*' can be used. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
28 The special item "<>" matches the null sender address |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
29 (eg. failure notices or delivery notifications). |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
30 If the pattern doesn't contain an `@', it is seen as a pattern for the |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
31 local part only. |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
32 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
33 Example: \fImeillo;*@*example.org;web*@example.com\fP |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
34 |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
35 (``meillo'' equals ``meillo@*'', i.e. the local part.) |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
36 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
37 .TP |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
38 \fBdenied_senders\fR = \fIlist\fR |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
39 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
40 This is a semicolon `;' separated list of envelope sender addresses. |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
41 Messages which have one of these addresses as the return path (= |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
42 mail from) will not |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
43 be sent using this route (even if also in \fBallowed_senders\fR). |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
44 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
45 Glob patterns containing `?' and `*' can be used. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
46 The special item "<>" matches the null sender address |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
47 (eg. failure notices or delivery notifications). |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
48 If the pattern doesn't contain an `@', it is seen as a pattern for the |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
49 local part only. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
50 |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
51 Example: (see \fIallowed_senders\fP) |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
52 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
53 .TP |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
54 \fBallowed_recipients\fR = \fIlist\fR |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
55 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
56 A list of envelope recipient addresses where mail can be sent to using |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
57 this route. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
58 This is for example useful if you use this route configuration when connected to another LAN via ppp. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
59 Glob patterns containing `?' and `*' can be used. |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
60 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
61 Example: \fI*@example.org;*@*foo.bar\fP |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
62 |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
63 (See also examples for \fIallowed_senders\fP) |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
64 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
65 .TP |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
66 \fBdenied_recipients\fR = \fIlist\fR |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
67 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
68 A list of envelope recipient addresses where mail will not be sent to |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
69 using this route. |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
70 This is for example useful if you send mail directly (\fBmail_host\fR is not set) |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
71 and you know of hosts that will not accept mail from you because they use a dialup list |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
72 (eg. \fBhttp://maps.vix.com/dul/\fR). |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
73 \fBdenied_recipients\fR overrules \fBallowed_recipients\fR. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
74 Glob patterns containing `?' and `*' can be used. |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
75 |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
76 Example: \fI*@spamblocker.example.org\fP |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
77 |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
78 (See also examples for \fIallowed_senders\fP) |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
79 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
80 .TP |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
81 \fBlast_route\fR = \fIboolean\fR |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
82 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
83 If this is set, a mail which would have been delivered using this route, |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
84 but has failed temporarily, will not be tried to be delivered using the next route. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
85 |
317
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
86 If you have set up a special route with filters using the lists |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
87 `allowed_recipients' and `allowed_senders' or their complements |
55b7bde95d37
reworked allowed and denied addrs for routes
meillo@marmaro.de
parents:
316
diff
changeset
|
88 (denied_), |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
89 and the mail passing these rules should be delivered using this route only, |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
90 you should set this to `true'. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
91 Otherwise the mail would be passed to the next route (if any), |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
92 unless that route has rules which prevent that. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
93 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
94 Default is false. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
95 |
318
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
96 .TP |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
97 \fBconnect_error_fail\fR = \fIboolean\fR |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
98 |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
99 If this is set, a connection error (or if a pipe command could not be |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
100 executed) will cause a mail delivery to fail, ie. it will be bounced. |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
101 If it is unset, it will just be defered. |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
102 |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
103 Default is false. |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
104 The reason for this is that masqmail is designed for non permanent internet connections, |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
105 where such errors may occur quite often, and a bounce would be annoying. |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
106 |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
107 For the default local_net route it is set to true. |
290da1595311
connect_error_fail affects pipe commands too
meillo@marmaro.de
parents:
317
diff
changeset
|
108 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
109 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
110 .SH SMTP CONFIGURATION |
0 | 111 |
34 | 112 .TP |
113 \fBmail_host\fR = \fIstring\fR | |
0 | 114 |
34 | 115 This is preferably the mail server of your ISP. |
116 All outgoing messages will be sent to this host which will distribute them to their destinations. | |
117 If you do not set this mails will be sent directly. | |
118 Because the mail server is probably `near' to you, mail transfer will be much faster if you use it. | |
0 | 119 |
120 You can optionally give a port number following the host name and a colon, eg mail_host="mail.foo.com:25". | |
34 | 121 |
0 | 122 .TP |
34 | 123 \fBresolve_list\fR = \fIlist\fR |
0 | 124 |
34 | 125 Specify the method how the domain of the server is resolved. |
126 Possible values are dns_mx, dns_a, byname. | |
127 For `dns_mx', the domain is assumed to be an MX pointer to a list of host names, | |
128 these will be tried each in order (lowest preference value first, equal preference values in random order). | |
129 For `dns_a', the domain is assumed to be an A pointer. | |
130 For `byname', the library function \fBgethostbyname(3)\fR will be used. | |
0 | 131 |
132 The default is "dns_mx;dns_a;byname". | |
34 | 133 |
0 | 134 .TP |
34 | 135 \fBhelo_name\fR = \fIstring\fR |
0 | 136 |
34 | 137 Set the name given with the HELO/EHLO command. If this is not set, |
138 \fBhost_name\fR from \fImasqmail.conf\fR will be used, | |
139 if the \fBdo_correct_helo\fR option (see below) is unset. | |
0 | 140 |
141 .TP | |
34 | 142 \fBdo_correct_helo\fR = \fIboolean\fR |
0 | 143 |
34 | 144 If this is set, masqmail tries to look up your host name as it appears |
145 on the internet and sends this in the HELO/EHLO command. | |
146 Some servers are so picky that they want this. | |
147 Which is really crazy. | |
148 It just does not make any sense to lie about ones own identity, | |
149 because it can always be looked up by the server. | |
150 Nobody should believe in the name given by HELO/EHLO anyway. | |
151 If this is not set, \fBhost_name\fR from \fImasqmail.conf\fR or as given with | |
152 the \fBhelo_name\fR (see above) will be used. | |
0 | 153 |
154 .TP | |
222 | 155 \fBinstant_helo\fR = \fIboolean\fR |
156 | |
157 If this is set, masqmail does not wait for the greeting of the SMTP server | |
158 after opening the connection. | |
159 Instead it says EHLO right away (ESMTP is assumed). | |
160 Use this option with wrappers that eat the 220 greeting of the SMTP server. | |
337
fe00f7952a7c
Minor fixes in man pages, reported by lintian(1)
markus schnalke <meillo@marmaro.de>
parents:
335
diff
changeset
|
161 Common examples are STARTTLS wrappers, like `openssl s_client \-starttls smtp ...'. |
222 | 162 |
163 If this option is set and a 220 greeting is received though, | |
164 everything should still work. | |
165 Please don't rely on that and keep in mind that RFC 2821 says that the client | |
166 SHOULD wait for the 220 greeting of the server. | |
167 | |
168 Default: false | |
169 | |
170 .TP | |
34 | 171 \fBdo_pipelining\fR = \fIboolean\fR |
0 | 172 |
34 | 173 If this is set to false, masqmail will not use ESMTP PIPELINING, |
174 even if the server announces that it is able to cope with it. | |
175 Default is true. | |
0 | 176 |
34 | 177 You do not want to set this to false unless the mail setup on the |
178 remote server side is really broken. | |
179 Keywords: wingate. | |
0 | 180 |
34 | 181 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
182 .TP |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
183 \fBauth_name\fR = \fIstring\fR |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
184 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
185 Set the authentication type for ESMTP AUTH authentication. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
186 Currently only `cram-md5' and `login' are supported. |
0 | 187 |
188 .TP | |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
189 \fBauth_login\fR = \fIstring\fR |
0 | 190 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
191 Your account name for ESMTP AUTH authentication. |
0 | 192 |
34 | 193 .TP |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
194 \fBauth_secret\fR = \fIstring\fR |
34 | 195 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
196 Your secret for ESMTP AUTH authentication. |
0 | 197 |
34 | 198 .TP |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
199 \fBwrapper\fR = \fIcommand\fR |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
200 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
201 If set, instead of opening a connection to a remote server, |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
202 \fIcommand\fR will be called and all traffic will be piped to its stdin and from its stdout. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
203 Purpose is to tunnel ip traffic, eg. for ssl. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
204 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
205 Example for SMTP over SSL tunneling: |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
206 .nf |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
207 wrapper="/usr/bin/openssl s_client \-quiet \-connect mail.gmx.net:465 2>/dev/null" |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
208 .fi |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
209 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
210 SMTP over SSL is supported since masqmail-0.1.8. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
211 It is marked obsolete by the IETF but is still in use. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
212 |
0 | 213 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
214 Example for encryption with STARTTLS (RFC-3207): |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
215 .nf |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
216 # don't forget the instant_helo, otherwise it won't work |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
217 instant_helo=true |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
218 wrapper="/usr/bin/openssl s_client \-quiet \-starttls smtp \-connect mail.gmx.net:25 2>/dev/null" |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
219 .fi |
0 | 220 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
221 This is supported since masqmail-0.2.28. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
222 STARTTLS supersedes SMTP over SSL. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
223 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
224 Note for openssl: |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
225 Ensure that stderr is redirected. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
226 Do *not* use \-crlf in the wrapper command, because masqmail does already insert CRLF. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
227 However, you might want to specify \-crlf if you want to test your wrapper command |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
228 interactively on the command line. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
229 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
230 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
231 .SH PIPE CONFIGURATION |
34 | 232 |
0 | 233 .TP |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
234 \fBpipe\fR = \fIcommand\fR |
0 | 235 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
236 \fIcommand\fR will be called and the message will be piped to its stdin. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
237 Purpose is to use gateways to uucp, fax, sms or whatever else. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
238 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
239 You can use variables to give as arguments to the command, |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
240 these are the same as for the mda in the main configuration, see \fBmasqmail.conf(5)\fR. |
34 | 241 |
0 | 242 .TP |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
243 \fBpipe_fromline = \fIboolean\fR |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
244 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
245 Only if `pipe' is used. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
246 A from line will be prepended to the output stream whenever a pipe command is called. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
247 Default is false. |
0 | 248 |
316
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
249 .TP |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
250 \fBpipe_fromhack = \fIboolean\fR |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
251 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
252 Only if `pipe' is used. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
253 Each line beginning with `From ' is replaced with `>From ' whenever a pipe command is called. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
254 You probably want this if you have set \fBpipe_fromline\fR above. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
255 Default is false. |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
256 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
257 |
d596ac8b5afb
heavy restructuring of masqmail.route(5) (sections)
meillo@marmaro.de
parents:
311
diff
changeset
|
258 .SH ADDRESS REWRITE RULES |
0 | 259 |
34 | 260 .TP |
261 \fBset_h_from_domain\fR = \fIstring\fR | |
0 | 262 |
34 | 263 Replace the domain part in `From:' headers with this value. |
264 This may be useful if you use a private, outside unknown address on your local LAN | |
141 | 265 and want this to be replaced by the domain of the address of your email address on the internet. |
34 | 266 Note that this is different to \fBset_return_path_domain\fR, see below. |
0 | 267 |
268 .TP | |
138
80b207e8b8af
documented, yet undocumented, set_h_reply_to_domain config option
meillo@marmaro.de
parents:
95
diff
changeset
|
269 \fBset_h_reply_to_domain\fR = \fIstring\fR |
80b207e8b8af
documented, yet undocumented, set_h_reply_to_domain config option
meillo@marmaro.de
parents:
95
diff
changeset
|
270 |
80b207e8b8af
documented, yet undocumented, set_h_reply_to_domain config option
meillo@marmaro.de
parents:
95
diff
changeset
|
271 Same as \fBset_h_from_domain\fP, but for the `Reply-To' header. |
80b207e8b8af
documented, yet undocumented, set_h_reply_to_domain config option
meillo@marmaro.de
parents:
95
diff
changeset
|
272 |
80b207e8b8af
documented, yet undocumented, set_h_reply_to_domain config option
meillo@marmaro.de
parents:
95
diff
changeset
|
273 .TP |
34 | 274 \fBset_return_path_domain\fR = \fIstring\fR |
0 | 275 |
34 | 276 Sets the domain part of the envelope from address. |
277 Some hosts check whether this is the same as the net the connection is coming from. | |
278 If not, they reject the mail because they suspect spamming. | |
279 It should be a valid address, because some mail servers also check that. | |
280 You can also use this to set it to your usual address on the internet | |
281 and put a local address only known on your LAN in the configuration of your mailer. | |
282 Only the domain part will be changed, the local part remains unchanged. | |
283 Use \fBmap_return_path_addresses\fR for rewriting local parts. | |
0 | 284 |
34 | 285 .TP |
286 \fBmap_h_from_addresses\fR = \fIlist\fR | |
287 | |
288 This is similar to \fBset_h_from_domain\fR, but more flexible. | |
289 Set this to a list which maps local parts to a full RFC 822 compliant email address, | |
290 the local parts (the keys) are separated from the addresses (the values) by colons (`:'). | |
0 | 291 |
292 Example: | |
223 | 293 .nf |
0 | 294 map_h_from_addresses = "john: John Smith <jsmith@mail.academic.edu>; charlie: Charlie Miller <cmiller@mx.commercial.com>" |
223 | 295 .fi |
0 | 296 |
297 You can use patterns, eg. * as keys. | |
34 | 298 |
0 | 299 .TP |
34 | 300 \fBmap_h_reply_to_addresses\fR = \fIlist\fR |
0 | 301 |
34 | 302 Same as \fBmap_h_from_addresses\fR, but for the `Reply-To:' header. |
0 | 303 |
304 .TP | |
34 | 305 \fBmap_h_mail_followup_to_addresses\fR = \fIlist\fR |
0 | 306 |
34 | 307 Same as \fBmap_h_from_addresses\fR, but for the `Mail-Followup-To:' header. |
308 Useful when replying to mailing lists. | |
0 | 309 |
310 .TP | |
34 | 311 \fBmap_return_path_addresses\fR = \fIlist\fR |
0 | 312 |
34 | 313 This is similar to \fBset_return_path_domain\fR, but more flexible. |
314 Set this to a list which maps local parts to a full RFC 821 compliant email address, | |
315 the local parts (the keys) are separated from the addresses (the values) by colons (`:'). | |
316 Note that this option takes RFC 821 addresses while \fBmap_h_from_addresses\fR takes RFC 822 addresses. | |
317 The most important difference is that RFC 821 addresses have no full name. | |
0 | 318 |
319 Example: | |
223 | 320 .nf |
0 | 321 map_return_path_addresses = "john: <jsmith@mail.academic.edu>; charlie: <cmiller@mx.commercial.com>" |
223 | 322 .fi |
0 | 323 |
324 You can use patterns, eg. * as keys. | |
34 | 325 |
0 | 326 .TP |
34 | 327 \fBexpand_h_sender_address\fR = \fIboolean\fR |
0 | 328 |
34 | 329 This sets the domain of the sender address as given by the Sender: header |
330 to the same address as in the envelope return path address | |
331 (which can be set by either \fBset_return_path_domain\fR or \fBmap_return_path_addresses\fR). | |
332 This is for mail clients (eg. Microsoft Outlook) which use this address as the sender address. | |
333 Though they should use the From: address, see RFC 821. | |
334 If \fBfetchmail(1)\fR encounters an unqualified Sender: address, | |
335 it will be expanded to the domain of the pop server, which is almost never correct. | |
336 Default is true. | |
337 | |
0 | 338 .TP |
34 | 339 \fBexpand_h_sender_domain\fR = \fIboolean\fR |
0 | 340 |
34 | 341 Like \fBexpand_h_sender_address\fR, but sets the domain only. |
342 Deprecated, will be removed in a later version. | |
343 | |
344 | |
0 | 345 .SH AUTHOR |
346 | |
34 | 347 Masqmail was written by Oliver Kurth. |
348 It is now maintained by Markus Schnalke <meillo@marmaro.de>. | |
0 | 349 |
95
e01fed4846e4
masqmail's homepage moved prog.marmaro.de/masqmail -> marmaro.de/prog/masqmail
meillo@marmaro.de
parents:
57
diff
changeset
|
350 You will find the newest version of masqmail at \fBhttp://marmaro.de/prog/masqmail/\fR. |
26
607221b0dac1
added myself as maintainer; updated URL of the website
meillo@marmaro.de
parents:
24
diff
changeset
|
351 There is also a mailing list, you will find information about it at masqmail's main site. |
0 | 352 |
34 | 353 |
0 | 354 .SH BUGS |
355 | |
34 | 356 Please report bugs to the mailing list. |
0 | 357 |
358 .SH SEE ALSO | |
359 | |
192 | 360 \fBmasqmail(8)\fR, \fBmasqmail.conf(5)\fR |