I’m long K9 user, and I was aware of it becoming Thunderbird, but I need to clarify what should I do to easy eventual transition, hopefully without having the deal with all my K9 settings…

Today K9 turned into Thunderbird Beta for Testers, however there’s already an app called that way Thunderbird Beta for Testers showing up on f-droid. Thoug the actual ID of each differ (com.fsck.k9 vs. net.thunderbird.android.beta).

What should K9 users do, to avoid losing its current settings (accounts, folder settings, encryption and so on)? Should we remain using the K9 app, and hope that when it goes away then the thunderbird app replaces it somehow automatically and pick all accounts and settings? Should this period when the two apps with the same name coexist be used to install thunderbird beta for testers, hope that it pick all settings from K9 up, and then remove K9?

It’s somehow confusing, I was originally hoping at some point K9 just turned into thunderbird, but at once, automatically, without still having two apps, so I’m wondering what’s next. For now I’m just still using the K9 app with thunderbird name…

Thanks !

Edit 1: Many thanks for those who replied, at least I don’t have a google account, and no need to inherit the OAuth to google, or any other of such account for that matter, although I could remain to K9 I migrated to Thunderbird official release (no beta) without issues. It sounds like a good opportunity to migrate to Thunderbird.

Edit 2: It’s sad that the OAuth can not be inherited, though understandable. For those who were just using TB or K9 for a long time with gmail, and the account gets into the infinite dependency loop of requiring a device already logged in, given the stupid security question has no answer, then perhaps it’s time to ditch google and look for an alternative, I haven’t found anything useful to help around there. Google actually sent a message indicated it has protected the user from herself, and inhibited her attempt to reach her own account. Meanwhile, just staying with K9 seems OK, since it’s still there (just a metadata name corrupted but the app ID remained K9 still).

  • kixik@lemmy.mlOP
    2·
    2 months ago

    F-Droid produces its own builds, with its own signatures, so to get f-droid going, you’ll need to install from F-Droid. However the import mechanism seems really nice. Perhaps you can install from F-Droid the official release, which can co-exist with your upstream installed beta release, import from it from the F-Droid app, then remove the upstream installed beta release, and if you wan to keep on beta, then install the beta release from F-DRoid (be careful right now, given a bug made K9 show up as beta release as well, but the app ID is clear, just being careful is enough), and then import from the official release, then remove the official release and you’re all set. The idea is not to reconfigure a thing by doing those steps, and perhaps you wouldn’t like to go to beta, and remain on the official release, which is not that behind, and perhaps better tested.