I second this, would love to be able to use my self-hosted installation of AnonAddy.
I was hyped by the SimpleLogin integration announcement until I learned that
- No custom app url, so does not work for selfhosted instances, and
- generated email addresses in Bitwarden don’t use your custom settings; ie, in SimpleLogin, when I generate an email it is [email protected]. Would be great if either this setting was added or if Bitwarden was able to get those settings from the api (this I doubt)
Thanks everyone, I’ve passed the feedback along to the team
Hi. I am using SimpleLogin and my bitwarden Chrome extension is correctly generating aliases with my custom domain but I had to change the default domain for aliases in the SimpleLogin settings.
Only problem I have with the Chrome extension is that it seems to use the domain name of my bitwarden selfhosted server to generate the alias (so I got someting like [email protected]) instead of the domain of the opened webpage.
Agreed, I added this several weeks ago. Custom forwarded e-mail alias URL
I guess you worded it better than I.
Can I request similar functionality for self-hosted/custom domain AnonAddy instances? Or should I file a separate feature request?
Hey @bingh0 I’ve updated this title to be inclusive of all forwarded email alias integrations.
I second this feature, as I would like to integrate this with my Mailcow server.
I am imagining a simple configuration interface that allows for adding a custom URL that will get POSTed to with the desired username once a new alias needs to be generated. That way, with a simple wrapper script, every application can easily be integrated. Bonus points if you’re able to configure the POST body or auth headers.