mail domain alias

gosha

Did not found the way to add mail domain alias, e.g. emails themselves are only being created in the primary domain but exists in all aliased domains?

Adam

Domain aliases are not yet supported but we have an open feature request for this. You will need to create the alias for each domain.

gosha

Adam for each address in the each domain? Second question, can I use a@a.com user to send mails as a@b.com via Enhance controlled mail server, b.com is an alias for a.com ?

Rich

@gosha Yes you can, I have done it with a domain recently that had 2 inboxes, inbox@a.com and inbox@b.com and I've used the alias feature to provide the b.com alias. I've emailed from and recvied to inbox@b.com even though it's all going to inbox@a.com.

Cavet to be aware of is domain aliass for mail. So I don't believe this will suport DKIM for b.com, but so far it's worked in terms of delivering mail. It just likely supports less features and is a best effort approach.

Once SNI for domains works nice for mail delivery, an extension might be to look at the feasability of DKIM/SPF for domain b.com so that it's more feature reach for it's receiving/delivery.

Short and dirty it's doable but not nessarily optimal. Ok for a catch all on domain inbox@b.com in my opinion.

Rich

To follow up I did a little extra testing and even from protonmail I've emailed to b.com and I only have a.com attached as webmail. Received it, replied and even the reply hasn't triggered warnings in protonmail.com (Good!)

Give it a try and see, I was lucky in that there was only 1 old inbox to deal with on b.com and I can migrate it's mail to a.com and call this job done.

Rich

That being said I also setup inbox@c.com which has never existed. This works internally i.e. domains on the same server, but externally inbox@c.com isn't working at least externally with say protonmail.( fails to deliver)

I believe this is more a DNS issue for c.com for me than it being unsupported as b.com works both externally and internally, and if setup in webmail for an alias identiy it replies as if from inbox@b.com even externally.

By webmail I also don't mean roundcube, but a version of roundloop called snappymail added into nextcloud connected to dovcot.

Don't overlook the lack of DKIM for b,com/c.com as that can and will possibly cause issues with deliverabilty.

@Adam is very knowledgeable, I am just sharing what I have tested working for me.

Machiel92

Are e-mail alliasses now automatically?
For example:
info@Domain1.com exists.

If I send an e-mail to info@domain2.com (alias of domain1.com) it should automatically receive in mailbox info@domain1.com.

I'm curious if this works 🙂

Adam

No, this is not yet possible. You need to create the aliases manually.

gosha

Adam Is it a planned feature?

kess

Regarding Aliases,
would it be possible to consider also for example a mailbox with main address a.mail@domain.com that has aliases like b.mail@domain.com, c.mail@domain.com, etc ?
Now we have to create forwarders in order to achieve that...

gosha

may be the support of the forward like *@a.com -> *b.com would be enough solution

gosha

During the migration i'm stuck with 5 cleints with 50+ addresses each with at least 2 domain alises, like dom.ee, and alised with dom.eu and dom.com. In current config I will have to create the at lease 100 forwards for each client, it's amazing )

gosha

Hello again. Did not found any info, it this feature is planned or not? Is it possible to move it upward in the list? We have a few large domains to migrate with 3-7 domain aliases. It is really not good to create the forwards for each address in each alias domain