dep wrote:
On Thursday, January 17, 2019 2:59 PM, deloptes deloptes@gmail.com wrote:
~/.trinity/Autostart/
or the files sourced
All I found in that directory was a file, .directory, which listes many translations of the word "Autostart".
ok so it is not autostarted by entry there - I don't remember where TDE is writing which apps were running when it stopped, so that it starts them next time .... there should be something in ~/.trinity
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
I have no idea what the results are supposed to look like, so I have no idea whether it's showing anything anomalous. Perhaps you would be able to read it, but I can make no sense of it.
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
Not sure how I'd do that, but a check of the ports tells me that the bridge is listening:
Desktop-Bridge 4392 dep 11u IPv4 34290 0t0 TCP 127.0.0.1:1143 (LISTEN) Desktop-Bridge 4392 dep 12u IPv4 33466 0t0 TCP 127.0.0.1:1025 (LISTEN)
Which I imagine is expected behavior. Nor are there failure to login errors from kmail.
telnet 127.0.0.1 1143 telnet 127.0.0.1 1025
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.
Right. I can view mail through the webmail version of Protonmail -- that's how I'm writing this -- but after months of being able, with reasonable success, to use ProtonMail bridge I now can't, and I can't figure out any diagnostics for determining what got broken.
does the bridge have some debugging option?
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.
If there were a certificate problem, wouldn't kmail throw an error? There are no security settings as such with Protonmail Bridge, and the settings in kmail appear to be correct.
yes indeed - it looks like that while it is trying to do something the connection breaks and you get the error
What I need to find out is if kmail is actually communicating with Protonmail Bridge. If it is, then I need to find out if Protonmail Bridge is communicating with the server in Switzerland. And I have no idea how to do either of those things.
Meet your best friend Wireshark ;-)
you can try also tdedebugdialog 5006 kmail and perhaps also tdeio and generic, but I am not sure if what you are using has debug, or you can install it - I think someone mentioned it is not compiled
regards