Hello, can you gather logs from the mail daemon on device ? This part has been touched during the last development cycle and it may have break Yahoo mail : Collect Email Logs | Sailfish OS Documentation
" So far only Rpn calculator
It looks like it is going to be pythongeddon due to python update."
For me, RPN calculator is so far the only app, that I found not working after the update. And this is likely due to the Phyton update, yes.
here is the journal log, this was just for yahoo mail but there is also separate yahoo account thing for contacts and calendars which also dont work
May 12 12:13:38 Xperia10II-DualSIM [5270]: [D] unknown:0 - "1" RECV: a001 OK CAPABILITY completed
May 12 12:13:38 Xperia10II-DualSIM [5270]: [D] unknown:0 - "1" SEND a002 AUTHENTICATE XOAUTH2 <password hidden>
May 12 12:13:42 Xperia10II-DualSIM [5270]: [D] unknown:0 - "1" RECV: a002 BAD [AUTHENTICATIONFAILED] AUTHENTICATE Invalid credentials
May 12 12:13:42 Xperia10II-DualSIM [5270]: [D] unknown:0 - Invalidate credentials "imap4" from account 13
May 12 12:13:42 Xperia10II-DualSIM [5270]: [D] unknown:0 - Action completed 21895743275009 result failure
I donât know how Yahoo account auth is supposed to work, but is XOAUTH2 the correct method? It would appear PLAIN or LOGIN should be supported.
I get this error with yahoo account every time :
and Iâm using the yahooâs âapp passwordâ thing that is needed
I could fix this error on my NAS by connecting to that URL with Sailfish OS Web Browser and entering my credentials there. After that, it also works in CalDAV Prefs.
1 Like
Thatâs the problem. I changed the authentication code (for other reasons) in the mailer daemon, and I gave OAUTH2 a higher priority than PLAIN, when no setting exists (and the UI donât give the possibility to change the authentication mechanism). Yahoo is exposing in its capabilities that XOAUTH2 is supported, so the mailer daemon choose it, but there is no support for it on Sailifsh sideâŚ
We can check this with @ahjolinna, can you check what the following command is giving :
devel-su -p ag-tool get-service 13 email string:imap4/authentication
To work, it should return imap4/authentication = 2 (2 means PLAIN) but it will report imap4/authentication = 4 (4 means XOAUTH2) in your case, right ? (ag-tool comes in the package libaccounts-glib-tools)
You can then change it for 2 using :
devel-su -p ag-tool update-service 13 email string:imap4/authentication="2"
If it works, then, we can think about CalDAV and CardDAV issuesâŚ
2 Likes
I have worked around a similar problem by changing the account creation page (in my case /usr/share/accounts/ui/email.qml, and adding a line to the defaults:
account.setConfigurationValue(defaultServiceName, "imap4/downloadAttachments", 0)
account.setConfigurationValue(defaultServiceName, "imap4/servicetype", "source")
account.setConfigurationValue(defaultServiceName, "imap4/acceptUntrustedCertificates", settings.acceptUntrustedC>
+ account.setConfigurationValue(defaultServiceName, "imap4/authentication", '2')
} else {
account.setConfigurationValue(defaultServiceName, "incomingServerType", 1)
account.setConfigurationValue(defaultServiceName, "customFields/showMoreMails", "false")
Using the changed file, create the account, afterwards revert it again.
1 Like
devel-su -p ag-tool get-service 13 email string:imap4/authentication
thing didnt work, it gave me this:
(process:19581): accounts-glib-WARNING **: 14:04:37.614: Unable to load account 13 Account does not exist. Check account ID entered
Strange, if you list all accounts, can you see your Yahoo mail account ? Which number does it have ?
devel-su -p ag-tool list-accounts
1 Like
okay it was 17âŚnot 13âŚ
and I had imap4/authentication = 4
using devel-su -p ag-tool update-service 17 email string:imap4/authentication="2" seems to have fixed the issue
4 Likes
Do the following from the Updating Sailfish OS article:
Final clean up
The OS update notification may persist in the device after updating the OS with the command line method. The commands below may help in eliminating the notification:
cd $HOME
devel-su
pkill -f osupdateservice
rm ./.cache/sailfish-osupdateservice/os-info
Youâll then see the proper version in the Settings â Sailfish OS updates. However, checking for an update will revert to the 5.0.0.78 update, which Iâve been told is a bug.
1 Like
I updated my dev device. Also got the Update notification for the downgrade. Didnât hit it, as downgrades are not supported. (Know that from reading the update documemtation page fully, wow!) If i would have, i wouldnât spread blame on the forums and accept, that i fucked up myself and reinstall. No problem on a dev device.
It is super important for the people having packages, e.g. on OBS/Chum, to be able to at least try to adapt them to the latest release asap (have to admit, not so easy with some of the python stuff and not to much packaging experience) and if to many people rant around here, most likely Jolla might start to think that this pre pre release for the developers was not a good idea after all. And that would be a great loss for the community in the end, as we would have to wait longer for updated comunity packages after the update was released to anyone âthe easy wayâ (as EA).
So please, Jolla, ignore the bad mood of some people here and offer the same type of developer early access release and OBS repos next time there are a lot of dependencies changes. 
EDIT: Maybe some mod can split all the latest to a â5.1 Developer early access release - ignored the warningâ-Thread?
10 Likes
Done. I hope you donât mind my not very sharp knife. It was not very easy to cut fat from the meat with it.
6 Likes