starred/anonaddy

Fork 0

mirror of https://github.com/anonaddy/anonaddy.git synced 2026-04-24 21:55:52 +03:00

[GH-ISSUE #790] [Bugs] Attaching recipients to new aliases using keys #1104

New issue

Open

opened 2026-03-14 11:44:49 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 11:44:49 +03:00

Owner

Originally created by @AS98765 on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/790

v1.3.5

On-the-fly:

Recipient is assigned as desired.
However, it is then saved under “Aliases” with the key. In this case, as xxx+1@yyy.addy.io instead of xxx@yyy.addy.io.
“Click to copy” also copies the wrong alias with +1.
Under “Delete”, “Forget” and "Send" the alias is correctly displayed again as xxx@yyy.addy.io.
It is also displayed correctly in the email banner.

Browser:

No assignment is made under “Create Alias” in the browser in the custom alias format.

If it only works On-the-fly, at least the help text under “Recipients” -> “Key” is unclear.

Originally created by @AS98765 on GitHub (Nov 13, 2025). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/790 v1.3.5 1. On-the-fly: - Recipient is assigned as desired. - However, it is then saved under “Aliases” with the key. In this case, as xxx+1@yyy.addy.io instead of xxx@yyy.addy.io. - “Click to copy” also copies the wrong alias with +1. - Under “Delete”, “Forget” and "Send" the alias is correctly displayed again as xxx@yyy.addy.io. - It is also displayed correctly in the email banner. 2. Browser: - No assignment is made under “Create Alias” in the browser in the custom alias format. If it only works On-the-fly, at least the help text under “Recipients” -> “Key” is unclear.

kerem commented

2026-03-14 11:44:55 +03:00

Author

Owner

@willbrowningme commented on GitHub (Nov 14, 2025):

Thanks, attaching recipients to aliases using their "Key" only works when creating aliases on-the-fly.

So do you think it should be saved without the key? But what then if you used xxx+1@yyy.addy.io to register an account or something and in the future forgot the full address, as xxx@yyy.addy.io isn't the exact email used to register.

@willbrowningme commented on GitHub (Nov 14, 2025): Thanks, attaching recipients to aliases using their "Key" only works when creating aliases on-the-fly. So do you think it should be saved without the key? But what then if you used xxx+1@yyy.addy.io to register an account or something and in the future forgot the full address, as xxx@yyy.addy.io isn't the exact email used to register.

kerem commented

2026-03-14 11:45:00 +03:00

Author

Owner

@AS98765 commented on GitHub (Nov 19, 2025):

Difficult.

The case you describe is one that I hadn't considered at all.
On the other hand, when responding (in rare cases), I would automatically use the wrong email address, xxx@yyy.addy.io.
In the case of account registration, this is all rather strange.

If it stays as it is, at least the help text should be adjusted. Also with regard to the exclusive on-the-fly functionality.

@AS98765 commented on GitHub (Nov 19, 2025): Difficult. The case you describe is one that I hadn't considered at all. On the other hand, when responding (in rare cases), I would automatically use the wrong email address, xxx@yyy.addy.io. In the case of account registration, this is all rather strange. If it stays as it is, at least the help text should be adjusted. Also with regard to the exclusive on-the-fly functionality.

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#1104

No description provided.

Rows
Columns