Feature #11215

Update Icedove design documentation wrt. the autoconfig wizard

Added by Anonymous 2016-03-10 21:14:49 . Updated 2016-05-24 20:16:52 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.4
Start date:
2016-03-10
Due date:
% Done:

100%

Feature Branch:
451f:tails/feature/11215+icedove_design_doc
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Email Client
Deliverable for:
268

Description

https://tails.boum.org/contribute/design/#index41h3 should be updated at the same time as we enble the auto configuration wizard in Tails.

Subtasks

History

#1 Updated by Anonymous 2016-03-10 21:15:04

#2 Updated by intrigeri 2016-05-10 04:30:46

  • Status changed from New to Confirmed

#3 Updated by intrigeri 2016-05-10 04:40:06

  • Subject changed from Update Icedove design documentation once the autoconfig wizard is in Tails to Update Icedove design documentation wrt. the autoconfig wizard
  • Description updated

#4 Updated by Anonymous 2016-05-16 08:42:32

  • Assignee set to anonym
  • % Done changed from 0 to 10
  • QA Check set to Ready for QA
  • Feature Branch set to 451f:/feature/11215+icedove_design_doc

Heya,

I’ve tried to be precise without being to detailed.. Not sure if that worked out correctly. Could you please review this and report back? If you think this should rather be assigned to somebody else.. please do!

Cheers!

#5 Updated by Anonymous 2016-05-16 08:42:47

  • Feature Branch changed from 451f:/feature/11215+icedove_design_doc to 451f:tails/feature/11215+icedove_design_doc

#6 Updated by anonym 2016-05-22 20:27:47

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Dev Needed

> +Furthermore, by default, these patches prevent testing email
> +account settings using insecure email protocols. This setting can be disabled
> +(opt-out by the user) and is not activated when using the manual configuration
> +either.

When “Use secure protocols only” is on, manual configuration is affected too. It wasn’t clear to me before, but I think now it’s clear to both of us, given the review remarks and consequent patches. :)

> Here, users are allowed to configure email accounts which do not use
> +transport layer encryption.

Sure, but it is possible to do so before manual configuration too; if we immediately disable “Use secure protocols only” and then probe, then we get the option to use insecure protocols (if no secure one was available).

#7 Updated by Anonymous 2016-05-24 13:36:27

  • Assignee set to anonym
  • QA Check changed from Dev Needed to Ready for QA

I’ve updated the branch. Please review.

#8 Updated by anonym 2016-05-24 20:16:52

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 10 to 100
  • QA Check changed from Ready for QA to Pass