| Current File : //var/qmail/man/cat5/qmail-log.0 |
Standards, Environments, and Macros qmail-log(5)
NNNNAAAAMMMMEEEE
qmail-log - the qmail activity record
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
qqqqmmmmaaaaiiiillll----sssseeeennnndddd prints a series of lines describing its activi-
ties. Each possible line is described below.
SSSSTTTTAAAATTTTUUUUSSSS
ssssttttaaaattttuuuussss:::: llllooooccccaaaallll _l////_L rrrreeeemmmmooootttteeee _r////_R ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is waiting for _l local deliveries and _r
remote deliveries. The concurrency limits are _L and _R.
ssssttttaaaattttuuuussss:::: eeeexxxxiiiittttiiiinnnngggg
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is done.
FFFFAAAATTTTAAAALLLL PPPPRRRROOOOBBBBLLLLEEEEMMMMSSSS
aaaalllleeeerrrrtttt:::: ccccaaaannnnnnnnooootttt ssssttttaaaarrrrtttt:::: ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to prepare itself for delivering
messages; it is giving up. This normally indicates a
serious configuration error, but it can be caused by a
temporary lack of resources.
aaaalllleeeerrrrtttt:::: oooohhhh nnnnoooo!!!! lllloooosssstttt ............
One of the other daemons has died. qqqqmmmmaaaaiiiillll----sssseeeennnndddd will
exit as soon as possible.
SSSSEEEERRRRIIIIOOOOUUUUSSSS PPPPRRRROOOOBBBBLLLLEEEEMMMMSSSS
aaaalllleeeerrrrtttt:::: uuuunnnnaaaabbbblllleeee ttttoooo aaaappppppppeeeennnndddd ttttoooo bbbboooouuuunnnncccceeee
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to record a permanent failure,
usually because the disk is full. This is a very seri-
ous problem; qqqqmmmmaaaaiiiillll----sssseeeennnndddd cannot proceed without record-
ing the results. It will try again in ten seconds.
aaaalllleeeerrrrtttt:::: oooouuuutttt ooooffff mmmmeeeemmmmoooorrrryyyy............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd tried to allocate more memory and failed.
It will try again in ten seconds.
aaaalllleeeerrrrtttt:::: uuuunnnnaaaabbbblllleeee ttttoooo ooooppppeeeennnnddddiiiirrrr............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is having trouble reading a file list from
disk, usually because the system's file descriptor
table is full, but possibly because permissions are set
incorrectly. It will try again in ten seconds.
aaaalllleeeerrrrtttt:::: uuuunnnnaaaabbbblllleeee ttttoooo sssswwwwiiiittttcccchhhh bbbbaaaacccckkkk............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was sent SIGHUP, and it is unable to reenter
the queue directory. This is a very serious problem;
qqqqmmmmaaaaiiiillll----sssseeeennnndddd cannot proceed outside the queue directory.
It will try again in ten seconds.
aaaalllleeeerrrrtttt:::: uuuunnnnaaaabbbblllleeee ttttoooo rrrreeeerrrreeeeaaaadddd............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was sent SIGHUP, but it is unable to read
the new controls. It will continue operating with the
SunOS 5.11 Last change: 1
Standards, Environments, and Macros qmail-log(5)
original controls.
MMMMEEEESSSSSSSSAAAAGGGGEEEESSSS
nnnneeeewwww mmmmssssgggg _m
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is going to preprocess a queued message.
The message number, _m, is its disk inode number. After
a message is removed from the queue, its number can be
reused immediately.
iiiinnnnffffoooo mmmmssssgggg _m:::: bbbbyyyytttteeeessss _b ffffrrrroooommmm
Message _m contains _b bytes; its envelope sender is _s;
it was queued by a user with user ID _u. _q is a long-
term queue identifier, the process ID of the qqqqmmmmaaaaiiiillll----
qqqquuuueeeeuuuueeee that queued the message.
bbbboooouuuunnnncccceeee mmmmssssgggg _m qqqqpppp _q
Message _m had some delivery failures. The long-term
queue identifier of the bounce (or double-bounce) mes-
sage is _q.
ttttrrrriiiipppplllleeee bbbboooouuuunnnncccceeee:::: ddddiiiissssccccaaaarrrrddddiiiinnnngggg ............
Message _m had some delivery failures, but it is already
a double-bounce message, so it must be thrown away.
Triple-bounce messages do not exist.
eeeennnndddd mmmmssssgggg _m
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is about to remove message _m from the queue.
DDDDEEEELLLLIIIIVVVVEEEERRRRIIIIEEEESSSS
ssssttttaaaarrrrttttiiiinnnngggg ddddeeeelllliiiivvvveeeerrrryyyy _d:::: mmmmssssgggg _m ttttoooo
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is telling qqqqmmmmaaaaiiiillll----llllssssppppaaaawwwwnnnn or qqqqmmmmaaaaiiiillll----rrrrssssppppaaaawwwwnnnn to
deliver message _m to one recipient. The delivery
number, _d, starts at 1 and increases by 1 for each new
delivery.
ddddeeeelllliiiivvvveeeerrrryyyy _d:::: ssssuuuucccccccceeeessssssss:::: ............
Delivery _d was successful.
ddddeeeelllliiiivvvveeeerrrryyyy _d:::: ffffaaaaiiiilllluuuurrrreeee:::: ............
Delivery _d failed permanently. The message will
bounce.
ddddeeeelllliiiivvvveeeerrrryyyy _d:::: ddddeeeeffffeeeerrrrrrrraaaallll:::: ............
Delivery _d failed temporarily. This recipient will be
retried later.
ddddeeeelllliiiivvvveeeerrrryyyy _d:::: rrrreeeeppppoooorrrrtttt mmmmaaaannnngggglllleeeedddd,,,, wwwwiiiillllllll ddddeeeeffffeeeerrrr
There is a serious bug in qqqqmmmmaaaaiiiillll----llllssssppppaaaawwwwnnnn or qqqqmmmmaaaaiiiillll----rrrrssssppppaaaawwwwnnnn.
This recipient will be retried later.
WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS
iiiinnnntttteeeerrrrnnnnaaaallll eeeerrrrrrrroooorrrr:::: ddddeeeelllliiiivvvveeeerrrryyyy rrrreeeeppppoooorrrrtttt oooouuuutttt ooooffff
SunOS 5.11 Last change: 2
Standards, Environments, and Macros qmail-log(5)
qqqqmmmmaaaaiiiillll----llllssssppppaaaawwwwnnnn or qqqqmmmmaaaaiiiillll----rrrrssssppppaaaawwwwnnnn has supplied a report on a
nonexistent delivery. This is a serious bug.
qqqqmmmmaaaaiiiillll----cccclllleeeeaaaannnn uuuunnnnaaaabbbblllleeee ttttoooo cccclllleeeeaaaannnn uuuupppp ............
For some reason qqqqmmmmaaaaiiiillll----cccclllleeeeaaaannnn is unable to remove the
indicated file. It will try again later.
ttttrrrroooouuuubbbblllleeee ffffssssyyyynnnncccciiiinnnngggg ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to write to disk the results of
preprocessing a queued message. It will try again
later.
ttttrrrroooouuuubbbblllleeee iiiinnnn sssseeeelllleeeecccctttt
There is an operating system bug.
ttttrrrroooouuuubbbblllleeee iiiinnnnjjjjeeeeccccttttiiiinnnngggg bbbboooouuuunnnncccceeee mmmmeeeessssssssaaaaggggeeee............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to queue a bounce message, usu-
ally because the disk is full. It will try again
later.
ttttrrrroooouuuubbbblllleeee mmmmaaaarrrrkkkkiiiinnnngggg ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to record the result of a suc-
cessful or permanently unsuccessful delivery. This
means that the delivery will be tried again later.
ttttrrrroooouuuubbbblllleeee ooooppppeeeennnniiiinnnngggg ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to open the list of local or
remote recipients for a message. It will try again
later.
ttttrrrroooouuuubbbblllleeee rrrreeeeaaaaddddiiiinnnngggg ............
Either qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to read a recipient list,
or it is unable to read the envelope of a queued mes-
sage, or it is out of memory. Whatever it was doing,
it will try again later.
ttttrrrroooouuuubbbblllleeee wwwwrrrriiiittttiiiinnnngggg ttttoooo ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to preprocess a queued message,
usually because the disk is full. It will try again
later.
uuuunnnnaaaabbbblllleeee ttttoooo ccccrrrreeeeaaaatttteeee ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd was unable to preprocess a queued message,
usually because the disk is out of inodes. It will try
again later.
uuuunnnnaaaabbbblllleeee ttttoooo ooooppppeeeennnn ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to read the envelope of a queued
message for preprocessing. It will try again later.
uuuunnnnaaaabbbblllleeee ttttoooo ssssttttaaaarrrrtttt qqqqmmmmaaaaiiiillll----qqqquuuueeeeuuuueeee............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to queue a bounce message, usually
SunOS 5.11 Last change: 3
Standards, Environments, and Macros qmail-log(5)
because the machine is almost out of memory. It will
try again later. This can also be caused by incorrect
settings of $$$$QQQQMMMMAAAAIIIILLLLQQQQUUUUEEEEUUUUEEEE or errors in a program or
script which $$$$QQQQMMMMAAAAIIIILLLLQQQQUUUUEEEEUUUUEEEE points to.
uuuunnnnaaaabbbblllleeee ttttoooo ssssttttaaaatttt ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to obtain information about a file
that should exist. It will try again later.
uuuunnnnaaaabbbblllleeee ttttoooo uuuunnnnlllliiiinnnnkkkk ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is unable to remove a file. It will try
again later.
uuuunnnnaaaabbbblllleeee ttttoooo uuuuttttiiiimmmmeeee ............
qqqqmmmmaaaaiiiillll----sssseeeennnndddd is about to exit, and it is unable to record
on disk the next scheduled delivery time for a message.
The message will be retried as soon as qqqqmmmmaaaaiiiillll----sssseeeennnndddd is
restarted.
uuuunnnnkkkknnnnoooowwwwnnnn rrrreeeeccccoooorrrrdddd ttttyyyyppppeeee iiiinnnn ............
There is a serious bug in either qqqqmmmmaaaaiiiillll----qqqquuuueeeeuuuueeee or qqqqmmmmaaaaiiiillll----
sssseeeennnndddd.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
qmail-send(8)
SunOS 5.11 Last change: 4