You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be beyond the scope of this extension, but maybe you'll consider it.
A backend that allows the creation of a multiuser instance, because currently all aliases within the same domain name are shared globally, but it would be great if there was a middle-software in charge of managing user's accounts and serving them only their respective aliases. This would also mean that the one in charge of managin the api is the server and only the server, which I guess would be good for security.
Solution idea
Not a developer here, but I'm thinking a database with every user and its designated aliases could be implemented, and of course a whole new API to manage the requests client-server-cloudflare. I think this is a lot, but it would be such a cool thing to have for self-hosters, because currently, the self-hosted email scene is basically dead because of the problem of untrusted ip's, and given that probably 80% of self-hosters have a domain-name, at least for me, this would be a great implementation.
Additional info
No response
The text was updated successfully, but these errors were encountered:
Hi, that's a great idea. I had similar thoughts in the past, but never got around to play around with them. The approach would to store aliases in Cloudflare's D1 database and handle all incoming emails through Workers, which would forward them to the corresponding alias receiver address. I'll think about this further and maybe try it out after making some progress with v2.
Feature Description
This may be beyond the scope of this extension, but maybe you'll consider it.
A backend that allows the creation of a multiuser instance, because currently all aliases within the same domain name are shared globally, but it would be great if there was a middle-software in charge of managing user's accounts and serving them only their respective aliases. This would also mean that the one in charge of managin the api is the server and only the server, which I guess would be good for security.
Solution idea
Not a developer here, but I'm thinking a database with every user and its designated aliases could be implemented, and of course a whole new API to manage the requests client-server-cloudflare. I think this is a lot, but it would be such a cool thing to have for self-hosters, because currently, the self-hosted email scene is basically dead because of the problem of untrusted ip's, and given that probably 80% of self-hosters have a domain-name, at least for me, this would be a great implementation.
Additional info
No response
The text was updated successfully, but these errors were encountered: