From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google SMTP with postfix - Password not accepted
Date: Sun, 15 Oct 2023 10:45:45 +0100 [thread overview]
Message-ID: <8285391.T7Z3S40VBb@rogueboard> (raw)
In-Reply-To: <4866239.31r3eYUQgx@wstn>
[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]
On Saturday, 14 October 2023 12:26:29 BST Peter Humphrey wrote:
> I also tried setting up a gmail IMAP source in KMail, and that worked so I
> assume the permissions are right at their end. (I removed the account when
> KMail kept resurrecting scores of mails I'd already deleted, even though
> access on my mobile showed an absence of mails.)
A bit O/T, but since you mention it I have observed the same behavior here
with Kmail. Different users, different email accounts (inc. Gmail). At
times, emails which have been deleted and even emptied from the Bin/Trash
folder reappear. Deleted again, only to reappear. This can carry on for a
while until the user gets so annoyed as to close Kmail.
I am not sure what causes this, but I suspect Kmail/akonadi does not like
multiple user inputs in close succession, while it is still synchronising
previous local changes to the remote IMAP folder(s). For example, I have
observed if a number of messages are selected and deleted, then without
waiting for Kmail progress bar to finish you move to a different folder and
delete a message, you are most likely to trigger this problem. The more
impatient a user is and the more accounts they have configured, the more often
deleted messages tend to reappear in their Kmail. A variation of the same
problem is when new messages are shown in the Folder List, but none appears
when you select the folder to look at its contents. Pressing F5 or Update
This Folder/Subfolders does not help.
The workarounds I have devised are:
1. Close Kmail, restart it and keep an eye on the progress bar to confirm it
has finished synchronizing all folders with remote IMAP servers, before I
click on anything else.
2. If the above does not succeed I close Kmail and run 'akonadictl stop',
before I restart it.
3. If the problem is not resolved, I repeat step 2 above and proceed to run:
akonadictl start
akonadictl fsck (wait for it to finish)
akonadi vacuum (wait for it to finish)
then relaunch Kmail.
4. A last resort is to launch akonadiconsole, go to the Browser tab and delete
any messages there.
I anyone knows of a better solution, other than trying alternative mail
clients, please post back.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-15 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:29 [gentoo-user] google SMTP with postfix - Password not accepted thelma
2023-06-20 8:30 ` Michael
2023-06-20 8:55 ` William Kenworthy
2023-10-14 5:02 ` Peter Humphrey
2023-10-14 7:04 ` Neil Bothwick
2023-10-14 11:26 ` Peter Humphrey
2023-10-14 13:28 ` Peter Humphrey
2023-10-14 21:59 ` Neil Bothwick
2023-10-15 2:43 ` William Kenworthy
2023-10-15 12:33 ` Peter Humphrey
2023-10-15 9:45 ` Michael [this message]
2023-10-15 12:31 ` Peter Humphrey
2023-06-20 18:09 ` thelma
2023-06-20 18:26 ` Matt Connell
2023-06-21 5:45 ` thelma
2023-06-20 9:11 ` Dr Rainer Woitok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8285391.T7Z3S40VBb@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox