On Tue, Jun 18, 2013 at 11:30:28AM +0100, Z? Loff wrote:
>
> [...]
>
> OK, mapping to a local user worked. I was trying to mimic my postfix
> setup, with a few virtual users/domains (and a few aliases) each with
> its own maildir. I managed to do this with:
>
> table users { foo => zeloff, goo => zeloff }
> accept for domain foo.bar virtual <users> deliver to maildir \
> "/mail/foo.bar/%{rcpt.user}"
>
> If I understand correctly, the mapping to a local user is necessary (at
> least) to define the ownership of the Maildir files. On my production
> postfix server all virtual Maildirs are owned by the same 'vmail' user,
> so there is no need to map every single virtual recipient to a local
> user (note that with my setup all virtual maildirs end up being owned by
> the same user as well)...
I don't really understand what you mean, because if you map your virtual
boxes to the 'vmail' user on Postfix, you essentially do:
table users { foo => vmail, goo => vmail }
unless I didn't understand what you meant
> Is there any other reason for the mapping to a local user being
> mandatory (honest question, no criticism implied)?
>
a mapping is required to determine the id under which a delivery will
take place. the user however is not necessarily a local user, it can
be a virtual userbase defined in a file or within smtpd.conf
> Anyway, I think an external MDA might be more suited to my needs...
>
Could be, but using virtual and userbase some very tricky virtual setups
can be achieved. Maybe you should explain your use-case in details :-)
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this email because you are subscribed to mailing list:
[email protected]
To unsubscribe, send mail with subject:
[[email protected]] unregister
