Feature #10574: Change default protocol (IMAP vs POP3) depending on whether persistence is enabled or not

Feature #10574

Change default protocol (IMAP vs POP3) depending on whether persistence is enabled or not

Added by kytv 2015-11-17 15:50:45 . Updated 2016-06-08 01:24:53 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Tails_2.4

Start date:

2015-11-17

Due date:

% Done:

100%

Feature Branch:

feature/6154-secure-autoconfig-in-icedove

Type of work:

Code

Blueprint:

Starter:

Affected tool:

Email Client

Deliverable for:

Description

In ~~Feature #9303~~ we decided that we should have POP as the default protocol if persistence is enabled and IMAP as the default if persistence is not enabled.

This ticket is for the actual implementation.

Subtasks

History

#1 Updated by intrigeri 2015-11-24 16:29:05

Assignee set to kytv

(Please fix assignee if that’s wrong, but it can’t be more wrong than no assignee at all :)

#2 Updated by sajolida 2015-11-27 04:39:48

Target version changed from 246 to Tails_2.0

#3 Updated by Anonymous 2015-12-22 06:56:16

Target version changed from Tails_2.0 to Tails_2.2

#4 Updated by Anonymous 2016-01-28 18:35:00

In Tails 2.0~rc1 it seems that IMAP is the default, fyi.

#5 Updated by Anonymous 2016-02-05 16:57:05

Priority changed from Normal to Elevated

Raising priority as this seems to be something which should be done asap.

#6 Updated by intrigeri 2016-02-06 13:46:42

Subject changed from Change protocol (IMAP vs POP3) depending on whether persistence is enabled or not to Change default protocol (IMAP vs POP3) depending on whether persistence is enabled or not

I had a look at ~~Feature #9303~~ that lead to the creation of this ticket, and I’m actually not sure why this is on the SponsorS M4 plate, nor why it would be urgent: Claws Mail defaulted to IMAP, Icedove still does. We have good reasons to switch to POP3 by default when persistence is enabled, but for me this is out of the scope of what we committed to do as part of SponsorS M4. Did I miss anything?

#7 Updated by sajolida 2016-02-07 15:25:35

I agree with you and I think we should remove this one from SponsorS_M4.

As a more general note, I think that sometimes it’s cool to take advantage of a momentum when working fast on a new feature to sneak in other related improvements even if slightly out of the scope of the deliverable, because it might then be way faster to solve this extra stuff than some months later or by someone else (if time allows of course). But here we’re quite far away from such a momentum indeed and it looks like it’s time to simplify kytv’s plate as much as we can :)

I’ll let u update the metadata as the tracker for this project.

#8 Updated by Anonymous 2016-02-09 18:43:14

Priority changed from Elevated to Normal
Target version changed from Tails_2.2 to Tails_2.4
Deliverable for deleted (~~268~~)

ack! delaying it then and removing the sponsor.

#9 Updated by anonym 2016-03-10 12:57:48

Assignee changed from kytv to anonym

#10 Updated by anonym 2016-05-22 15:35:30

Target version changed from Tails_2.4 to Tails_2.6
Type of work changed from Code to Discuss

I know that I originally (on ~~Feature #9303~~) came up with this idea, but after having looked briefly at it, it will not be simple. It will definitely require more upstream Thunderbird patches. Quite honestly, I think we can spend our time on more important stuff.

So I’m raising the discussion for making this a low-prio wishlist feature.

#11 Updated by sajolida 2016-05-23 17:51:14

If you are sure that this will imply upstream patches, then I’m also in favor or rejecting this straight away :)

#12 Updated by intrigeri 2016-05-23 19:13:01

> If you are sure that this will imply upstream patches, then I’m also in favor or rejecting this straight away :)

#13 Updated by Anonymous 2016-05-23 21:10:24

#14 Updated by anonym 2016-05-24 11:51:55

sajolida wrote:
> If you are sure that this will imply upstream patches, then I’m also in favor or rejecting this straight away :)

After a last look at this, apparently I was not, so I have now pushed a solution to: https://github.com/fred-a-kemp/torbirdy/tree/post-secure-autoconfig-fixup . It is hacky (monkeypatches!), but hey, this is a Mozilla add-on. :) Assuming my patch works, we just have to import it into config/chroot_local-patches and add three lines of trivial code to the icedove wrapper, so it is not hard and will require little implementation.