Bug 232245 - Could not read file Invalid response from server:
Summary: Could not read file Invalid response from server:
Status: RESOLVED DUPLICATE of bug 230072
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2010-03-26 17:07 UTC by dc
Modified: 2010-07-30 00:00 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dc 2010-03-26 17:07:18 UTC
Version:           1.13.1 (using 4.4.1 (KDE 4.4.1), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-17-generic

Since my last upgrade, this morning, (Kubuntu 10.04 beta1) I cant retrieve my mails through a simple pop3 server. Kmail client says :

    Could not read file Invalid response from server:

While the pop3 server says :

    I/O error flushing output to client dc at xxx: Operation not permitted (1) [pop_send.c:693]

Wow ! Each one's saying : "It's not me...".

Since the pop3 server has not been updated for months, I suspect something wrong on the Kintact/Kmail side. The error message (on the Kmail side) is rather misleading or incomplete.

I don't mind spending sometimes investigating the problem, but I need a few hints before that.
Comment 1 E.T. Anderson 2010-04-23 23:51:46 UTC
This is happening to me too. I also have recently upgraded to Lucid, so I wonder if this is a Kmail bug or a Kubuntu bug.
Comment 2 Nicolas L. 2010-04-28 11:36:23 UTC
can you update your ubuntu to see if the bug is still valid ?
Comment 3 dc 2010-04-28 15:03:57 UTC
I updated my system to Kubuntu 10.04 RC* a few weeks ago, and the error moved to kontact unable to start (akonadi/nepomuk grrrrr...). 

Anyway, using Kmail (not Kontact) seemed to solve the problem for a while, and it seems everything's working fine now. What happened ? still don't know... but it works.

My feeling is that it was related to akonadi/nepomuk/MySQL/blabla (far too complex stuff).

I can't reproduce the problem anymore and it works now. I think we can close it.

Thanks

dc
Comment 4 E.T. Anderson 2010-04-28 16:46:25 UTC
I'm still getting this error. I have all the latest updates for Ubuntu, but I still get the error. What I find interesting is that I only get it when I click "check mail". If I allow it to download mail automatically at an interval, I never get the error.

I don't know if it's related or not, but Kmail now also has a bad problem with downloading the same messages over and over. A few times, I have ended up with three copies of the same message. It isn't all of them (I filed a separate bug for that a few months ago), it's just a couple of messages every day. If I delete those messages from the server, Kmail will pick new messages to download over again.

Needless to say, I'm perplexed.
Comment 5 Chip Bennett 2010-05-25 11:56:17 UTC
Please re-open. This bug still exists.

I dist-upgraded from Kubuntu Karmic to Lucid, and the bug appeared, including all symptoms above (emails not properly deleted from server, resulting in emails being downloaded multiple times; occasional "could not read file invalid response from server" error messages; KMail freezing).

Note, this is related to bug# 230072.
Comment 6 Craig 2010-07-07 10:20:25 UTC
This bug still exists in KMail 1.13.2 (included with Ubuntu Lucid). Interestingly, KMail is set to collect mail every x minutes, and this automatic check does not trigger the issue - this message only appears upon manually clicking the "Check Mail" button (can't envision why there would be two different internal methods of checking mail - I'm an end user and don't know how the internals work of course).

Having monitored the transaction between Kmail and server using Wireshark, it does appear to "just stop" mid transaction. KMail kills the connection to the server long before the complete contents of the email is received.
Comment 7 Craig 2010-07-12 10:47:38 UTC
Should add, you get these lines emitted when Kmail is run from a console, you click "Check Mail", and the bug is exhibited:

kmail(4160)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("pop3://USER@XXX.XXX.XXX.XXX:110/index") data size = 8 
kmail(4160)/kio (KIOJob) KIO::TransferJob::slotData: mimetype() not emitted when sending first data!; job URL = KUrl("pop3://USER@XXX.XXX.XXX.XXX:110/uidl") data size = 24 

(Actual server address omitted for obvious reasons)
Comment 8 Thomas McGuire 2010-07-30 00:00:16 UTC

*** This bug has been marked as a duplicate of bug 230072 ***