On giovedì 4 gennaio 2018 11:00:06 CET Rob Brewer wrote: > Pino Toscano wrote: > > > On martedì 26 dicembre 2017 10:49:12 CET Pino Toscano wrote: > > So this is only a short-term issue. That said, not sure for how long > >> the kdepim 4.x stack can still be shipped, although... we will see. > > > > That said, since I published the code (although I need to "present it" > > to the PIM people): my personal plan is to create a NNTP resource for > > Akonadi, so kmail can be a newsreader client too. Here > > https://cgit.kde.org/scratch/pino/akonadi-nntp.git/ > > you can see the first version I have so far, which works fine for me. > > It will not have all the extra features knode has (like scoring) > > though, at least if noone implements them, and it will require a bit > > of integration work (like extra actions on right click on a server) in > > kmail too. > > > This will be great and I really do appreciate your effort in doing this. I > have not had a chance to look at this yet (see below) and will respond when > I have had a look at it. > Sandro emailed me earlier in the week asking for help in porting knode to > Qt5. I have been looking into what would be required and I would be very > happy to help but the learning curve to manage this seems to be too steep > for me. Maybe your NNTP resource would negate the need for the porting > anyway. I went for the "Akonadi resource" route because my feeling is that knode is basically 75% what kmail is, so even using the common PIM (internal) libraries there is still an amount of repeated code, UI bits, etc, that IMHO is simply not worth to maintain in the long term. With the Akonadi resource I wrote, kmail works as-is as basic NNTP reader, and (always IMHO) adding the extra functions should be easier than work with an generally different application. Of course, I have nothing against anyone else porting knode fully, and becoming its medium-/long-term maintainer :-) > Regarding kmail after the update I can no longer access my gmail IMAP > account. Looking at the akonadi messages I am seeing > > "org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no > mechanism available: No worthy mechs found" > qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on > non-plain connection" > > and when looking at gmail account settings all the connection options are > greyed out. > > Could it possibly be due to a missing XOAUTH plugin? > I have tried to install sasl2-bin but this wants to remove : > > dolphin4 kde-baseapps-data kdepim-doc kpart-webkit ktnef libgeos-3.5.1 > libkcddb4 libkcompactdisc4 libkonqsidebarplugin4a libmikmod3 libqmobipocket1 > libsdl-mixer1.2 libsdl-net1.2 python3.6-2to3 Some of these (dolphin4, kdepim-doc, libkc*, libqmobipocket1) are old, and should appear in the The following packages were automatically installed and are no longer required: section in the output of apt. Can you please paste/attach the full outputs of - LANG=C apt-get install sasl2-bin - LANG=C dpkg -l '*sasl*' ? Thanks, -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.