mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 06:05:55 +03:00
[GH-ISSUE #421] [Enhancement] Disallow inclusion of plus address when creating alias. #877
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#877
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RokeJulianLockhart on GitHub (Jan 20, 2023).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/421
I accidentally included a plus address in an alias that I created. This hasn't been a problem, since sending mail with a different plus address (obviously as replacement to the original rather than appended) and without any plus address deliver mail to the base address without problem.
However, I see no benefit to including it in the original address in the interface, whereas it certainly may cause confusion, as it did for me, since the mail delivery subsystem treats it as one would probably hope.
Summarily:
Disallow creating
mailTo:base-address+plus-address@anonaddy.com.Perhaps, correct to
mailTo:base-address@anonaddy.com.I don't consider this to be important, but I certainly believe that it's worth implementing.
@willbrowningme commented on GitHub (May 26, 2023):
The + extension of an alias is recorded in a separate database column when a standard alias is first created.
This is mainly so that you do not forget that you included one when first making the alias.
If you created a new alias
first+ext@johndoe.anonaddy.comas your login for a site but then AnonAddy removed the+extbit and didn't record it then you may later try to login withfirst@johndoe.anonaddy.comforgetting that you had used an extension.@RokeJulianLockhart commented on GitHub (May 26, 2023):
Yeah. @willbrowningme, I don't believe that we should retroactively remove them – just prevent creation of new ones with them (since, as you state, they're able to be overriden anyway, so they're not actually part of the address).
@willbrowningme commented on GitHub (May 26, 2023):
It is not overridden if you send a message to the same alias with a different plus extension. Only the one that was present when it was first created it stored.
If I prevent the creation of new ones with any extension then their will be no record of the full email used when creating a login etc.
@RokeJulianLockhart commented on GitHub (May 26, 2023):
@willbrowningme,
It is: If I create username+one@anonaddy.com but send a message to username+two@anonaddy.com, the message is not sent to username+one+two@anonaddy.com. It's sent to username+two@anonaddy.com. That's the entire crux of this issue – that that behaviour is deceptive.
How? Not if you prevent creation of them. All that the form has to do is either disallow entry of the sub-address, or reject the sub-address when the e-mail address is created.
@willbrowningme commented on GitHub (May 26, 2023):
With subaddressing (plus extensions) the underlying email address is the same. So in the eyes of AnonAddy
username+one@anonaddy.comis the same alias asusername+two@anonaddy.com.It doesn't matter what extension you add, the message will still go to the same underlying alias
username@anonaddy.com.Appending multiple extensions and sending to
username+one+two@anonaddy.comis not the expected behaviour.You can inspect the headers of any forwarded message and view the
X-AnonAddy-Original-To:to see if it was sent to the alias including a plus extension.https://www.codetwo.com/admins-blog/plus-addressing/
Many users choose to use plus extensions for their aliases and if I disabled it then it would also break the feature described here https://anonaddy.com/blog/add-recipients-to-aliases-at-creation-and-new-uuid-aliases/.
@RokeJulianLockhart commented on GitHub (May 26, 2023):
Alright. I didn't know of that nifty feature. Thanks.