[GH-ISSUE #632] Create Custom Mail Alias for default domain #1019

Closed
opened 2026-03-14 11:30:06 +03:00 by kerem · 10 comments
Owner

Originally created by @xanthos84 on GitHub (Apr 29, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/632

Hi,

why is it not possible to add a new custom mail alias for the default domain?
I also cant add the default domain to the "Domain" tab, because I get the error "is a local domain".

Thank you for clarifiying - as I need to create some custom mail aliases.

Originally created by @xanthos84 on GitHub (Apr 29, 2024). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/632 Hi, why is it not possible to add a new custom mail alias for the default domain? I also cant add the default domain to the "Domain" tab, because I get the error "is a local domain". Thank you for clarifiying - as I need to create some custom mail aliases.
kerem closed this issue 2026-03-14 11:30:11 +03:00
Author
Owner

@dec-mail commented on GitHub (May 11, 2024):

I would like to know too, as i will likely want to do this.

<!-- gh-comment-id:2106050670 --> @dec-mail commented on GitHub (May 11, 2024): I would like to know too, as i will likely want to do this.
Author
Owner

@dec-mail commented on GitHub (May 11, 2024):

Hmm.
TWO WEEKS that was Posted and NO Response at all (from anyone, let alone Addy Support!)

In that case, Addy might be all hype and no Support ... in which case i should prob select a different app for this purpose. Plenty of others, but would still be quite disappointing after spending so much time evaluating and reviewing so many apps.

And, together with the case of my separately posted fatal Addy error (no Verification email) before i can even start, it is not looking good.

<!-- gh-comment-id:2106051395 --> @dec-mail commented on GitHub (May 11, 2024): Hmm. TWO WEEKS that was Posted and NO Response at all (from anyone, let alone Addy Support!) In that case, Addy might be all hype and no Support ... in which case i should prob select a different app for this purpose. Plenty of others, but would still be quite disappointing after spending so much time evaluating and reviewing so many apps. And, together with the case of my separately posted fatal Addy error (no Verification email) before i can even start, it is not looking good.
Author
Owner

@willbrowningme commented on GitHub (May 12, 2024):

@dec-mail This user is requesting a feature for self-hosted instances that is not possible on the hosted (addy.io) instance.

On the hosted addy.io instance you can create custom aliases for your own domain without any issues.

@xanthos84 If you have:

# This allows you to receive emails as a catch-all at the apex domain e.g. *@example.com
ANONADDY_ADMIN_USERNAME=username

set in your .env file where username is your account's username, then you can create custom aliases on the fly for the default domain.

<!-- gh-comment-id:2106173087 --> @willbrowningme commented on GitHub (May 12, 2024): @dec-mail This user is requesting a feature for self-hosted instances that is not possible on the hosted (addy.io) instance. On the hosted addy.io instance you can create custom aliases for your own domain without any issues. @xanthos84 If you have: ``` # This allows you to receive emails as a catch-all at the apex domain e.g. *@example.com ANONADDY_ADMIN_USERNAME=username ``` set in your `.env` file where `username` is your account's username, then you can create custom aliases on the fly for the default domain.
Author
Owner

@xanthos84 commented on GitHub (May 12, 2024):

@willbrowningme thank you for your answer.
I got that line in my .env file, with my username filled in.
but i still cant create a new alias:
image

<!-- gh-comment-id:2106174450 --> @xanthos84 commented on GitHub (May 12, 2024): @willbrowningme thank you for your answer. I got that line in my .env file, with my username filled in. but i still cant create a new alias: <img width="411" alt="image" src="https://github.com/anonaddy/anonaddy/assets/18182913/761c8b0f-af66-46f4-8da5-d352cd4d63e5">
Author
Owner

@xanthos84 commented on GitHub (May 12, 2024):

to clarify: i am using addy since about 2 years now selfhosted... and with the old versions before version 1.0, it was easily possible to create new custom aliases for my domain.
but now since 2 weeks I updated to v1.1.0 its not working anymore.

so i dont think its a feature request from me as you stated.
it seems like a bug in the current version!

<!-- gh-comment-id:2106175138 --> @xanthos84 commented on GitHub (May 12, 2024): to clarify: i am using addy since about 2 years now selfhosted... and with the old versions before version 1.0, it was easily possible to create new custom aliases for my domain. but now since 2 weeks I updated to v1.1.0 its not working anymore. so i dont think its a feature request from me as you stated. it seems like a bug in the current version!
Author
Owner

@willbrowningme commented on GitHub (May 12, 2024):

Adding that to your .env does not allow you to create the aliases manually for the default domain (I need to implement that still).

But it does enable catch-all for your default domain so you don't need to create the alias beforehand.

<!-- gh-comment-id:2106175924 --> @willbrowningme commented on GitHub (May 12, 2024): Adding that to your `.env` does not allow you to create the aliases manually for the default domain (I need to implement that still). But it does enable catch-all for your default domain so you don't need to create the alias beforehand.
Author
Owner

@xanthos84 commented on GitHub (May 12, 2024):

Adding that to your .env does not allow you to create the aliases manually for the default domain (I need to implement that still).

But it does enable catch-all for your default domain so you don't need to create the alias beforehand.

i see. well, thats a pity - because it opens spam mail bots open doors to just send random mails to aliases which are then automatically created.
so best use case was to create custom aliases manually for specific services I am using.

catch all works as long nobody gets a bot sending out spam mails to your domain because they know its catch-all enabled!
so I think it should be really high prioritised to get this feature out... fingers crossed!

<!-- gh-comment-id:2106178375 --> @xanthos84 commented on GitHub (May 12, 2024): > Adding that to your `.env` does not allow you to create the aliases manually for the default domain (I need to implement that still). > > But it does enable catch-all for your default domain so you don't need to create the alias beforehand. i see. well, thats a pity - because it opens spam mail bots open doors to just send random mails to aliases which are then automatically created. so best use case was to create custom aliases manually for specific services I am using. catch all works as long nobody gets a bot sending out spam mails to your domain because they know its catch-all enabled! so I think it should be really high prioritised to get this feature out... fingers crossed!
Author
Owner

@willbrowningme commented on GitHub (May 12, 2024):

Will sort this shortly to allow manual creation of custom aliases at the default domains.

<!-- gh-comment-id:2106178628 --> @willbrowningme commented on GitHub (May 12, 2024): Will sort this shortly to allow manual creation of custom aliases at the default domains.
Author
Owner

@xanthos84 commented on GitHub (May 12, 2024):

thank you so much!

<!-- gh-comment-id:2106179047 --> @xanthos84 commented on GitHub (May 12, 2024): thank you so much!
Author
Owner

@willbrowningme commented on GitHub (May 15, 2024):

Fixed in v1.2.0.

<!-- gh-comment-id:2112278225 --> @willbrowningme commented on GitHub (May 15, 2024): Fixed in [v1.2.0](https://github.com/anonaddy/anonaddy/releases/tag/v1.2.0).
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#1019
No description provided.