lanedirt

Thank you for your kind words! Nice idea about the header exchanger, I’ll add it to my list to explore as an option for this feature.

I’m looking forward to your feedback whenever you have had the chance to try AliasVault. Much appreciated! :-)

Thanks for your comment!

The official cloud hosted variant currently offers unlimited *@aliasvault.net addresses. However I’ll be adding more domains as time goes on as certain companies don’t always like the idea of aliases and tend to start blacklisting.

The self-hosted variant allows you to attach as many of your own domains that you want, and then you can choose which domain you want to generate an alias with from the GUI.

The ability to connect your own private domains to the cloud hosted variant is also on the roadmap and will be added in the coming 2-3 weeks. This will allow you to move from/to different services without losing access to your email aliases.

Thanks for your feedback! Yes the primary reason for it being receive only right now is to combat spam. I am considering options where self-hosted users and cloud users (perhaps as a premium option) will be able to do this though.

One of the big challenges then would be that self hosting outgoing email servers has historically always been tricky thing in terms of email deliverability. A lot of big email providers block entire residential IP ranges, so more often than not emails tend to be delivered straight to spam.

But there are other options I’m considering such as being able to integrate AliasVault with external email servers (e.g. MS365 or Google) for both receiving and sending. Or leaving the receiving as-is but integrating with an external SMTP relay for email sending.

I’m actively working on improving AliasVault and iterating quickly, so all feedback is appreciated. :-)