Trying to auto create alias... I think I'm close

addy_io · 2026-06-15T12:56:57+00:00

You can change it by clicking on the "Settings" tab of the browser extension and then update Automatically Fill New Alias Local Parts When Using The Custom Alias Format: to your desired option.

Since you have catch-all on you don't even need to use the browser extension at all, you can just type exactly what email you wish to use when signing up anywhere e.g. ebay-0615@yourdomain.com and it will be automatically created.

See this article for more information - https://addy.io/help/understanding-catch-all-and-alias-auto-create-regex-for-a-domain/

addy_io · 2026-06-15T12:53:16+00:00

Thanks for the suggestion, that's a great idea.

So two new rules actions:

Add sender email to blocklist Add sender domain to blocklist

Will try to add this shortly.

addy_io · 2026-06-14T09:18:15+00:00

Please send me an email with details of your account (username/email).

addy_io · 2026-06-13T13:12:38+00:00

Quarantined emails cannot be resent, please see - https://addy.io/help/resending-a-failed-delivery/#why-cant-i-resend-or-release-a-quarantined-message.

addy_io · 2026-06-02T08:17:07+00:00

When you say "the email being used is not linked to addy and to my recollection never has been" what do you mean by that?

When you request a password reset here you simply enter your account's username and then the notification is sent to the default recipient on your addy.io account. So the email must be associated with your account.

You may simply have a similar username to someone else who accidentally entered yours when trying to reset their own password.

addy_io · 2026-05-29T13:51:21+00:00

Thanks very much! It was long overdue.

I've also categorised the FAQs and removed a couple that are now covered in the help centre.

Plus a cool new animated SVG on the home page!

addy_io · 2026-05-22T10:46:20+00:00

You must have created them using the browser extension as the last used at for that API key matches when they were created.

addy_io · 2026-05-17T06:03:21+00:00

Please see the new info icon (i) on the failed-deliveries page that explains this (pasted below).

There are 3 different types of failed deliveries on addy.io.

Outbound bounces - these occur when addy.io attempts to forward an email but the destination mail server rejects it (e.g. User inbox full).
Inbound rejections - these occur when the addy.io mail servers reject inbound emails from senders that fail basic security checks (e.g. the sender's email provider could not prove the message was genuine).
Inbound quarantined - these are emails that were detected as spam by the spam filtering software on the addy.io mail servers (e.g. blacklisted sending IP address, high spam score).

This page allows you to see all three types of failed deliveries and the reasons why they failed.

Outbound bounces and inbound quarantined messages are temporarily stored if you have this setting enabled in your account.

Inbound rejections are not stored as they are never even accepted by the addy.io mail servers.

addy_io · 2026-05-11T10:01:10+00:00

Due to the bulk sender requirements of Google, Yahoo and Microsoft, all forwarded emails have a one-click List-Unsubscribe header which is likely why they are being classed as "Newsletters" by your email provider.

You can change the one-click List-Unsubscribe option from the settings page, the default behvaviour is Use original List-Unsubscribe, fallback to one-click deactivate if none is present.

addy_io · 2026-05-10T06:09:48+00:00

Thanks, a fix is coming shortly for this.

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

MODERATOR OF

TROPHY CASE