Releasing messages from the hold channel

To cause messages sidelined as  in the hold channel  queue area to become eligible for delivery (to be delivered onwards)  once again, set the  user&#x27;s status   and  domain status  once again to  , and then use the   utility&#x27;s    command to release the held messages for  processing. As of Messaging Server 7.0u4, the   utility informs  the Job Controller  of such message release, which for normal messages  usually results in an "immediate" (more-or-less, depending on  current load on the MTA) delivery attempt. (But in some earlier versions, the released message would not get "seen" by the  Job Controller until the next    occurred, whether via an explicit   command,   or via the Job Controller&#x27;s  own automatic, periodic  .)

Note that attempting to release a message for a user who is still marked as " " will merely result in the message again  getting sidelined as   with a temporary error  (recorded in the  MTA message transaction log, and the  message&#x27;s own  delivery history) using the    MTA option&#x27;s text, so by default 452 4.2.1 cannot reenqueue while still held

See also:
 * Hold channel
 * qm utility
 * Job Controller operation
 * cache -sync utility
 * synch_time Option
 * error_text_still_held MTA Option
 * MTA transaction logging