transport_maps and lookups reason


I have 'transport_maps = mysql:/etc/postfix/' in
configuration and want to understand the reason of every db lookup as I
have some actions in mysql server based on queries count. Please explain

When sending single email these lookups are made:

1. "*"
2. "source@emal"
3. "destination@email"
4. "destination@email"

Especially what directives cause lookups over "mail from" address and
why destination address is called twice?

I have single mysql inclusion in configuration.

postfix 3.3.0



Re: transport_maps and lookups reason

By Viktor Dukhovni at 05/15/2018 - 09:48

This is typically cached, and not queried for each and every message.

Postfix performs the lookups it needs to perform. We document
the configuration interface. The exact timing and multiplicity
of the underlying lookups is an internal detail. Postfix is
modular and some lookups are made in more than once in separate

Re: transport_maps and lookups reason

By Bokhan Artem at 05/15/2018 - 10:00

Thank you.

Can source email (mail from) lookup be disabled when using
transport_maps? Any ideas? As I understand transport_maps should rely on
destination address when sender depended transport maps are not used.

15.05.2018 20:48, Viktor Dukhovni пишет:

Re: transport_maps and lookups reason

By Viktor Dukhovni at 05/15/2018 - 10:16

As Wietse suggested, it would be prudent to post your configuration.

If you have any "check_sender_access" restrictions, those will trigger
a transport lookup on the sender, since transport lookup actually
resolves a resipient to (transport, nexthop, address) with the address
suitably normalized.

Re: transport_maps and lookups reason

By Wietse Venema at 05/15/2018 - 09:30

Bokhan Artem:
TO REPORT A PROBLEM see <a href="" title=""></a>

TO (UN)SUBSCRIBE see <a href="" title=""></a>

Thank you for using Postfix.