On 04/05/2011 12:09 AM, Victor Duchovni wrote:
On Mon, Apr 04, 2011 at 11:51:40PM +0200, Jeroen Geilman wrote:
The only Postfix service that consults the transport table is
trivial-rewrite(8), which in turn is consulted by smtpd(8), cleanup(8),
qmgr(8), ... with the main routing decision made in qmgr(8).
Postfix parameter settings don't get recorded in the queue file as
the message moves through the various stages of processing. Each
service (smtpd(8), cleanup(8), qmgr(8), smtp(8), ...) has its
own view of the configuration settings.
I thought some services could add extra info to queue messages, such as a
content_filter or smtpd proxy ?
These are not main.cf parameter overrides. The access(5) FILTER action
does not override the transport_maps setting in any other service. It
does record transport:nexthop *value* in the queue_file that pre-empts
normal transport lookups, but this is very different from changing some
other service's setting the variable that defines the list of tables to
consult.
Oh I missed that he wanted a completely different set of tables...
sounds like multi-instance time, then.
The queue file containts the message envelope and body, plus a small
amount of metadata that includes DSN attributes, content encoding domain,
... and sometimes a content_filter setting. There are NO main.cf parameter
settings in the queue file.
Didn't mean to imply that there were, thanks for the clarification.
--
J.
