Archived
🆕 Software Suggestion | ForwardEmail.net Email Provider #1671
Closed
opened 2020-01-30 08:27:17 +00:00 by niftylettuce
·
4 comments
No Branch/Tag Specified
master
dependabot/bundler/nokogiri-1.13.6
dependabot/bundler/addressable-2.8.0
freddy-m-patch-3
pr-add_RemoveMyPhone_sponsor
pr-browser_cleanup_1257_1328_1430
freddy-m-patch-2
freddy-m-patch-1
pr-vpn_hated_one_video
cdn
update-nitrohorse-image
promote-metager-to-card
hardware
pr-add_azirevpn
pr-add_mailfence
shop
1673
pr/1658
i18n-simple
sponsorship-edits-nov2019
i18n
ipfs
blacklight447-ptio-patch-3
blog
remove-windows-icons
pr/1147
i18n-testing
add-beautify
No results found.
Labels
Clear labels
:mag:🤖 Search Engines
I2P
OS
Self-contained networks
Social media
Tor
WIP
XMPP
[m]
approved
dependencies
duplicate
feedback wanted
high priority
iOS
low priority
stale
streaming
todo
wontfix
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
🆕 software suggestion
🆘 critical
🇦🇶 translations
🌐 Social News Aggregators
🌐 hosting
🌐 website issue
🏠 housekeeping
🐛 bug
👁️ browsers
👥 team chat
💢 conflicting
💬 discussion
💻 hardware
📁 file storage
📝 correction
📧 email
🔎 research required
🔐 password managers
🔒 VPN
🔒 file encryption
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🚫 Windows
🤖 Android
🦊 Firefox
🧰 productivity tools
The Invisible Internet Project (I2P)
Operating Systems
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Extensible Messaging and Presence Protocol
Matrix protocol
approved, waiting for a PR
Pull requests that update a dependency file
A label for stalebot if it gets added
Anything related to media streaming.
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Browser Extension related issues
Anything covering a translated version of the site
*Technical* issues with the website.
Anything primarily related to site cleanup.
Correction of content on the website
Virtual Private Network
Domain Name System
Firefox & forks, about:config etc.
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1671
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Basic Information
Name: ForwardEmail
Category: Email
URL: https://forwardemail.net
Description
Create and forward an unlimited amount of email addresses with your domain name. Plus get catch-all, wildcard, and disposable forwarding addresses. It is 100% open-source.
About: https://forwardemail.net/en/about
Privacy Policy: https://forwardemail.net/en/privacy (we don't store logs nor emails)
Terms: https://forwardemail.net/en/terms
Why I am making the suggestion
No email-forwarding service existed that was free, secure, and open-source – so we built one.
My connection with the software
I am the author.
@dngray I don't see ForwardEmail mentioned anywhere - not sure why this was closed, but I think it should be added to the Email Cloaking section at https://www.privacytools.io/providers/email/#cloaking. We do not store logs and have a way better privacy policy than any other service that exists. We don't store any logs and I set up load balancing around the world using Cloudflare's privacy-first load balancing and DNS.
cc @Mikaela
You don't meet the security criteria, that's why, you can check your website's security here: https://www.hardenize.com/report/forwardemail.net/1583092497 and you can check the criteria on the new email provider's web page.
The criteria on the new email provider's web page is extremely biased. Even if I pass the "hardenize" test, we will still be rejected because we use Digital Ocean as our server hosting? I operate a privacy-first service that is also reliable and is lightning fast globally, it is a shame to not honor that instead.
I don't see anywhere that there's a prohibition against hosting your service with Digital Ocean or something like that, the only thing similar to that is that you must host your own analytics.
All in all I think the criteria is pretty good, you don't have to pass every part of the hardenize test, but you do need to not use old TLS that are going to be depreacted, for example.
Stil, I didn't create the criteria, so...