Version: (using KDE KDE 3.1.1a) Installed from: Compiled From Sources Compiler: gcc 3.2.2 OS: Linux Sometimes, I will have mail available on my IMAP account, and the folder list updates to say that there are unread emails, but they are not listed when I click on the folder. This happens quite frequently, and it happens on all of my IMAP accounts. restarting kmail does not reliably fix the problem.
What imap ser ver are you using?
This started happening some time around 3.1. I thought it was just something wrong with my configuration, but it's happening now on a different computer as well. uclink4.berkeley.edu - * OK uclink4.berkeley.edu Execmail IMAP4rev1 (2.1.6/200010040910) imail.eecs.berkeley.edu - * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] imail.CS.Berkeley.EDU IMAP4rev1 2001.315-VA-mm1 at Sun, 4 May 2003 12:14:29 -0700 (PDT) voyager.724hosting.com - * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=LOGIN] voyager IMAP4rev1 2000.287 at Sun, 4 May 2003 12:02:27 -0700 (PDT)
As it happens with all your servers I assume that it?s a config problem. But ok, let?s try. Is the unread count which is shown in the folderlist correct? You could check that with a different mailclient. If yes, are there any mails which are marked as read in kmail and are shown as unread in other clients? Is your home-dir (where your .kde-dir resides) on a nfs share?
The unread count shown in the folder list (and by clicking on the folder and looking in the status bar) is correct as verified through pine, webmail (squirrelmail), and mozilla. No kmail-read messages are shown as unread in the other client. This has occurred on a system where my home was on a NFS share, but the machine I am testing it out on now (and having the same problem) is on a local ext3 fs.
I know I haven't lost connection to the mail server because I am still able to download messages from the server.
If there are no messages which are incorrect marked as read it means that these messages (which are unread) are not shown in kmail. The folderlist shows that you have unread mails but these mails are not downloaded by kmail. Is that correct? If yes then I need an ethereal log from the communication with your server.
That is correct. The messages are correctly marked, but some just do not show up. How do I get an ethereal log for you?
Well, start ethereal (as root), Capture->start, select your device and click ok. Start kmail (check your account settings and make sure that the communication with your server is _not_ encrypted), check your mail, click on the folder that should have more unread mails. End ethereal and remove the part with your login/password. Save the log and attach it to this report.
Created attachment 1518 [details] ethereal log The IP address for the IMAP server is 128.32.42.119 Sorry I couldn't figure out how to setup the filters to give you a more consise log.
Ignore the filters, I use the follow tcp stream feature. The log only shows that you checked for new mail and no mailbox had new mail. To debug the problem I obviously need a listing with new mails _and_ the selection of the folder which doesn?t list those new mails.
I DID select the folder.
OK, but the server reports that no folder has new mail so kmail obviously does not need to retrieve new headers. If you selected the folder it is possible that you stopped ethereal too early as there is no selection in the logfile.
ok. I'll do one ethereal log with kmail and one with another client later tonight for you. --Jeremy
Created attachment 1548 [details] log of session with kmail the IP address for the IMAP server here is 63.170.197.10
Created attachment 1549 [details] log of session with evolution 63.170.197.10 again
Created attachment 1550 [details] kmail screenshot taken just after ethereal log closed
Created attachment 1551 [details] evolution screenshot taken just before ethereal closed
Subject: Re: new IMAP messages available but not listed On Monday 12 May 2003 02:20, jeremyhu@uclink4.berkeley.edu wrote: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=58090 > > > > > ------- Additional Comments From jeremyhu@uclink4.berkeley.edu 2003-05-12 > 02:20 ------- Created an attachment (id=1550) > --> (http://bugs.kde.org/attachment.cgi?id=1550&action=view) > kmail screenshot taken just after ethereal log closed The selected folder of your screenshot does not correspond with the ethereal log. The listing shows the pure folderlisting of your jeremyhu@ssl.berkeley.edu account and the result of the status command which says that there is 1 unread message in the inbox. So the selected inbox of your outersquare.org account is not in the log. Either you closed ethereal too early or the traffic is on a different network device. There must be more traffic because the message you see in the screenshot has to be downloaded from the server.
I waited for 15 seconds of no traffic (the counter did not increase) before closing the log. I am NOT lieing to you here. Perhaps the problem is that simply selecting the folder does not actually check the folder for new messages.
Created attachment 1577 [details] tarball of logs & screenshots The kmail ethereal log was started before launching kmail. After kmail started and all the folders had been automatically checked, I clicked on the unclink inbox (t=31s, packet count was around 515). I then let the ethereal log go on for another 30s or so before taking the screen shot for you, and this time you can see ethereal running when I took the screenshot, so please stop insisting that I am lying to you.
I turned off the 'auto check' on all the accounts and also removed the '--check' command line option when I launch kmail, and atleast for now, that seems like a temporary fix, so maybe the problem is somewhere in the code that handles that.
nevermind, that doesn't solve the problem...
Subject: Re: new IMAP messages available but not listed jeremyhu@uclink4.berkeley.edu sagte: > ------- Additional Comments From jeremyhu@uclink4.berkeley.edu 2003-05-15 > 04:27 ------- > Created an attachment (id=1577) > --> (http://bugs.kde.org/attachment.cgi?id=1577&action=view) > tarball of logs & screenshots > > The kmail ethereal log was started before launching kmail. After kmail > started > and all the folders had been automatically checked, I clicked on the > unclink > inbox (t=31s, packet count was around 515). I then let the ethereal log > go on > for another 30s or so before taking the screen shot for you, and this time > you > can see ethereal running when I took the screenshot, so please stop > insisting > that I am lying to you. I _never_ said that you were lying. I said that something went wrong while capturing the packets. This is obvious because - and I stated that - the displayed message was _definitely_ loaded from the server and this is not in the log. I definitely believe that you did everything you said.
Subject: Re: new IMAP messages available but not listed OK, it would be good if you could you apply the attached patch to your kmail source (go to kdenetwork/kmail and "patch -p0 < imapdebug.diff"), compile kmail with "--enable-debug=yes" and start it from the console so that you get the debug output. Then select any folder with new messages where kmail doesn
Here's the segment that appeared as I changed folders to my inbox that should (but didn't) show new messages. It doesn't look like any of those debugging statements from your patch printed out, but I definately applied that patch. kmail: set Msg, force = true kmail: set Msg, force = false kmail: set Msg, force = false kmail: enable progress kmail: end 25461[virtual void KMHeaders::setFolder(KMFolder*, bool)] kmail: (1996595101, last 0) notification_only@netbank.com notification_only@netbank.com kmail: set Msg, force = true kmail: ####### ####### ####### parseMsg(KMMessage* aMsg == aMsg, bool onlyProcessHeaders == false ####### ####### kmail: *no* first body part found, creating one from Message kmail: -----> Inserting Root Node into the Mime Part Tree kmail: Inserting one item into MimePartTree kmail: Content-Type: text/plain kmail: <----- Finished inserting Root Node into Mime Part Tree kmail: KMMessage::emailAddrAsAnchor('notification_only@netbank.com') returns: --><a href="mailto:notification_only%40netbank.com">notification_only@netbank.com</a><-- kmail: KMMessage::emailAddrAsAnchor('jeremy@outersquare.org') returns: --><a href="mailto:jeremy%40outersquare.org">jeremy@outersquare.org</a><-- kmail: ** ** KMReaderWin::parseObjectTree( node OK, showOneMimePart: FALSE ) ** ** kmail: * text * kmail: plain kmail: default kmail: KMMsgEncryptionState: 78 kmail: KMMsgSignatureState: 78 kmail: KMReaderWin - finished parsing and displaying of message.
Subject: Re: new IMAP messages available but not listed On Friday 16 May 2003 23:29, you wrote: > Alright, I'll setup to use 3_1_BRANCH for next time, but here's the > output I got from kmail --check. OK, I
It does, but with --check has been more "reliable" for triggering the bug (because of the probable cause being the concurrent checking)
*** Bug 69950 has been marked as a duplicate of this bug. ***
OK, since Till Adam considers this bug identical to #69950 and since this one (#58090) is still marked unconfirmed, should sombody mark it as "Confirmed" or do I need to send some traces/debug data? I'm willing to help in anything that's within my reach.
Subject: Re: new IMAP messages available but not listed Till Adam wrote: >------- You are receiving this mail because: ------- >You are on the CC list for the bug, or are watching someone who is. > >http://bugs.kde.org/show_bug.cgi?id=58090 >adam@kde.org changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > everconfirmed|0 |1 > > I reported the bug #69950. Till Adam placed the report as identical to #58090, with which I am in agreement. I am offering my limited capacity to try to trace a bug with which I have a problem. Salud, Mark
Subject: Re: new IMAP messages available but not listed > I reported the bug #69950. Till Adam placed the report as identical to > #58090, with which I am in agreement. I am offering my limited capacity > to try to trace a bug with which I have a problem. > > Salud, > > Mark Mark, can you provide an ethereal log just to make sure it's a kmail bug and no problem with the kioslave? Start your ethereal and click on a folder that has new messages that are not shown. And it would be helpful if you could compile your imap4-kioslave (kdebase/kioslave/imap4) with debug information and give us the debug output when you click on the folder. Carsten
Mark, can you provide an ethereal log just to make sure it's a kmail bug and no problem with the kioslave? Start your ethereal and click on a folder that has new messages that are not shown. And it would be helpful if you could compile your imap4-kioslave (kdebase/kioslave/imap4) with debug information and give us the debug output when you click on the folder. Carsten
Subject: Re: new IMAP messages available but not listed Carsten Burghardt wrote: >------- You are receiving this mail because: ------- >You are on the CC list for the bug, or are watching someone who is. > >http://bugs.kde.org/show_bug.cgi?id=58090 > > > > >------- Additional Comments From burghardt@kde.org 2003-12-12 09:11 ------- >Subject: Re: new IMAP messages available but not listed > > > >>I reported the bug #69950. Till Adam placed the report as identical to >>#58090, with which I am in agreement. I am offering my limited capacity >>to try to trace a bug with which I have a problem. >> >>Salud, >> >>Mark >> >> > >Mark, can you provide an ethereal log just to make sure it's a kmail bug and >no problem with the kioslave? Start your ethereal and click on a folder that >has new messages that are not shown. And it would be helpful if you could >compile your imap4-kioslave (kdebase/kioslave/imap4) with debug information >and give us the debug output when you click on the folder. > > >Carsten > > > >------- Additional Comments From burghardt@kde.org 2003-12-12 09:13 ------- >Mark, can you provide an ethereal log just to make sure it's a kmail bug and no problem with the kioslave? Start your ethereal and click on a folder that has new messages that are not shown. And it would be helpful if you could compile your imap4-kioslave (kdebase/kioslave/imap4) with debug information and give us the debug output when you click on the folder. > > >Carsten > > Hello Carsten, In reference to imap4-kioslave. Are we talking specifically about "/usr/lib/kde3/kio_imap4.so" which in Mandrake Cooker seems to live in libkdebase4-3.1.94-4mdk? Sorry, I'm not very up on the specifics of KDE programming. Mark
Subject: Re: new IMAP messages available but not listed On Friday 12 December 2003 13:04, Mark Pierce wrote: > In reference to imap4-kioslave. Are we talking specifically about
Subject: Re: new IMAP messages available but not listed Carsten Burghardt wrote: >------- You are receiving this mail because: ------- >You are on the CC list for the bug, or are watching someone who is. > >http://bugs.kde.org/show_bug.cgi?id=58090 > > > > >------- Additional Comments From burghardt@kde.org 2003-12-12 19:08 ------- >Subject: Re: new IMAP messages available but not listed > >On Friday 12 December 2003 13:04, Mark Pierce wrote: > > >>In reference to imap4-kioslave. Are we talking specifically about >>"/usr/lib/kde3/kio_imap4.so" which in Mandrake Cooker seems to live in >>libkdebase4-3.1.94-4mdk? Sorry, I'm not very up on the specifics of KDE >>programming. >> >> > >Probably, but this won't help very much if you don't compile it yourself as >debugging will probably be disabled in packages. I need the debug output from >a self compile kioslave with "--enable-debug=yes". > > >Carsten > > I am including the ethereal trace and kmail/imap-kioslave logs for a single "Check mail in folder" for Inbox. The only directory which refuses to show updated messages. Mark Try Checkmail on Inbox next kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kmail: set Msg, force = true khtml (part): DONE: 14 kmail: set Msg, force = false kmail: set Msg, force = false kmail: enable progress kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=67 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4::get - imaps://makis@mailrelay.genasys.com:993/INBOX/;UID=7096;SECTION=HEADER kio_imap: URL: box= INBOX, section= HEADER, type= , uid= 7096, validity= kio_imap: IMAP4::parseURL: box INBOX kio_imap: IMAP4::makeLogin - checking login khtml (part): DONE: 14 kio_imap: IMAP4Protocol::assureBox - opening box kio_imap: imapParser::sendCommand - setting current box to INBOX kio_imap: imapParser::parseResult - current box is now INBOX kio_imap: IMAP4::get - finished kmail: ImapJob::slotGetMessageResult - retrieved part HEADER kmail: (1979756285, last 0) Mandrake newsletter: new product 'MandrakeMove' unveiled! Mandrake Team, complete false kmail: set Msg, force = true kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=67 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4::get - imaps://makis@mailrelay.genasys.com:993/INBOX/;UID=7096;SECTION=STRUCTURE kio_imap: URL: box= INBOX, section= STRUCTURE, type= , uid= 7096, validity= kio_imap: IMAP4::parseURL: box INBOX kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::assureBox - reusing box kio_imap: IMAP4::get - finished kmail: ImapAccountBase::constructParts - created id 1 of type TEXT/PLAIN kmail: ImapAccountBase::handleBodyStructure - load 1 (TEXT/PLAIN) kmail: load Part kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=67 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4::get - imaps://makis@mailrelay.genasys.com:993/INBOX/;UID=7096;SECTION=1 kio_imap: URL: box= INBOX, section= 1, type= , uid= 7096, validity= kio_imap: IMAP4::parseURL: box INBOX kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::assureBox - reusing box kio_imap: IMAP4::get - finished kmail: ImapJob::slotGetMessageResult - retrieved part 1 kmail: ISubject::notify 1 kmail: KMReaderWin::update - message kmail: ####### ####### ####### parseMsg(KMMessage* aMsg == aMsg ) ####### ####### kmail: *no* first body part found, creating one from Message kmail: -----> Inserting Root Node into the Mime Part Tree kmail: Inserting one item into MimePartTree kmail: Content-Type: text/plain kmail: <----- Finished inserting Root Node into Mime Part Tree kmail: partNode::findType() is looking at Text/Plain kmail: KMMessage::emailAddrAsAnchor('Mandrake Team <return@mandrakesoft.com>') returns: --><a href="mailto:Mandrake%20Team%20%3Creturn%40mandrakesoft.com%3E">Mandrake Team <return@mandrakesoft.com></a><-- kmail: KMMessage::emailAddrAsAnchor('mark.pierce@genasys.com') returns: --><a href="mailto:mark.pierce%40genasys.com">mark.pierce@genasys.com</a><-- kmail: ** ** ObjectTreeParser::parseObjectTree( node OK, showOnlyOneMimePart: FALSE ) ** ** kmail: WARNING: Unknown codec "7bit" requested! kmail: WARNING: KMMessagePart::bodyDecoded(): body is binary but used as text! kmail: KMReaderWin - finished parsing and displaying of message. khtml (part): DONE: 43 kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special kio_imap: IMAP4::dispatch - command=80 kio_imap: IMAP4::dispatch - command=77 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4Protocol::special Created an attachment (id=3715) kmail_checkmail_capture
Subject: Re: new IMAP messages available but not listed On Monday 15 December 2003 11:02, Mark Pierce wrote: > I am including the ethereal trace and kmail/imap-kioslave logs for a > single "Check mail in folder" for Inbox. The only directory which > refuses to show updated messages. Thanks. Unfortunately this is not what I need. If you click on check mail, kmail only gets the unread count but not the new messages. This happens only when you select the folder. So I need the mentioned debug when you click on your inbox. Do you use an up-to-date cvs version of kmail or a beta version? Carsten
I'm pretty sure this is fixed in kde 3.2.1, can you check that please?
I don't use the server which caused this problem any more... so I can't reproduce the environment in which I encountered the bug.
OK, feel free to reopen the report if necessary
Hi, I'm not sure. But perhaps this error came just back. Please have a look at bug 102165 if you're interessted.