SimpleLogin (manage email aliases and dynamically reply as the alias!)
While there is no extension, one can use wildcard aliases - https://docs.cloudron.io/apps/#aliases . So, you can add
blah*and then handout blah1231 or whatever you like.
But I guess one would want to track with a label or equivalent of the created aliases and what they were used for. (That's what I think this app does). One can create some strategy like
blah-service-oneor something like that.
@girish I guess anyone can just strip the
+servicepart from the address quite easily.
I'm trying to think how one would make this work using the same domain but perhaps somehow having different MX records for each server that would look for if an email address is able to receive.
@girish I guess the wildcard solution only works for those receiving emails to a catchall mailbox. Wouldn't work for multiple user's separation of emails on the same domain.
Perhaps there's a way to replicate the Simple Login hooks to work with Cloudron API? That way you get Cloudron mailbox and alias management, and Simple Logins' already developed browser extensions?
email@example.com and firstname.lastname@example.org are not Cloudron Admins, but their mailboxes are hosting in a Cloudron service — both want to sign up to newsletters and make online purchases, without their email address getting onto mailing lists, and without having the +service part being removed to become their main email address.
What email addresses do John and Jane put into those forms?
@marcusquinn you, as the Cloudron admin, would add a wildcard alias for the
email@example.com. This alias can be named
Then, you tell john to use that wildcard alias, however, he wants.
johnservices-srv-three.. However, he wants. Replies will end in his mailbox.
Also, I don't think simplelogin has multiple users either for a custom domain - https://github.com/simple-login/app/discussions/1359 .
@girish OK, sorta makes sense, so basically the Admin has to setup and explain this feature in onboarding, and disposable aliases are manually created, but only removed on request from user to Admin.
Really the convenience of the browser extension is in making unique non-decypherable aliases on the fly in email inputs, eg, if I open the extension on this website (https://bakadesuyo.com) I get this in the extensions:
Multiple domain options:
Or something totally random:
And I can also delete them in the extensions.
I see what you're saying, and I can cope with that for personal use, and could perhaps document it for client use — if anyone would ever care about that sort of thing with a work email address anyway, because spam is usually IT's problem.
So, just really documenting here to show the differences in delivery and user experience.
Given you have A solution, that probably demotes this option to more of a convenience app, than a whole new feature.
We'll probably get it running some other way though, as my attention span is precious, and protecting that from Inbox time-costs is an ongoing need.