dep wrote:
On Thursday, January 17, 2019 2:21 AM, deloptes
<deloptes(a)gmail.com> wrote:
so are you sure you don't have anything
running twice - I mean kmail?
yup, at least if the command killall kmail followed by top are any
indication.
Did you reboot in the mean while? Does it work
after reboot?
i've rebooted a few times, no joy. i've looked at ~/.xsession-errors and
there's nothing pertinent. (though i did see an error that the dropbox
binary is not found, which raises another issue: where might i edit things
that autostart? dropbox did, though i've long since deleted it, and
protonmail bridge does. might be useful to remove it from autostart and
then start it manually -- in fact, i'd prefer to do it that way. any idea
how to go over the autostart stuff and prune the stuff i don't want?)
~/.trinity/Autostart/
or the files sourced
at this point i'm not sure whether it is kmail or
protonmail bridge that's
causing the problem. the error thrown: "The connection to the server
DrippingWithIrony was unexpectedly closed or timed out. It will be
re-established automatically if possible." I am not certain that it ever
gets established.
sometimes strace helps in such cases
the issue is this: the only linux mail client
officially supported by
protonmail bridge is thunderbird, which i'd use if it supported maildir,
but it doesn't and i see no reason to think it ever will. configuring
protonmail bridge is actually fairly straightforward -- both incoming and
outgoing use 127.0.0.1. imap is port 1143; smtp is 1025. there is an
elaborate password, which i get from protonmail bridge itself.
don't know - you should be able to check those even with telnet
starting the bridge from a terminal throws this:
dep@dep-desktop:~$ Desktop-Bridge
DEBU[0000] main init goroutine=1
pid=12511 pkg=init
INFO[0000] init error: <nil> goroutine=1
pid=12511 pkg=init
and it seems then to start. i do not know, though, what normal behavior
would be -- could be that it's working just fine.
would be nice if there were a privacy-oriented email service that used gpg
or the like and didn't read/scan/track email. best i can tell, there
isn't, which is why i use protonmail.
no one argues against. I just asked because I recall you were writing about
it, so it looks like kmail is not able to authenticate against your local
protonmail instance.
what happens if you check in the settings of the account for example
security or something - could be ssl certificate expired or who knows what.
regards