Bug 312705

Summary:	kmail2 crunches some emails but not all to size 1 byte
Product:	[Applications] kmail2	Reporter:	furgl <pfurgala>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	pfurgala
Priority:	NOR
Version:	4.9.97 RC2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description furgl 2013-01-05 20:48:27 UTC

POP3 receive
filtering
some emails are stored as 1 byte fragments

find ~/.local/share/local-mail/ -type f -size 1c -ls
1691976    4 -rw-------   1 pf       users           1 Jan  5
12:03 /home/pf/.local/share/local-mail/.PP.directory/AGn/new/1356182823.3065_131.PefNB:2,S
1691987    4 -rw-------   1 pf       users           1 Jan  5
12:03 /home/pf/.local/share/local-mail/.PP.directory/AGn/new/1356302126.3051_142.PefNB:2,S
1719078    4 -rw-------   1 pf       users           1 Jan  5
12:02 /home/pf/.local/share/local-mail/.PP.directory/AGn/new/1356814854.3475_170.PefNB:2,S
1719064    4 -rw-------   1 pf       users           1 Jan  5
12:02 /home/pf/.local/share/local-mail/.PP.directory/AGn/new/1356694341.3557_156.PefNB:2,S
1691962    4 -rw-------   1 pf       users           1 Jan  5
....and some more...

this appeared in 4.8.4 and 4.8.5 and happens now after the last upgrade:

python-kde4 from 4.9.97-71.1 to 4.9.97-71.2 and
kdebase4-runtime from 4.9.97-408.1 to 4.9.97-409.1


Reproducible: Sometimes

Steps to Reproduce:
1.update KDE4.9.97 with both last patches as shown above
2.get some emails via pop
3.check "find ~/.local/share/local-mail/ -type f -size 1c -ls" for results
Actual Results:  
emails were crunched to size 1 byte

Expected Results:  
emails hould have been stored completely

Comment 1 Denis Kurz 2016-09-24 18:24:14 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 2 Denis Kurz 2017-01-07 22:48:33 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.