FYI, BH no longer allows the user of aliases due to concerns with spam. The mail servers were slowing to a crawl before they implemented this policy a few years ago.
The only option I see to do this is to pipe mail to a email distribution program that is sent to a specific address.
Hmmm. I just managed to do it.
Instead of creating a mailbox called firstname.lastname@example.org I went to forwarders and added a line for each e-mail address that webmaster forwards to;
So email@example.com forwards to firstname.lastname@example.org
Then a second line email@example.com forwards to firstname.lastname@example.org
And then a third line, that forwards email@example.com to an e-mail address outside @mydomain.com
I sent an e-mail to firstname.lastname@example.org and all three got it.
Well, that works, too!
However, while a few forwarders from the same address might not be an issue, the only question would be whether having a much larger number of forwarders (read: hundreds) would tax the mail servers. Someone who knows more than I on that subject might have the answer.
Nice to find this thread (but not that aliases are unsupported!) though the work-around is interesting.
I have the opposite problem, many-to-one aliasing, instead of one-to-many aliasing. It used to all work like magic from /etc/aliases on the previous host.
I have existing domain aliases username1@domain, username2@domain etc that all need to forward to either a single email box on my bluehost domain or a single mailbox on an outside domain.
Do you think I will need to bring up real email accounts (with appropriate forwarding/deletion) on the bluehost domain for each "alias"?
Ugh, clumsy, but it might work... it's dozens, not hundreds...
A forwarder within your account is just pointing to the email account where the email is to be delivered and so having 1000 forwarders to one account wouldn't be any worse than having 1000 separate accounts and would possibly be more efficient in server processing as it probably doesn't have as much overhead for forwarders as for separate accounts.
I just found an oddity that bears mention, that BillH on bluehost live chat helped me debug.
I was testing forwarders from a gmail account, the same account to which the forwards were destined. The gmail message would land in the bluehost box alright, but never showed back up in the gmail account. Everything looked good, traces looked correct, simple mail from gmail to bluehost and vice-versa was fine, and despite not getting the mail forwarded back, the gmail messages appeared in the bluehost mailbox.
But BillH's mail test DID forward, so then I tried from yet another source address, and it also correctly forwarded to my gmail, proving bluehost forwarders were working fine all along.
Bottom line: don't try to test a bluehost forwarder from a gmail account to which it forwards, because bluehost sends it, but google drops it. And not in spam. Silently. How odd, perhaps an over-ambitious mail-loop detection algorithm...
Now if I just had the domain up and happy, I wouldn't have to test from gmail! Catch-22, thought y'all might like to know... :-)