Summary: | After configuring Kmail - using Gmail.Error pop-up at the Rt.Lower corner stating "Google mail :Unknown error - unable to append item flags. | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Dr.M.A.Siriwardena <msiri102> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | bosyber, leon.maurer, montel, msiri102, null |
Priority: | NOR | ||
Version: | 1.99.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dr.M.A.Siriwardena
2011-12-12 16:13:15 UTC
pop3 ? imap ? Both IMAP and POP3 Dr.M.A.Siriwardena. On Mon, Dec 12, 2011 at 11:47 AM, Laurent Montel <montel@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=288816 > > > Laurent Montel <montel@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |montel@kde.org > > > > > --- Comment #1 from Laurent Montel <montel kde org> 2011-12-12 16:47:39 > --- > pop3 ? imap ? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. > I have the same problem - KDE 4.7.4 from the kubuntu ppa, with Kontact 4.7.3. I have now set Kontact to log errors when retrieving mail to a file, hopefully that will give some more useful messages (or even a clear response kontact gets from the gmail imap server on what is failing?). Is there another way to get these messages to be a bit more verbose and useful for debugging? I have kdepim-dbg installed. Seeing the same thing here. Gmail with IMAP over SSL/TLS. Each time KMail checks Gmail (which is 5 minutes), I receive one popup for each folder/label. On the first check, no folders contained messages. On the next check, one folder populated with messages. On some subsequent checks, another folder's messages appeared. There is no apparent consistency to this, however. * Ubuntu Precise * KDE installed from Precise repos (i.e., not Kubuntu) * KMail 4.8 rc1 Followup... I disabled Akonadi Server, deleted the following files: ~/.local/share/akonadi/* ~/.kde/share/config/akonadi* ~/.config/akonadi/* Then I restarted the server and allowed it to create its default set of files. Next I opened KMail and recreated my Gmail settings. Last time, when I was encountering the problem reported in this bug, I had configured this IMAP server: imap.gmail.com This time, I used the following server instead: imap.googlemail.com KMail is now very happy with Gmail. Steve's workaround led me to look at my akonadiserver configuration again too. Apparently my backup hadn't added the right config files, so I returned them to the correct config file ~/.config/akonadi/akonadiserverrc: ---- [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host=localhost Options="MYSQL_OPT_RECONNECT=1" ServerPath=/usr/sbin/mysqld StartServer=false <snip username,password> ---- This cured the issue for me. However, given comment #5 by Steve, it might just be due to changing the configuration. That's especially as he uses a default setting while I use the already running mysqld (the OPT_RECONNECT=1 to avoid errors with timouts) on my system now. I tried returning to the previous configuration, but now my gmail imap folders are up to date, so the error doesn't return. I'd have to remove the current db, at least, but I don't have time to do that today. Upon further experimentation, I'm convinced that starting with a fresh database is the key, not simply changing which IMAP server one uses. However, I'm encountering other problems, and I can no longer say KMail is very happy with Gmail. Deleting messages, for instances, causes a variety of strange problems. I'll look for another bug or open a new one. Gmail appears to be working much better with updated KMail 4.7.97. I was having similar problems in 4.8.0, but Steve's workaround seems to have made KMail happy -- at least for the moment... This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |