mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2024-09-08 18:49:12 +00:00
Criteria updates to email: Require export and headers (#1933)
This commit is contained in:
parent
fa9faa5648
commit
80f1e8ca51
@ -209,7 +209,7 @@ For everything else, we recommend a variety of email providers based on sustaina
|
|||||||
- [:simple-linux: Linux](https://tutanota.com/#download)
|
- [:simple-linux: Linux](https://tutanota.com/#download)
|
||||||
- [:octicons-browser-16: Web](https://mail.tutanota.com/)
|
- [:octicons-browser-16: Web](https://mail.tutanota.com/)
|
||||||
|
|
||||||
Tutanota doesn't use the [IMAP protocol](https://tutanota.com/faq/#imap) or the use of third-party [email clients](email-clients.md), and you also won't be able to add [external email accounts](https://github.com/tutao/tutanota/issues/544#issuecomment-670473647) to the Tutanota app. Neither [Email import](https://github.com/tutao/tutanota/issues/630) or [subfolders](https://github.com/tutao/tutanota/issues/927) are currently supported, though this is [due to be changed](https://tutanota.com/blog/posts/kickoff-import). Emails can be exported [individually or by bulk selection](https://tutanota.com/howto#generalMail).
|
Tutanota doesn't use the [IMAP protocol](https://tutanota.com/faq/#imap) or the use of third-party [email clients](email-clients.md), and you also won't be able to add [external email accounts](https://github.com/tutao/tutanota/issues/544#issuecomment-670473647) to the Tutanota app. Neither [Email import](https://github.com/tutao/tutanota/issues/630) or [subfolders](https://github.com/tutao/tutanota/issues/927) are currently supported, though this is [due to be changed](https://tutanota.com/blog/posts/kickoff-import). Emails can be exported [individually or by bulk selection](https://tutanota.com/howto#generalMail) per folder, which may be inconvenient if you have many folders.
|
||||||
|
|
||||||
??? check "Custom Domains and Aliases"
|
??? check "Custom Domains and Aliases"
|
||||||
|
|
||||||
@ -378,6 +378,7 @@ We regard these features as important in order to provide a safe and optimal ser
|
|||||||
**Minimum to Qualify:**
|
**Minimum to Qualify:**
|
||||||
|
|
||||||
- Encrypts email account data at rest with zero-access encryption.
|
- Encrypts email account data at rest with zero-access encryption.
|
||||||
|
- Export capability as [Mbox](https://en.wikipedia.org/wiki/Mbox) or individual .eml with [RFC5322](https://datatracker.ietf.org/doc/rfc5322/) standard.
|
||||||
|
|
||||||
**Best Case:**
|
**Best Case:**
|
||||||
|
|
||||||
@ -427,6 +428,7 @@ Email servers deal with a lot of very sensitive data. We expect that providers w
|
|||||||
- Website security standards such as:
|
- Website security standards such as:
|
||||||
- [HTTP Strict Transport Security](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)
|
- [HTTP Strict Transport Security](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)
|
||||||
- [Subresource Integrity](https://en.wikipedia.org/wiki/Subresource_Integrity) if loading things from external domains.
|
- [Subresource Integrity](https://en.wikipedia.org/wiki/Subresource_Integrity) if loading things from external domains.
|
||||||
|
- Must support viewing of [Message headers](https://en.wikipedia.org/wiki/Email#Message_header), as it is a crucial forensic feature to determine if an email is a phishing attempt.
|
||||||
|
|
||||||
**Best Case:**
|
**Best Case:**
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user