🆕 Software Suggestion | ForwardEmail.net Email Provider #1671

Closed
opened 2020-01-30 08:27:17 +00:00 by niftylettuce · 4 comments
niftylettuce commented 2020-01-30 08:27:17 +00:00 (Migrated from github.com)

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.

  •  I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## 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. - [X] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
niftylettuce commented 2020-03-01 18:43:33 +00:00 (Migrated from github.com)

@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

@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
5a384507-18ce-417c-bb55-d4dfcc8883fe commented 2020-03-01 19:56:49 +00:00 (Migrated from github.com)

@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.

> @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.
niftylettuce commented 2020-03-01 20:09:38 +00:00 (Migrated from github.com)

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.

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.
5a384507-18ce-417c-bb55-d4dfcc8883fe commented 2020-03-01 20:24:11 +00:00 (Migrated from github.com)

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...

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...
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1671
No description provided.