said Darrell Anderson via tde-users:
| I much dislike webmail too. I have not tried to use the Proton bridge.
|
| I think I would first log into the webmail interface. Verify only single
| instances of the mails exist. Then use kmail to download through the
| bridge.
I have here and sometimes use because it is quick and efficient (and for
diagnostic uses such as you describe) ElectronMail, an electron-based
webapp that recreated the ProtonMail web interface. (And also gives
app-level access to such as Proton Drive, Calendar, VPN, and Pass.)
So I have long known that the doubling occurs somewhere between there and
KMail. The first issue I encountered, and this was after I'd used the
bridge for some time, was that messages read on KMail were not always
marked as read at Proton. I *suspect* that if I were to tell KMail not to
leave the messages on the server the problem would go away. But I use
ProtonMail on several devices, using the native ProtonMail app on all but
this machine, where I try to keep a mail archive. The doubling thing is
relatively -- last couple of years -- new. I kind of figured that Proton
would eventually fix it, but maybe I need to make more noise.
(I live where the phone company, the reprehensible Frontier Communications,
has the internet go down one or more times each day. This created a real
problem with Proton VPN, because it wouldn't come back up unless you did
this:
[code]
nmcli connection show --active
nmcli connection delete [pvpn conn.]
[/code]
It would have been trivial for them to put this in the code, to look for
that connection and if it existed and delete it, as part of starting up
their VPN app. But it took literally years of whining about it before they
fixed it. I even made a little script that did it before calling the
Proton VPN application.)
| Another option is temporarily use another mail client such as
| Thunderbird, or perhaps something console based like pine, mailx, or
| mutt. Possibly a less tasteful experiment is install a full KDE 5 in a
| VM along with KMail. The goal is to see whether the same problems occur
| with the Proton bridge. If the same thing happens then sounds like the
| bridge might be faulty or misconfigured.
In the course of this note I realized that I have ProtonMail addresses that
I could set to *not* leave mail on the server, with no inconvenience. I
think I'll give that a shot.
Here is one of the ghost messages, received a little while ago. (It seems
that of the doubled messages, the only ones from the list today that were
doubled were yours, and not all of those.)
X-UID: 9414
X-Length: 10813
X-Flags: 32
From: Darrell Anderson via tde-users <users(a)trinitydesktop.org>
Sender: Darrell Anderson via tde-users <users(a)trinitydesktop.org>
Reply-To: TDE Users <users(a)trinitydesktop.org>
To: <users(a)trinitydesktop.org>
CC: Darrell Anderson <darrella(a)clovermail.net>
Subject: [tde-users] Re: Password Manager constantly asking for password
at
launch.
Message-ID: <d7b11a63-b0be-74c3-1e01-412836827958(a)clovermail.net>
In-Reply-To: <202405191429.39892.CWM1330(a)gmail.com>
References: <202405191429.39892.CWM1330(a)gmail.com>
<T3R6flCKrbRw9RBM0Gfm_uzYiXKkNS8S9m6KMKVA8MngUpNuhWmY1lXEil6jdnCU9K7ES8NzdajdjFdBow3J_Q==(a)protonmail.internalid>
Date: Mon, 20 May 2024 14:26:06 -0500
Content-Type: text/plain
That's the entire thing. The message part was missing, though I got the
whole thing in the other version of the same message.
| Another idea is to use the Proton webmail interface to forward mails to
| another email address. See what happens without needing to use the
| Proton bridge.
Then it would be sent in the clear, which kind of defeats the purpose (but
for the VPN).
| With the keyboard perhaps move the cable to a different USB 2 port.
| Commonly USB keyboards and mice are designed to USB 1.1 specs, so don't
| waste USB 3 ports with these peripherals. Another option is install
| powertop. Commonly with the Linux kernel autosuspend is the default with
| keyboards and mice. Use the 'powertop --html' command to create an HTML
| page. That HTML page will contain explicit commands to disable
| autosuspend with the peripherals. Copy and paste those commands into
| rc.local or similar.
I'll give those things a shot. I've tried different USB ports, put the
keyboard on different devices (so I'm pretty sure it's not the keyboard;
also experienced the same effect with different keyboards on this
machine).
--
dep
Pictures:
http://www.ipernity.com/doc/depscribe/album
Column:
https://ofb.biz/author/dep/