3 qmail-log \- the qmail activity record
6 prints a series of lines describing its activities.
7 Each possible line is described below.
8 .SH "STARTING AND STOPPING"
12 is ready to deliver messages.
14 .B local deliveries will be put on hold
15 The local concurrency limit is 0, so
17 will not perform any local deliveries.
19 .B remote deliveries will be put on hold
20 The remote concurrency limit is 0, so
22 will not perform any remote deliveries.
24 .B number of deliveries left before exiting: ...
26 wants to exit as soon as possible,
27 usually because it was sent a
29 but it has to wait for some deliveries to finish.
30 It will not start any new deliveries.
37 .B alert: cannot start: ...
39 is unable to prepare itself for delivering messages;
41 This normally indicates a serious configuration error,
42 but it can be caused by a temporary lack of resources.
44 .B alert: oh no! lost ...
45 One of the other daemons has died.
47 will exit as soon as possible.
48 .SH "SERIOUS PROBLEMS"
50 .B alert: unable to append to bounce message...
52 is unable to record a permanent failure,
53 usually because the disk is full.
54 This is a very serious problem;
56 cannot proceed without recording the results.
57 It will try again in ten seconds.
59 .B alert: out of memory...
61 tried to allocate more memory and failed.
62 It will try again in ten seconds.
64 .B alert: unable to opendir...
66 is having trouble reading a file list from disk,
67 usually because the system's file descriptor table is full,
68 but possibly because permissions are set incorrectly.
69 It will try again in ten seconds.
71 .B alert: unable to switch back...
74 and it is unable to reenter the queue directory.
75 This is a very serious problem;
77 cannot proceed outside the queue directory.
78 It will try again in ten seconds.
80 .B alert: unable to reread...
83 but it is unable to read the new controls.
84 It will continue operating with the original controls.
89 is going to preprocess a queued message.
92 is its disk inode number.
93 After a message is removed from the queue,
94 its number can be reused immediately.
96 .B info msg \fIm\fB: bytes \fIb\fB from <\fIs\fB> qp \fIq\fB uid \fIu\fB
102 its envelope sender is
104 it was queued by a user with user ID
107 is a long-term queue identifier,
108 the process ID of the
110 that queued the message.
112 .B bounce msg \fIm\fB qp \fIq\fB
115 had some delivery failures.
116 The long-term queue identifier of the bounce (or double-bounce) message
120 .B triple bounce: discarding ...
123 had some delivery failures,
124 but it is already a double-bounce message,
125 so it must be thrown away.
126 Triple-bounce messages do not exist.
136 .B starting delivery \fId\fB: msg \fIm\fB to ...
147 starts at 1 and increases by 1 for each new delivery.
149 .B delivery \fId\fB: success: ...
154 .B delivery \fId\fB: failure: ...
158 The message will bounce.
160 .B delivery \fId\fB: deferral: ...
164 This recipient will be retried later.
166 .B delivery \fId\fB: report mangled, will defer
167 There is a serious bug in
171 This recipient will be retried later.
174 .B internal error: delivery report out of range
178 has supplied a report on a nonexistent delivery.
179 This is a serious bug.
181 .B qmail-clean unable to clean up ...
184 is unable to remove the indicated file.
185 It will try again later.
187 .B trouble fsyncing ...
189 was unable to write to disk the results of preprocessing a queued message.
190 It will try again later.
193 There is an operating system bug.
195 .B trouble injecting bounce message...
197 was unable to queue a bounce message,
198 usually because the disk is full.
199 It will try again later.
201 .B trouble marking ...
203 was unable to record the result of a successful or permanently
204 unsuccessful delivery.
205 This means that the delivery will be tried again later.
207 .B trouble opening ...
209 was unable to open the list of local or remote recipients
211 It will try again later.
213 .B trouble reading ...
216 is unable to read a recipient list,
217 or it is unable to read the envelope of a queued
218 message, or it is out of memory.
219 Whatever it was doing, it will try again later.
221 .B trouble writing to ...
223 was unable to preprocess a queued message,
224 usually because the disk is full.
225 It will try again later.
227 .B unable to create ...
229 was unable to preprocess a queued message,
230 usually because the disk is out of inodes.
231 It will try again later.
233 .B unable to open ...
235 is unable to read the envelope of a queued message
237 It will try again later.
239 .B unable to start qmail-queue...
241 is unable to queue a bounce message,
242 usually because the machine is almost out of memory.
243 It will try again later.
245 .B unable to stat ...
247 is unable to obtain information about a file that should exist.
248 It will try again later.
250 .B unable to unlink ...
252 is unable to remove a file.
253 It will try again later.
255 .B unable to utime ...
258 and it is unable to record on disk
259 the next scheduled delivery time for a message.
260 The message will be retried as soon as
264 .B unknown record type in ...
265 There is a serious bug in either