Bug 296181 - kmail cannot fetch mails after a mail with no body was received
Summary: kmail cannot fetch mails after a mail with no body was received
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-16 22:13 UTC by Bruno Haible
Modified: 2017-01-07 22:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
An example mail that causes kmail to stop fetching mails (1.24 KB, text/plain)
2012-03-16 22:15 UTC, Bruno Haible
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Haible 2012-03-16 22:13:36 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0
Build Identifier: 

kmail+kdepim version 4.7.4.

I fetch mails through POP3. I receive a lot of spam. Occasionally, one of these
spam mails has no body. kmail's behaviour in this case is:
It fetches all mails that arrived prior to that particular mail, including that particular mail, but it does not delete any of the mails.
Therefore, when I fetch mails again, the same mails arrive again, leading to duplicates.
But I can not access/download the mails that arrived that particular one!
Blocked!

I have to go out and delete the particular mail manually, like in the transcript below. After this, kmail can again fetch mails normally.

============================= TRANSCRIPT ==========================
$ telnet post.strato.de pop3
Trying 81.169.145.136...
Connected to post.strato.de.
Escape character is '^]'.
+OK POP3 server ready <52f96570x12ed9606a9ce.barnabe@pop3.strato.de>
USER bruno%haible.de
+OK Waiting for password
PASS ********
+OK User logged in, proceed. (44)
LIST
+OK 65 messages, listing follows:
1 19847
2 22202
3 27635
4 6258
5 6427
6 1303
7 2227
8 6157
9 54174
10 5798
11 13346
12 116417
13 6084
14 4606
15 4249
16 7942
17 150524
18 3093
19 2657
20 51998
21 3295
22 3314
23 4267
24 9648
25 12132
26 5002
27 5005
28 23156
29 7794
30 2209
31 4500
32 11763
33 4178
34 3610
35 4061
36 4150
37 7152
38 2774
39 11317
40 918
41 2319
42 2149
43 4964
44 3923
45 5688
46 2589
47 3995
48 3701
49 3404
50 3552
51 4648
52 7542
53 7497
54 3877
55 6844
56 3745
57 5390
58 4386
59 72790
60 3381
61 4386
62 4385
63 2193
64 7701
65 4564
.
RETR 6
+OK Message follows:
X-Envelope-From: <bruno@haible.de>
X-Envelope-To: <bruno@haible.de>
X-Delivery-Time: 1331896937
X-UID: 134488
Return-Path: <bruno@haible.de>
X-Authentication-Results: mailin.rzone.de (andre mi30) (RZmta 28.1)
        header.From=haible.de;
        dkim=pass
To: bruno@haible.de
X-RZG-CLASS-ID: mi
Received: from mo-p00-ob6.rzone.de ([IPv6:2a01:238:20a:202:53f0::1])
        by mailin.rzone.de (andre mi30) (RZmta 28.1 OK)
        with ESMTP id 407263o2GAlkeC for <bruno@haible.de>;
        Fri, 16 Mar 2012 12:22:17 +0100 (MET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1331896937; l=0;
        s=domk; d=haible.de;
        h=X-RZG-CLASS-ID:Date:From:X-RZG-AUTH;
        bh=2jmj7l5rSw0yVb/vlWAYkK/YBwk=;
        b=dgKi9yjCFvRn/841CqHHMBkhXzTipmpsZKAdGmGnKDrh5XcElFh9yUZ1ji6dLrn2bmX
        XR41E/NW728EFlvEksK4golGj5l0WqEWknYKeLUid8pJINqUKZSaxWdaZZq9Q2JFn0x95
        jUm3ihQkHULsJczIo/M8Wqp2Ufd9PNkmI5c=
X-RZG-AUTH: :Ln4Re0+Ic/6oZXR1YgKryK8brksyK8dozXDwHXjf9hj/zDNRbvY44zMkpA==
From: bruno@haible.de
Date: Fri, 16 Mar 2012 12:22:17 +0100 (MET)
Message-ID: <Y02bb7o2GB8BLD.RZmta@mo-p00-ob.rzone.de>
X-RZG-CLASS-ID: mo00
Received: from linuix.haible.de
        (dslb-088-068-070-142.pools.arcor-ip.net [88.68.70.142])
        by smtp.strato.de (jimi mo5) (RZmta 28.1 DYNA|AUTH)
        with ESMTPA id Y02bb7o2GB8BLD ; Fri, 16 Mar 2012 12:22:17 +0100 (MET)

.
.
DELE 6
+OK Message 6 deleted
QUIT
+OK Closing connection


Reproducible: Always

Steps to Reproduce:
1. Get spammed.
2. Wait until a spam mail arrives that has no body.
3. Fetch mails. The one with no body is the last one. Nothing more is received.
4. Fetch mails again. The same mails are received again. but still none of those after the mail with no body.
Actual Results:  
No mails past the particular one can be received.

Expected Results:  
A mail with empty body should be handled like all other mails.
Comment 1 Bruno Haible 2012-03-16 22:15:56 UTC
Created attachment 69682 [details]
An example mail that causes kmail to stop fetching mails
Comment 2 Denis Kurz 2016-09-24 17:57:02 UTC
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.
Comment 3 Denis Kurz 2017-01-07 22:30:34 UTC
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.