This example illustrates the case of a message routed through the conversion channel. The site is assumed to have a CONVERSIONS mapping table such as:
CONVERSIONS IN-CHAN=tcp_local;OUT-CHAN=l;CONVERT Yes
This example assumes option settings of LOG_FILENAME=1 and LOG_MESSAGE_ID=1.
04-Feb-1998 00:06:26.72 tcp_local conversion E 9 (1) amy@siroe.edu rfc822;bert@sesta.com bert@sesta.com imta/queue/conversion/ZZ01IT5UAMZ4QW98518O.00 <01IT5UALL14498518O@siroe.edu> 04-Feb-1998 00:06:29.06 conversion l E 9 (2) amy@siroe.edu rfc822;bert@sesta.com bert imta/queue/l/ZZ01IT5UAOXLDW98509E.00 <01IT5STUMUFO984Z8L@siroe.edu> 04-Feb-1998 00:06:29.31 conversion D 9 (3) amy@siroe.edu rfc822;bert@sesta.com bert imta/queue/conversion/ZZ01IT5UAMZ4QW98518O.00 <01IT5UALL14498518O@siroe.edu> 04-Feb-1998 00:06:32.62 l D 9 (4) amy@siroe.edu rfc822;bert@siroe.com bert imta/queue/l/ZZ01IT5UAOXLDW98509E.00 <01IT5STUMUFO984Z8L@siroe.edu> |
The message from external user amy@siroe.edu comes in addressed to the l channel recipient bert@sesta.com. The CONVERSIONS mapping entry, however, causes the message to be initially enqueued to the conversion channel (rather than directly to the l channel).
The conversion channel runs and enqueues the message to the l channel.
Then the conversion channel can dequeue the message (delete the old message file).
And finally the l channel dequeues (delivers) the message.