✨ Feature Suggestion | New email Criteria. #1345

New Issue

2019-09-24T12:02:33Z

blacklight447 commented

2019-09-24 12:02:33 +00:00

(Migrated from github.com)

Description:

This post is to kick of the discussion for our new email criteria.

The new criteria should include:
I started with a list of things i things should be required:
secure mail extensions: SPF,DMARC, DKIM, StartTLS, DNSSEC, and Dane at a minimum, with a best case scenerio of also supporting mta-sts and smtp tls reporting.

We also have to discuss whether we will make GDPR compliancy a requirement or a preference.

Another thing that has to be discussed is if we hold on to our 5 eyes rule. this is because we don't know what has changed over the years, and which countries are trustworthy and which are not.

As a last thing, we need to figure out what we see as an acceptable privacy policy:
what gets stored. why does something get stored? for how long? do other providers store it as well (is it an industry standard)?

## Description: This post is to kick of the discussion for our new email criteria. The new criteria should include: I started with a list of things i things should be required: secure mail extensions: SPF,DMARC, DKIM, StartTLS, DNSSEC, and Dane at a minimum, with a best case scenerio of also supporting mta-sts and smtp tls reporting. We also have to discuss whether we will make GDPR compliancy a requirement or a preference. Another thing that has to be discussed is if we hold on to our 5 eyes rule. this is because we don't know what has changed over the years, and which countries are trustworthy and which are not. As a last thing, we need to figure out what we see as an acceptable privacy policy: what gets stored. why does something get stored? for how long? do other providers store it as well (is it an industry standard)?

👍 1

blacklight447 commented

2019-09-24 12:13:20 +00:00

(Migrated from github.com)

Pinging @tya99 from issue #603 so we can get started

mfed3 commented

2019-09-30 17:22:35 +00:00

(Migrated from github.com)

Recommend to add two additional columns with headers "Open Source Client" and "Open Source Server" with possible enumerated values as "Yes", "No" and ("Planned" or "No, Planned" for sortability. For example, Proton Mail and Tutanota both have open source clients, with (as of 9/30/2019) closed source servers, but claim that they plan to open source them in the future.

👍 2

ghost commented

2019-10-05 11:40:59 +00:00

(Migrated from github.com)

Just wanted to let you know I will be handing https://github.com/privacytoolsIO/privacytools.io/issues/603 and this issue over to @dngray, newest member of privacytoolsIO and capable email provider shepherd.

Just wanted to let you know I will be handing https://github.com/privacytoolsIO/privacytools.io/issues/603 and this issue over to @dngray, newest member of [privacytoolsIO](https://github.com/privacytoolsIO) and capable email provider shepherd.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1345