The logging code lives outside the individual table drivers and with "_maps" parameters that support multiple tables, above any individual table lookup.
Oh I see. Well without rearchitecting the logging it seems this could be made more intuitive for the case where all of the maps in a sequence are skipped (e.g. my case with a single regexp table). If I understand right the non-indexed skip is implemented by the 'continue' at global/maps.c:199, so a flag could be added to track whether execution has passed line 199 and if not, the log statement at 221 could be skipped. Whether this would actually be a net benefit I'm not sure, but it seemed worth mentioning.
Some tables support partial keys, other do not, as documented under in regexp_table(5):
Ah, didn't see this before in the man page. Thoughts on updating the documentation for check_recipient_access to mention the indexed/non-indexed distinction? Thoughts on more fully documenting which table types do partial key lookups? Jakob _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
