We support SMTP, POP3, IMAP, API, webhooks, regular expressions, and more.
[1]: https://forwardemail.net/blog/docs/best-quantum-safe-encrypt...
[2]: https://forwardemail.net/faq#do-you-support-openpgpmime-end-...
Sorry; I was being unnecessarily ironic because there really is no "quantum safe" things yet. Otherwise nice work; always nice to see more competition in this space!
How?
Or maybe I'm just jaded to centralized platforms
Still a cool idea though
> We rate limit users and domains to 300 outbound SMTP messages per 1 day.
People who are using DeltaChat groups should think twice here: Every time you reply to the group it will “cost you” as many outgoing emails as there are people in the group, and every time you read a group message it will also cost you as many outgoing emails as there are group members because “read receipts” are sent as plain emails.
A couple of years ago I had to switch email provider exactly because of this. While 300 outgoing emails may sound like a lot, it isn't if you're using DeltaChat groups.
I'm a firm believer privacy and security should be a default and not a pay to unlock feature. With that in mind I never gave this service a chance and instead tried to use other competitors for email aliasing. [1]
[1]. (Simplelogin.io/ / Addy.io)
Question regarding encryption:
It seems that unless there's an active IMAP connection, emails are written in plaintext to a temporary location and are only added to the encrypted mailbox once a new IMAP connection starts. This is because you use symmetric encryption and need the user's password.
Have you considered incorporating public key encryption in your architecture and if so, why did you choose not to?