> Here, the trivial-rewrite address resolver is intializing for > > - "normal" routing, which uses transport_maps, default_transport, > and so on. > > - "address verification" routing, which uses address_verify_transport_maps, > address_verify_default_transport, and so on.
According to the documentation: address_verify_transport_maps (default: $transport_maps) address_verify_default_transport (default: $default_transport) So if I set: address_verify_transport_maps = address_verify_default_transport = smtp transport_maps = tcp:127.0.0.1:9998 default_transport = smtp:[127.0.0.1:25] Would this avoid MAIL FROM command from sending requests to trivial-rewrite? Also, "sender_dependent_default_transport_maps" would check the sender domain, but according to the documentation, the order should be 1) $transport_maps 2) $sender_dependent_default_transport_maps 3) $default_transport Would this be the cause for this query? > transport_maps and address_verify_transport_maps may be different, > therefore the trivial-rewrite initialization code makes one "*" > query for each table. The code does not try to be clever when > 'normal" and "address verification" settings have the same value. > The "*" result is cached in-process for 30 seconds. In my case this is set to empty (address_verify_transport_maps = ), but still looks like it is hitting the service. BR, Rafael _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
