-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: added Forward Email #13
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi there! We are the official team behind Forward Email at https://forwardemail.net and @forwardemail on GitHub. **We are sharing a few highlights below about our service:** * Unlike Proton Mail, Skiff, and Tuta we are actually 100% open-source on GitHub. * We support ~250,000+ custom domain names using our MX service (this is _more_ than Proton Mail and Fastmail). * Used by some notable organizations including: - The National Association for Amateur Radio (ARRL) (e.g. `dig arrl.net mx`) - Disney Ad Sales (e.g. `dig disneyadsales.com mx`) - Tufts University (e.g. `dig alumni.tufts.edu mx`) * You'll see in our PR that we already support OpenPGP and WKD.* We are planning to release calendar, contacts, and newsletter support in early 2024. * You don't need a bridge or need to use proprietary apps to use us, you can simply use Thunderbird, Apple Mail, Outlook, or Gmail (we support standard SMTP, POP3, IMAP, API, etc). We also do not rewrite your messages like Proton Mail does. * Our website is translated to 25 languages (even our API, SMTP, POP3, and IMAP error messages are translated to your locale thanks to our work with `@ladjs/i18n` and `mandarin` (npm packages). No other service comes close to us in terms of internationalization support. Some questions we receive frequently are listed below, and we're happy to answer more. P.S. We'd love to be included in your list and have already submitted a PR adhering to your existing code practices – happy to make changes as requested. We're also available at `support@forwardemail.net` and we have a Matrix Chat channel `#forwardemail:matrix.org`. ## Do you have any reviews online anywhere? Yes, we have a list of reviews on Trust Pilot at <https://www.trustpilot.com/review/forwardemail.net>. ## How can you claim to not increase prices? We haven't since 2017 and don't plan to. We abide by a set of [principles](https://forwardemail.net/blog/docs/best-quantum-safe-encrypted-email-service#principles); which keeps us in tune with our product and customer base. ## Do you have a status page? Yes, our status page is linked in the Resources dropdown of our website, on the footer of every page, and our website also updates in real-time of any errors (and automatically presents a notification if necessary of _any_ issues). We also have a TTI (time to inbox) monitoring feature that is public, it's on the footer of every page of our website and shows response times from Gmail, Outlook/Hotmail, and Apple iCloud. An example screenshot is below from the present time (it updates every 5 min): ![Screen Shot 2024-01-02 at 1.26.23 PM|690x287](upload://kYbs0yl1DVTL02a7LNICPWfgbQ1.png) ## How does your encrypted SQLite database feature work, and why SQLite? We have an entire article dedicated to this at <https://forwardemail.net/blog/docs/best-quantum-safe-encrypted-email-service>. Unlike every other email provider, we use individually encrypted SQLite mailboxes with `ChaCha20-Poly1305` encryption (using your strong passphrase, which only you have; you can audit our source to see that we do not store this anywhere and it's only presented client-side when rendered in-memory). Other email providers use shared relational databases to store your emails, and most of them that use MongoDB and PostgreSQL have LUKS encryption, but NOT encryption at rest (of the actual database). SQLite encryption allows us to have both LUKS encryption AND the actual database encrypted itself. Even if a bad actor got access to the block storage device with `yourmailbox.sqlite` they still couldn't open it. If a bad actor has access to the shared relational database of any other email service provider, they have full access to your mailbox. ## Do you have a FAQ section? Yes, see our website FAQ section (note if you hit CMD+F or CTRL+F it will expand everything so you can easily search). We haven't yet added something like Algolia or TypeSense yet but plan to do so in a privacy-focused way.
✅ Deploy Preview for email-comparison ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
titanism
commented
Jan 2, 2024
4 tasks
Looks great! Just going through the details at the moment. Will give you a review or merge later this evening or tomorrow morning. |
Thank you @Lissy93 🙏 Happy New Year 🎉 – we also started sponsoring your efforts on GitHub! |
titanism
added a commit
to titanism/personal-security-checklist
that referenced
this pull request
Jan 2, 2024
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there!
We are the official team behind Forward Email at https://forwardemail.net and @forwardemail on GitHub.
We are sharing a few highlights below about our service:
dig arrl.net mx
)dig disneyadsales.com mx
)dig alumni.tufts.edu mx
)@ladjs/i18n
andmandarin
(npm packages). No other service comes close to us in terms of internationalization support.Some questions we receive frequently are listed below, and we're happy to answer more.
P.S. We'd love to be included in your list and have already submitted a PR adhering to your existing code practices – happy to make changes as requested. We're also available at
support@forwardemail.net
and we have a Matrix Chat channel#forwardemail:matrix.org
.Do you have any reviews online anywhere?
Yes, we have a list of reviews on Trust Pilot at https://www.trustpilot.com/review/forwardemail.net.
How can you claim to not increase prices?
We haven't since 2017 and don't plan to. We abide by a set of principles; which keeps us in tune with our product and customer base.
Do you have a status page?
Yes, our status page is linked in the Resources dropdown of our website, on the footer of every page, and our website also updates in real-time of any errors (and automatically presents a notification if necessary of any issues). We also have a TTI (time to inbox) monitoring feature that is public, it's on the footer of every page of our website and shows response times from Gmail, Outlook/Hotmail, and Apple iCloud. An example screenshot is below from the present time (it updates every 5 min):
How does your encrypted SQLite database feature work, and why SQLite?
We have an entire article dedicated to this at https://forwardemail.net/blog/docs/best-quantum-safe-encrypted-email-service.
Unlike every other email provider, we use individually encrypted SQLite mailboxes with
ChaCha20-Poly1305
encryption (using your strong passphrase, which only you have; you can audit our source to see that we do not store this anywhere and it's only presented client-side when rendered in-memory). Other email providers use shared relational databases to store your emails, and most of them that use MongoDB and PostgreSQL have LUKS encryption, but NOT encryption at rest (of the actual database). SQLite encryption allows us to have both LUKS encryption AND the actual database encrypted itself. Even if a bad actor got access to the block storage device withyourmailbox.sqlite
they still couldn't open it. If a bad actor has access to the shared relational database of any other email service provider, they have full access to your mailbox.Do you have a FAQ section?
Yes, see our website FAQ section (note if you hit CMD+F or CTRL+F it will expand everything so you can easily search). We haven't yet added something like Algolia or TypeSense yet but plan to do so in a privacy-focused way.