Reprocess channel transaction log entries

Note that MTA message transaction   records  involving the   channel require a bit of special reading, as  one of the whole goals of use of   is to preserve the  "original" source channel name (for purposes of access  checks, etc.), and this then affects the message transaction  log entries. For instance, in the case of a message enqueued (received) by the   channel and automatically deferred to the     channel (perhaps because, say, the LDAP server is not currently  responding, or because a Sieve " " must  be performed), relevant MTA message transaction log entries, with  the MTA option   set, might have the rough form: date-time-1 SMTP-process-id tcp_intranet reprocess  E ...  date-time-2 reprocess-id    tcp_intranet  tcp_local  E ...  date-time-3 reprocess-id    reprocess                D ... That is, the   channel&#x27;s enqueue onwards is recorded (and  access checked, if appropriate) as if it were an enqueue from the  original enqueueing channel---but if you have    set, then  you can see by the process-id that it&#x27;s actually the    channel  that did that second enqueue.

Prior to 8.0, the  channel handled  Sieve " " messages;  as of 8.0, Sieve " " messages instead go through the   channel.

See also:
 * Reprocess channel operation as prior channel
 * Process and reprocess channels
 * MTA transaction log entry format
 * log_process MTA Option
 * Sieve redirect action