--On Wednesday, April 10, 2013 1:27 AM +0000 Viktor Dukhovni
<postfix-us...@dukhovni.org> wrote:
On Tue, Apr 09, 2013 at 04:56:28PM -0700, Quanah Gibson-Mount wrote:
The main issue right now is that it has:
virtual_transport = error
which I was told makes little sense, so I'm trying to correct our
configuration.
Actually, it is not always a bad idea. If you have a virtual_mailbox
domain, solely for the purpose of recipient validation:
indexed = ${default_database_type}:${config_directory}/
virtual_mailbox_domains = example.com
virtual_mailbox_maps = ${indexed}vmbox
and if delivery to real users in example.com is always via LMTP or
some other transport that requires an explicit user mapping (say
to a specific IMAP server, ...) then it may make sense to set:
virtual_transport = error:5.1.1 User unknown
transport_maps = ${indexed}transport
with:
/etc/postfix/vmbox:
lu...@example.com ok
/etc/postfix/transport:
lu...@example.com lmtp:inet:imap.example.com:24
with the result that mail to <lu...@example.com> is delivered to
the virtual mailbox, while mail for <bo...@example.com> is not
only rejected by smtpd(8) (since bogus is not in virtual_mailbox_maps),
but also bounces if generated locally, since it resolves to the
error transport without the need to contact the LMTP server (which
may in some cases be configured to create mailboxes on the fly).
This said, I would take a different approach:
...
Thanks Viktor, this looks interesting.
I'm assuming I can do all of this via LDAP rather than flat files? We have
customers with thousands of domains, and number of which may be aliases for
various of the defined domains, which is why we query all of this
information from LDAP. Any solution that requires using flat files is a
nonstarter.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
