By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 737

Summary:	Kmail - Unable to complete LIST operation
Product:	TDE	Reporter:	Marcin Wilk <m.wilk>
Component:	tdepim	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	critical	CC:	bugwatch, darrella, panamajo, slavek.banko
Priority:	P1
Version:	3.5.12 [Trinity]
Hardware:	i386
OS:	Kubuntu Lucid
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Marcin Wilk 2011-12-09 20:49:24 CST

It looks like something similar to an old Kmail bug http://bugs.kde.org/show_bug.cgi?id=127696

1. I am able to collect all my mail form several pop accounts
2. I have option /leave it on the server for x days/ turn on
3. after some time one of the accounts (its random) hangs out and message appears (its impossible to stop account checking in a right bottom corner menu)...
4. after longer period rest of the accounts joins to the first one...
5. to fetch mail i need to restart Kontact
6. situation repeats after 5-10min sometime 1h

I am only a user however with a detailed instruction can produce a debug info

Comment 1 Jo Schulze 2012-01-31 09:15:17 CST

I can reproduce with KMail 1.9.10 from OBS (http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_12.1/)
As stated here: https://bugzilla.novell.com/show_bug.cgi?id=735064#c21 the KDE3 builds there share code with trinity, Ilya Chernykh did not provide details.

Taken from https://bugzilla.novell.com/show_bug.cgi?id=740594#c0

Since the install of kdepim3-3.5.10-161.1 kmail shows a messagebox saying that
there was a problem when checking for new mail on the remote server, then stops
looking for new mail.

I don't think it's server related as I can perform the very same action with
other mail clients (thunderbird, kmail from KDE4) without any error.

Besides there is no sign of errors on the server side in the logs.

This is probably related to bug #735064 as it didn't happen before.

Reproducible: Sometimes

Steps to Reproduce:
1. Konfigure kmail. In my case it's pop3 vis port 995 (with SSL), same with
pop3 via 110
2. Mail check interval is 5min
3. Start kmail, wait

Actual Results:
As mentioned above this in not always reproduceable. It depends how often kmail
attempts to fetch the mail, sometimes the first attempt right after startup
fails, sometimes it takes 30min.

Kmail shows an alert box captioned "Invalid response from server" and saying
"Unable to complete LIST operation."
Kmail then stops to even try to fetch new mail until restarted.

Expected Results:
No error message. Even if a lookup fails (there are a lot of reasons like
network problems, server downtime, too many users accessing their mailboxs)
kmail should not stop trying.
IIRC that was the former behavior of kmail.

Comment 2 Jo Schulze 2012-02-02 07:56:03 CST

To provide some more information:
It seems related to the inbox size. I got a >500KiB mail this morning and the bug occured right after startup when kmail tried to fetch new mails.
This happend 3 times in a row. Then it succeeded fetching the new mails.

I moved the (then marked as read) mail outside the inbox folder. Then kmail was able to fetch the mails for approx. 25 mins before it failed with the "Unable to complete LIST operation" message (which is equivalent to 5 succuessful inbox checks).

HTH

Comment 3 waldo 2012-08-19 06:16:43 CDT

I was unable to fetch messages from gmail suddenly.

LIST command returned corrupted data every time. You can enter "pop3s://user:password@pop.gmail.com/index" in Konqueror address bar to see it.

This patch fixed the problem for me:
http://patch-tracker.debian.org/patch/series/view/kdepimlibs/4:4.4.5-2/04_backport_fix_abnormal_pop3_aborting.diff

Comment 4 Slávek Banko 2012-12-13 12:50:19 CST

Fixed in GIT hash 65c85dca.

If the bug occurs again, please reopen this bug report.