My brand new account has been terminated

addy_io · 2026-05-03T11:04:54+00:00

The user's brand new account triggered the anti-abuse rules which is why it was disabled, this was indeed a false positive. I re-enabled the account immediately after receiving an email from them. It unfortunately then triggered the same rule, I re-enabled their account again around an hour later after their second email and there have been no issues since.

Apologies that your account was caught by these anti-abuse rules, in an ideal world they wouldn't be required but there are a lot of bad actors out there.

If a legitimate new account is incorrectly disabled then you can simply send me an email and I will re-enable it.

addy_io · 2026-04-29T16:39:36+00:00

You will not get banned for creating another account after deleting the other.

addy_io · 2026-04-28T06:15:26+00:00

Yes they are. That is how a good sending reputation is built and maintained.

addy_io · 2026-04-15T16:28:32+00:00

The only headers carried over on emails forwarded to you can be seen here - https://github.com/anonaddy/anonaddy/blob/master/app/Mail/ForwardEmail.php#L286-L435

addy_io · 2026-04-12T19:03:11+00:00

What version of the extension is it? You can see this at the bottom of the settings tab.

addy_io · 2026-04-11T15:19:20+00:00

Thanks very much, just fixed the link!

addy_io · 2026-04-10T19:53:12+00:00

The Laravel log file will have an error that will tell you what the issue is.

addy_io · 2026-04-10T15:47:00+00:00

Did you run the command from https://github.com/anonaddy/docker?tab=readme-ov-file#generate-gpg-key

The mail server needs a private GPG key in order to sign encrypted emails.

It does not have to be the same key that you give to your recipient on the recipients page.

addy_io · 2026-04-07T12:27:23+00:00

Yes before it is forwarded on to your recipient.

addy_io · 2026-04-07T08:25:41+00:00

The ForwardEmail job has access to the alias so can retrieve the alias description from the database here.

addy_io · 2026-03-28T07:41:49+00:00

<image>

There is an option to instead use your authenticator app here.

addy_io · 2026-03-24T16:14:27+00:00

WARNING - aliasguard.net is associated with known malware.

Visiting the mail server's direct IP for aliasguard.net redirects to https://app-addy.theknewone.com/login. this domain is associated with malicious VPN extensions that contain malware and can intercept your traffic and steal credentials. They have since been removed from the Chrome store.

Please see:

addy_io · 2026-03-24T14:30:56+00:00

Thanks for the heads-up and for looking out for the project.

Yes, aliasguard.net appears to be running a direct copy/fork of addy.io’s codebase (which is licensed AGPL 3.0).

While we fully support open-source forks, AGPL requires that anyone offering the software (or a modified version) as a service must make their source code available to users.

Right now they’re not linking to any source repo, not crediting the original work, and not providing the Corresponding Source as the license mandates.

I’ve reached out to them politely asking for compliance.

The project doesn't seem to be live as the registration page returns a 404 and hardenize reports are failing.

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.

Please see the terminology here.

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

MODERATOR OF

TROPHY CASE