From: Wietse Venema (no email)
Date: Sun Feb 01 2004 - 17:21:41 EST
Matthias Andree:
> Before this gets out of hand, let's recollect and consolidate some
> things (some I'm not 100% sure about):
>
> 1. when using a custom master.cf transport for a domain via
> transport_maps, does it matter if I use (mydestination,
> local_recipient_maps) or (relay_domains, relay_recipient_maps)?
You have to somehow define its address class, so that Postfix knows:
1 - What domains to accept mail for (mandatory).
2 - What recipients exist (optional).
(1) Requires listing the domain name in mydestination,
virtual_mumble_domains or relay_domains. (2) follows from (1).
> Either seems to work fine, I'd personally choose the one that fits
> the contractual status best. I. e. if I deliver my own domain to
> maildrop, I'd list it in mydestination, if I deliver somebody else's
> domain to maildrop, I'd list it in relay_*.
If Postfix does final delivery, mydestination or virtual_mumble_domains
are the politically correct place to list the domain name. Relaying
implies forwarding off-host.
> 3. when using a local(8) transport with mailbox_command, the
> (mydestination, local_recipient_maps) is the natural (if not the
> only) choice.
>
> So this effectively means that the only real decision the user has to
> make is if he wants his maildrop recipients subjected to alias_maps and
> .forward redirection/expansion.
Right. Hence the two main ways of using Cyrus and Maildrop: via
local(8) or not. However, nothing stops you from delivering hosted
domains through local(8) into cyrus or maildrop.
> The setup flow plan (and what should be the essence of a
> MAILDROP_README) would then be (realizing it isn't really
> maildrop specific):
>
> Choose if you need /etc/aliases and ~USER/.forward expansion
>
> if yes -> put maildrop as mailbox_command
> put the domain into mydestination
> put the recipient maps into local_recipient_maps
> (convenient if user owns mailbox)
OK.
> ALTERNATIVE:
> if yes -> put maildrop as mailbox_transport
> put the domain into mydestination
> put the recipient maps into local_recipient_maps
> create a maildrop transport in master.cf
> (convenient for virtual users)
Caution: mailbox_transport and fallback_transport should be used
when you receive mail for local addresses not in /etc/passwd. This
variant is more useful if you're going to host domains virtually
through the local delivery agent.
> if no -> put the domain into relay_domains
> put the domain into transport
> put the recipient maps into relay_recipient_maps
> create a maildrop transport in master.cf
I would recommend using virtual_mailbox_domains, virtual_transport
and virtual_mailbox_maps.
Wietse
> The current maildrop examples for master.cf can be taken from the
> current readme.
>
> Comments solicited.
>
> --
> Matthias Andree
>
> Encrypt your mail: my GnuPG key ID is 0x052E7D95
>
>
|
|
|