-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to choose an automatically generated address for a custom subdomain. #5333
Comments
Thanks for logging an issue @RokeJulianLockhart! We actually recommend people to use the non-subdomain addresses wherever possible, and limiting use of the custom subdomain for e.g. situations where you need to come up with an easy-to-remember email address on the spot. The reason for that is that the custom subdomain makes you more identifiable than a regular random address. And theoretically, anyone who knows your custom subdomain can bombard you with emails at different email address (though I don't believe we've seen this happen in practice yet). |
@Vinnl, for me, that's deliberate. I've been using Addy.IO 1 in the stead of Relay, and want to begin using Relay. I use both not as obfuscators, but mere middlemen so that I can organise my mail and prevent spam, not prevent being identified. Being identified is actually quite useful when posting e-mail addresses publicly, since it allows anyone contacting me to not know my ultimate address, yet know they're talking to me due to my subdomain.
The aforementioned service explicitly allows the user to enable to disable that functionality. Does Relay not? Footnotes
|
That's fair enough. And no, as far as I'm aware, at the moment Relay does not yet allow limiting emails sent to your custom subdomain. |
Request
If I generate a mask with my custom subdomain (
@rokejulianlockhart.mozmail.com
), I am unable to choose to have the local part be randomly generated like I can for an address without a subdomain (like[email protected]
).Meta
If of interest, I've ascertained a convenient workaround: use
aran.horse/converters/time/b36
1 to generate the local part, like[email protected]
.You needn't redact anything you consider to be accidentally publicly posted personal information - I've generated addresses specifically for this issue.
You don't seem to have any issue templates configured. It'd save you some triage time if I could tentatively mark my own issues as BRs and/or FRs.
Footnotes
Arancaytar (no date)
ARAN-WEB/SOURCE/CONVERTERS/TIME/B36.HTML.MD
atAE74BEAE55A851706A5093D7F7786C2680F20FA8
·arancaytar/aran-web
, GitHub. Available at:github.com/arancaytar/aran-web/blob/ae74beae55a851706a5093d7f7786c2680f20fa8/source/converters/time/b36.html.md
(Accessed: 20 January 2025). ↩The text was updated successfully, but these errors were encountered: