Hello William
the solution I provided works even if you use the mailaddress (like in my example donald@cokl.eu) for many recipients - I've tried this as well. I've added donald@cokl.eu to several users as an alternative, an alias that they should receive emails for, and they all received the mail addressed for donald@cokl.eu. So - isn't that what an alias is supposed to do?! This works perfect for approaches like with the famous info@abcd.efg, or support@abcd.efg. Just add these mail-address to all the users who should receive email for these addresses. One interesting question arises though - lets say I had configured 3 with same alias - what if the first of them read the email? Will this emails be marked as "read" on the inboxes of the second and third, too?
And BTW - cokl.eu is a virtual domain on this server, and I didn't edit the virtual_users file with the donald-address. However, the primary address for every virtual user is in place in the file like:
howard@cokl.eu userid@localhost.
However, how is vacation messaging configured?!
There are several different mechanisms for hosting multiple domains. It is possible to mix techniques if you must handle different domains in different ways.
To determine which technique or techniques you need, you must decide how postfix should deliver messages for virtual domains. There are two important considerations that influence how you should configure postfix for hosting multiple domains:
- Should your domains have separate namespaces? For esample, should mail for the two addresses info@blue.com and info@red.com go to the same mailbox or separate ones? If they go to the same mailbox name them shared domains, and if the are delivered into different mailboxes then call it seperate domains.
- Does every user require a system account? We'll make the distinction between system accounts that are real Unix accounts on your system, and virutal accounts. With virtual accounts, users can have mailboxes on your server, but don't otherwise log in to the system and don't require an entry in /etc/passwd.
With all that said you can consider 4 ways how postfix can handle mail for virtual domains:
- shared domains with system accounts
- separate domains with system accounts
- separate domains with virtual accounts
- virtual domains with a proprietary message store not managed by postfix
Your POP/IMAP server will be a major factor in deciding which tehnique you need. If your POP/IMAP server does not understand virtual domains, then it will most likely require that you have asystem accounts for all addresses - that's not the case with dovecot which runs on mavericks.
More of what I just cited can be found in the book "Postfix: The Definitive Guide" available from O'Reilly, written by Kyle D. Dent - which I would recommend reading first before messing around with Apples implementation of postfix - which is a little different - so to say.