Scott Sharkey wrote:
> Hi Brian,
>
> I'm editing this to make it a bit shorter.
>
> Brian Evans - Postfix List wrote:
>> Scott Sharkey wrote:
>>> Brian Evans - Postfix List wrote:
>>>> Scott Sharkey wrote:
>
>>>> We need your 'postconf -n' to give more hints about a correct setup.
>>>> (with virtual_ maps explained too)
>>> see below:
>>> local_recipient_maps = $virtual_mailbox_maps,
>>> $virtual_alias_maps,        $alias_maps,
>>> hash:/etc/postfix/relay_recipient_map
>
> dropped the relay_recipient map, but questions remain (see below)

You should not need the $virtual_ either.  If you want to disable
lookups in /etc/passwd, use just $alias_maps to pull in your list maps
you mentioned.
Virtual maps are checked automatically if the recipient domain is listed
as virtual_(alias|mailbox)_domains.

Beware to include things like root (or other service names that receive
mail) in one of the maps or important things like services (e.g. cron)
will not be able to notify you.
>
>>> local_transport = dovecot
>
> put this back to local for the list domains (which are the only local
> mail accounts).
>
>>> myhostname = mail.linuxunlimited.com
>>> mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
>>>
>>> relay_domains = proxy:mysql:/etc/postfix/mysql_relay_domain_map.cf 
>> relay_domains with no relay_recipient_maps parameter? This is not the
>> best way to handle this.
>
> What is? -- I have no way to determine the actual users on the relay
> domain... I'm not actually using any relay domains, now that I've
> moved the mailman lists to local...  But theoretically, I could
> be a backup MX for someone. How do I create/manage a list of
> THEIR recipients...  I was under the impression that I would NOT,
> just accept all and deliver to them, but I can see the flaw in
> that plan...  Not planning on using this, at least not right now,
> so I may just turn it off (came with postfixadmin setup)

relay_domains is for remote systems you trust and are the MX  for.
If you do not keep a relay_recipient_maps listing, you could be a
Backscatter source.

If you cannot get a list of users, use a check_recipient_access map that
returns reject_unverified_recipient for domains that you control.
It is bad practice to set reject_unverified_recipient globally.
>>> transport_maps = proxy:mysql:/etc/postfix/mysql_transport_map.cf
>> Is this trip really necessary?
>
> Not sure... I have dovecot, local, vacation, and potentially relay
> transports, loaded via postfixadmin/mysql.  The dovecot domains are
> virtual, the mail list domains local, vacation and relay are
> special cases.  How do I set the "default" transport to dovecot?
>

The default transport is the one in main.cf for that class (local,
virtual) that the domain belongs to (mydestination, virtual_mumble_domains).
ex. virtual_transport, local_transport

A transport_maps entry is not required when you don't need to change the
default, but it only hurts if it's incorrect in the map.

Brian

Reply via email to