Re: is a local IMAP server "remote"? 
On Wed, 2008-02-13 at 11:29 -0500, Jorey Bump wrote:
> Stefan Palme wrote, at 02/13/2008 11:05 AM:
> 
> > after reading another recent thread on this list I have question:
> > 
> > Wietse wrote:
> >> Virtual domains are not the correct solution for this.
> >>
> >> For mail that is delivered elsewhere use relay_domains and
> >> relay_recipient_maps, and perhaps transport_maps.
> > 
> > I have a setup running postfix and an IMAP server on the same host.
> > Several domains are configured using virtual_alias_domains and
> > virtual_alias_maps (see postconf -n at the end). Transport to
> > the local IMAP server happens using LMTP.
> > 
> > Although the IMAP server is obviously not "remote", LMTP is a
> > "remote" protocol, so for this setup Wietse's statement would
> > apply, too (because "mail ist delivered elsewhere"). 
> > Does it mean, I better should use relay_domains for this setup?
> 
> No, your mail is not *delivered* elsewhere.
> 
> > local_recipient_maps = $alias_maps, hash:/etc/postfix/imapusers
> 
> Why not the default? What does the imapusers file do for you?

The default setting includes UNIX system accounts and the aliases
file, but because the IMAP server gets its account information from
an external source (an LDAP server), it is possible to write an
email to dbd@XXXXX.de, where "bob" is neither a UNIX account nor
an alias, but a valid IMAP account. 

The /etc/postfix/imapusers contains all those usernames like "bob".


> > mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
> > virtual_alias_domains = hash:/etc/postfix/virtualdomains
> > virtual_alias_maps = hash:/etc/postfix/virtualaliases
> 
> These are typical settings. You shouldn't need to change them.

Ok, just listed here because in my real setup the virtual_alias_*
settings contain some more tables (e.g. mailman's virtual aliases)...

Thanks!
-stefan-


