Page 107 - Mercury Manual.book

Workflow and Implementation 102
Deferred jobs

• If the recipient appears to be a valid local address but Mercury cannot determine the
mailbox directory for the user (this often happens when the underlying user database is
locked, as in the first case described above).
• If there is an active Network Personality Module, and it indicates to Mercury that it can-
not successfully attach to a server or resource required for delivery (this can happen if
Mercury is servicing a remote NetWare server that is temporarily out of licenses).
• If Mercury could not find a name for the .CNM file that was not already in use. Mercury
tries generating names up to 30 times, and uses algorithms that give a high degree of col-
lision avoidance, so this is a fairly unlikely scenario.
• If Mercury could not create the .CNM file for the message but all other aspects of the
delivery were normal. This condition typically indicates that Mercury does not have
enough rights to create files in the user’s mailbox directory, and in such a case, the job
will eventually expire and be returned to the sender.
• If a write error occurred while the .CNM file was being written to the user’s mailbox
directory; this is usually caused by a user exceeding quota, or a volume becoming full.
• If Mercury could not rename the .CNM file after finishing writing the message. To pre-
vent clients such as MercuryP or Pegasus Mail from picking up the message while it is
still being written, Mercury initially creates the file without the .CNM extension, then
renames it when it has finished writing it. If Mercury fails 30 times to rename the file, it
will defer the job. As with file creation, this type of error is usually caused by insuffi-
cient rights in the mailbox directory.