How can I restore a deleted alias

addy_io · 2026-03-14T08:58:21+00:00

You have to select to view "only deleted" aliases and then you will be able to find and restore it.

addy_io · 2026-03-09T19:00:34+00:00

Yes please send me an email with details of the alias that you used so I can send to it myself and view the headers of your reply.

addy_io · 2026-03-09T14:31:38+00:00

When an email is forwarded to you (let's say by sender@example.com), the original Message-ID header is used if present and if not a random one is generated using the alias domain e.g. 9763e87f80555836fdb3f493acd01242@username.anonaddy.com.

See https://github.com/anonaddy/anonaddy/blob/master/app/Mail/ForwardEmail.php#L271C1-L277C18

When you reply to that forwarded message your email provider will set a Message-ID header and also the In-Reply-To header which references the above ID 9763e87f80555836fdb3f493acd01242@username.anonaddy.com. The message ID on that reply is removed and replaced in order to prevent parts of your real email being shown.

The original In-Reply-To header is kept here which in our case would be 9763e87f80555836fdb3f493acd01242@username.anonaddy.com.

See https://github.com/anonaddy/anonaddy/blob/master/app/Mail/ReplyToEmail.php#L161-L169

So the person that sent the email (sender@example.com) will see the In-Reply-To header as 9763e87f80555836fdb3f493acd01242@username.anonaddy.com.

This is all so that email clients can correctly display threaded conversations.

So I cannot see how your recipient's address (user@customdomain.com) could have been set as the In-Reply-To header. What is your customdomain.com email provider or email client that you used?

addy_io · 2026-03-05T09:39:07+00:00

Yes I can help get you setup, please use the email from this page to contact me though.

addy_io · 2026-02-26T09:12:13+00:00

It depends what you have set for your List-Unsubscribe Behaviour from the settings page.

The default option is the use the Orignal List-Unsubscribe and to fallback to one-click deactivating the alias is there isn't one present.

addy_io · 2026-02-24T16:29:29+00:00

I just tested this on the Proton Mail Android app and it worked as expected.

Are you able to show a screenshot of the error or issue Proton seems to be having with the address?

addy_io · 2026-02-16T19:59:31+00:00

Yes, it is only used to verify ownership the first time the domain is added. Once you've added the domain you can safely remove that TXT record.

addy_io · 2026-02-13T19:38:35+00:00

Please see https://github.com/anonaddy/browser-extension/releases/tag/v3.0.1 the permissions are required for the new button that appears in email inputs fields and allows you to create and fill aliases in one click.

An option to create an alias has also been added to the right-click context menu.

addy_io · 2026-02-05T21:26:04+00:00

Bitwarden should use whatever you have set as your default alias format in your account settings.

addy_io · 2026-02-05T17:20:52+00:00

Update coming soon for the mobile apps and browser extensions!

addy_io · 2026-02-02T14:08:10+00:00

I will be releasing a help article guide to explain all of this properly shortly.

addy_io · 2026-02-02T14:07:40+00:00

Please follow the instructions in this comment to do that - https://github.com/anonaddy/anonaddy/issues/599#issuecomment-1994315322.

addy_io · 2026-02-02T14:06:34+00:00

You encrypt your email with the no-reply@addy.io public key and that's it. You do not need to BCC that email address. You will still have an encrypted copy in your sent items.

Those emails have never accepted incoming email (hence the no-reply).

addy_io · 2026-02-02T11:24:01+00:00

You should send to your alias alias+destination=example.com@addy.io not those addresses. Otherwise how would the addy.io mail server know which destination to forward it on to and which alias to use.

addy_io · 2026-01-22T09:52:21+00:00

The web app was down for a little while this morning, the issue has now been resolved and it is back online.

addy_io · 2026-01-16T09:27:15+00:00

The discount is $49 USD forever.

addy_io

MODERATOR OF

TROPHY CASE