Nikolaos Milas:
> On 9/3/2012 2:09 ??, Reindl Harald wrote:
>
> > his "postconf -n" does not contain "proxy_read_maps"
> > if you think it is not needed at all than postfix has a bug
> >
> > i did the follwoing long a go because exavtly the same messages
> > in the error log after start using "proxy:mysql" and because
> > "proxymap service is not configured for table" is really clear
> >
> > there is currently no magic in postfix let this work
> > without configure "proxy_read_maps" what the OP did not
>
> I would like to ask whether any changes are anticipated in coming
> Postfix versions (e.g. 2.9.2) to correctly support the "auto"
> proxy_read_maps feature (I can wait a bit), or we should proceed with
> explicitly defining proxy_read_maps, on a per table basis, as Reindl
> suggested.
As of Postfix 2.9, the default proxy_read/write_maps settings are:
% bin/postconf -df proxy_read_maps proxy_write_maps
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps
$virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains
$relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps
$recipient_canonical_maps $relocated_maps $transport_maps $mynetworks
$sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps
$alias_maps
proxy_write_maps = $smtp_sasl_auth_cache_name $lmtp_sasl_auth_cache_name
$address_verify_map $postscreen_cache_map
If any parameters are missing from this list, I can add them with
the next patchlevel update. Just let me know what is missing.
Wietse
