On 2012-03-02 Karol Babioch wrote: > I've got a server, which can be found at the domain "example.com" > (including a PTR record for reverse DNS lookups). > > Now I want to run a mailserver for "example.com", but I don't want to > create local users, but instead use virtual mailboxing. > > Furthermore I've got the domain "example.net" which I want to be a > mail host for - once again using virtual mailboxing. > > Emails to "i...@example.com" should be stored (using dovecot) in > "/var/spool/mail/example.com/info". The emails for the "example.net" > domain should be treated the same way (e.g. > "/var/spool/mail/example.net/info"). > > Now what would be the best way to deal with these kind of problem? > From my understanding the documentation seems to assume that virtual > mailboxing is only used for "additional" domains, but not for the > "main" one.
True, and the recommended way of handling things. However, the "main" domain of the server can be the server itself, and you can restrict the valid local mailboxes via $local_recipient_maps: ----8<---- mydestination = $myhostname local_recipient_maps = $alias_maps ---->8---- I'd suggest to have $alias_maps look somewhat like this: ----8<---- mailer-daemon: postmaster postmaster: root hostmaster: root abuse: root root: mailad...@example.com ---->8---- For the virtual mailbox domain setup follow the examples in the Virtual Domain Hosting Howto [1]. [1] http://www.postfix.org/VIRTUAL_README.html Regards Ansgar Wiechers -- "Abstractions save us time working, but they don't save us time learning." --Joel Spolsky
