Feature #7685

Document alternative email providers

Added by Anonymous 2014-07-28 21:43:57 . Updated 2019-03-12 14:26:27 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2014-10-27
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Email Client
Deliverable for:

Description

The doc should state something like:
“We do not recommend any third party services for your private communication, be it email, instant messaging or any other kind of messaging. We consider that it is not the aim of Tails to provide such information. However, the RiseupCollective provides a list of autonomous servers.(”$“:https://help.riseup.net/en/security/resources/radical-servers) Furthermore, we encourage you to run your own, independent, services.”

If such a list exists for Jabber too, then let’s add this too eventually.

Subtasks

Feature #8176: Research privacy-friendly email providers Rejected

0

Related issues

Related to Tails - Feature #5870: Better support of non-commercial ISPs Rejected
Blocked by Tails - Feature #7694: Document email client Resolved 2014-07-31
Blocked by Tails - Feature #7436: Contact Riseup on how we could help towards publishing a list of recommended email providers Resolved 2014-06-22

History

#1 Updated by Anonymous 2014-07-28 21:44:44

  • related to Feature #7436: Contact Riseup on how we could help towards publishing a list of recommended email providers added

#2 Updated by intrigeri 2014-07-28 21:58:32

  • Status changed from New to Confirmed

I think the next thing to do is to look for potential places where this can be added in the documentation.

#3 Updated by BitingBird 2014-07-29 16:11:52

It should go on the email documentation page, except… we don’t have one, and since we’re going to move back to iceweasel, it would be a waste of time to document Claws Mail. But maybe we should have just a link to Calws’documentation, and your email-provider paragraph ?

#4 Updated by Anonymous 2014-07-29 19:52:48

BitingBird wrote:
> It should go on the email documentation page, except… we don’t have one, and since we’re going to move back to iceweasel, it would be a waste of time to document Claws Mail. But maybe we should have just a link to Calws’documentation, and your email-provider paragraph ?

I like this idea.

I also discovered the only relevant page when searching for claws mail in the documentation just now: https://tails.boum.org/doc/encryption_and_privacy/openpgp_with_claws_mail/index.en.html It’s empty :(

#5 Updated by BitingBird 2014-07-29 20:09:25

Yep, and it’s not linked from the documentation main page. Maybe it should be removed ?

#6 Updated by sajolida 2014-07-31 09:26:25

#7 Updated by sajolida 2014-07-31 09:50:00

First of all, I’m not convinced by “We do not recommend any third party services for your private communication […] Furthermore, we encourage you to run your own, independent, services.”. As this is not practical or actionable by the people who are interested in that info. But I’ll rather work on the draft through tails-dev and Git.

Then, yes, we should add a minimal documentation page for email client, delete that other empty page, and add it there. That’s now Feature #7694,

#8 Updated by sajolida 2014-07-31 09:50:17

  • related to deleted (Feature #7436: Contact Riseup on how we could help towards publishing a list of recommended email providers)

#9 Updated by sajolida 2014-07-31 09:50:37

  • blocked by Feature #7436: Contact Riseup on how we could help towards publishing a list of recommended email providers added

#10 Updated by sajolida 2014-10-27 08:25:38

We got an answer from someone from riseup on this.

It would be great to have a list of privacy-friendly email providers that include providers that are not explicitly political.

This could be done on the Riseup help pages, maybe at https://help.riseup.net/security/resources/communication-providers (or something like this).

The Riseup help page are generated from a public Github repository, so anyone can submit changes: https://github.com/riseupnet/riseup_help

It is not clear whether anyone at Riseup has the time to really work on this right now. So if someone does that work, they are willing to help us formatting and publishing the thing.

#11 Updated by sajolida 2014-10-27 08:27:03

  • Category set to 212

#12 Updated by BitingBird 2014-12-03 16:05:58

  • Status changed from Confirmed to In Progress
  • QA Check set to Ready for QA

#13 Updated by BitingBird 2014-12-03 18:15:43

  • Assignee set to sajolida
  • Target version set to Tails_1.2.2
  • Feature Branch set to bitingbird:doc/7694-email_client

#14 Updated by sajolida 2014-12-11 15:58:33

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed

Thanks for working on this.

Unfortunately, it seems like you copied and pasted the proposal from the ticket description, but I raised many concerns about it in the following comments. So please have a look at all the comments and at the subtask Feature #8176 and ask for clarification if needed.

#15 Updated by anonym 2014-12-12 16:41:57

  • Target version changed from Tails_1.2.2 to Tails_1.2.3

#16 Updated by BitingBird 2015-01-08 05:35:21

  • Target version changed from Tails_1.2.3 to Tails_1.3

#17 Updated by BitingBird 2015-01-16 13:46:41

So… I should put this ticket on wait until Feature #8176 is resolved? Because right now, there is nothing I could add in it…

#18 Updated by BitingBird 2015-01-16 13:46:53

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Dev Needed to Info Needed

#19 Updated by BitingBird 2015-02-10 13:54:24

  • Target version changed from Tails_1.3 to Tails_1.3.2

#20 Updated by sajolida 2015-02-24 12:32:34

  • Assignee deleted (sajolida)
  • Target version deleted (Tails_1.3.2)

Feature #8176 is already a subtask of this one, so for me the semantics is here already. We could add a blocking relationship as well, but being a subtask already blocks the parent task I think.

Anyway, I think that efforts on this front should be put into compiling the information in Feature #8176 and working together with Riseup to push that on their wiki.

#21 Updated by BitingBird 2015-04-05 16:55:14

  • Assignee set to BitingBird
  • Feature Branch changed from bitingbird:doc/7694-email_client to bitingbird:doc/7685-email_providers

#22 Updated by BitingBird 2015-04-05 16:57:10

Pushed there a page about email providers, cut from Feature #7694. Will work on that later.

#23 Updated by BitingBird 2015-04-05 16:57:30

  • QA Check deleted (Info Needed)

#24 Updated by Anonymous 2017-06-30 14:35:17

I’d love to move this forward, it’s simply about adding one sentence and a link. BitingBird, are you still up for this?

#25 Updated by Anonymous 2018-08-18 13:18:54

  • Assignee deleted (BitingBird)

I’ll try to look at BitingBird’s branch.

#26 Updated by Anonymous 2018-08-19 09:39:13

  • related to Feature #5870: Better support of non-commercial ISPs added

#27 Updated by Anonymous 2019-03-12 14:20:26

  • Status changed from In Progress to Rejected
  • Feature Branch deleted (bitingbird:doc/7685-email_providers)

- The branch is not existent anymore.

- The previously provided link (https://riseup.net/security/resources/communication-providers) is not existent.
- Nobody managed to work on this in the last four years (wow!)

→ I’m rejecting this now, let’s reopen it if we really want to do it.

#28 Updated by intrigeri 2019-03-12 14:26:27

> - The branch is not existent anymore.

Just in case someone comes back to it later, the branch is still there: https://git.tails.boum.org/bitingbird/tails/log/?h=doc/7685-email_providers