Mercurial > masqmail

comparison man/masqmail.8 @ 258:05fa719b7002

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fixed -oem by removing it ;-) The implemenation of -oem had been very weird. docs/oem-option explains the situation and the fix.
author markus schnalke <meillo@marmaro.de>
date Wed, 01 Dec 2010 18:27:46 -0300
parents 1b25fabdc3cb
children f4117fd5a163
comparison
equal deleted inserted replaced
257:8cca5305e4f0 258:05fa719b7002
126 \fImasqmail \-bp\fP (aka. \fImailq\fR). 126 \fImasqmail \-bp\fP (aka. \fImailq\fR).
127 127
128 .TP 128 .TP
129 \fB\-m\fR 129 \fB\-m\fR
130 130
131 Same as \fB\-om\fR, see below. 131 ``Me too''
132 This switch is ignored as,
133 masqmail never excludes the sender from any alias expansions.
134
135 \fB\-m\fP is an ancient alias for \fB\-om\fP.
132 Kept for compatibility. 136 Kept for compatibility.
133
134 .TP
135 \fB\-oem\fR
136
137 Currently this option makes masqmail behave such:
138
139 If the \fB\-oi\fR ist not also given, always return with a non zero return code.
140
141 It seems as if this current behavior is not like it should be.
142
143 In exim this option makes it behave such:
144
145 .in +4
146 .ll -4
147 If an error is detected while a non-SMTP message is being received
148 (for example, a malformed address),
149 the error is reported to the sender in a mail message.
150 Exim exits with a non-zero return code then,
151 no matter if the error message was successful or not.
152 (In exim, -oee is similar but exim returns successful
153 if the error message had been sent successful.)
154 .ll
155 .in
156
157 The mutt wiki writes about ``sendmail -oi -oem'':
158
159 .in +4
160 .ll -4
161 The mail server (in this case sendmail) will receive the message in input,
162 and will parse it. In case of a malformed message, it will send an error
163 message to the user to whom belongs the MUA trasmitting the message
164 (e.g. user@localhost.localdomain), and it will exit with a non zero exit code:
165 the -oem flag forces the returning of a non zero exit code even in
166 the case the error message has been successfully sent to the local server.
167 .ll
168 .in
169
170 Masqmail's behavior is different in that:
171 First, it does not send such error messages.
172 Second, return non-zero whenever -oem is set (but -oi not).
173 Third, -oi overrules -oem, though as it seems the two options
174 should not affect each other.
175 (Their relationship is just that -oem does only affect non-SMTP
176 messages on stdin, which is the typical use of -oi.)
177 137
178 .TP 138 .TP
179 \fB\-odb\fR 139 \fB\-odb\fR
180 140
181 ``Deliver in Background'' 141 ``Deliver in Background''
193 .TP 153 .TP
194 \fB\-oi\fR 154 \fB\-oi\fR
195 155
196 A dot as a single character in a line does not terminate the message. 156 A dot as a single character in a line does not terminate the message.
197 157
198 .TP 158 The same as \fB\-i\fP.
199 \fB\-om\fR
200
201 ``Me too''
202 Masqmail never excludes the sender from any alias expansions,
203 like if this switch is always set.
204 Specifying this switch changes nothing.
205 159
206 .TP 160 .TP
207 \fB\-oXXX\fR 161 \fB\-oXXX\fR
208 162
209 Any other switch starting with `-o' is ignored. 163 Any other switch starting with `\-o' is ignored.
164 This especially affects \-om, \-oem, \-oee.
210 165
211 .TP 166 .TP
212 \fB\-q [\fIinterval\fB]\fR 167 \fB\-q [\fIinterval\fB]\fR
213 168
214 If not given with an argument, run a queue process, i.e. try to deliver all messages in the queue. 169 If not given with an argument, run a queue process, i.e. try to deliver all messages in the queue.