Feature #5663: Return to Icedove
Change default protocol (IMAP vs POP3) depending on whether persistence is enabled or not
In #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.
Make extensions.torbirdy.defaultprotocol affect the auto wizard.
We need this for #10574, to make POP the default when persistence is
enabled, and IMAP when persistence is disabled.
Note that we also rename the other patch against TorBirdy to ensure
that they are applied in the correct order.
This patch will be upstreamed in TorBirdy.
#6 Updated by intrigeri almost 3 years ago
- 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 #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 almost 3 years ago
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.
#10 Updated by anonym over 2 years ago
- 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 #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.
#14 Updated by anonym over 2 years ago
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.