Bug#530741: set all my mails marked NEW as OLD
Package: kmail Version: 4:4.2.2-1 Severity: critical I'm using mutt to read my emails and kontact to use a variety of PIM application, especially for my calendar and contacts, occasionnally taking notes (but not email). Today I opened kontact and it complained about many .summary files not being up to date, and just after that, all my mails previously marked NEW in the Maildirs in ~/Mail were suddenly marked OLD instead, which is a huge loss of information for me (I now have to browse them all to try and recover which mails I already have read or not). How come kmail's component in kontact MODIFIED my data without me using it?! And why such a nonsensical modification?! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kmail depends on: ii kdebase-runtime 4:4.2.2-1 runtime components from the offici ii kdelibs5 4:4.2.2-2 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.2-1 core libraries for KDE PIM 4 appli ii libc6 2.9-12 GNU C Library: Shared libraries ii libgcc1 1:4.4.0-5 GCC support library ii libkdepim44:4.2.2-1 KDE PIM library ii libkleo4 4:4.2.2-1 certificate based crypto library f ii libkontactinterfaces4 4:4.2.2-1 KDE Kontact interface library ii libkpgp4 4:4.2.2-1 gpg based crypto library for KDE ii libksieve44:4.2.2-1 KDE mail/news message filtering li ii libmimelib4 4:4.2.2-1 KDE mime library ii libphonon44:4.3.1-1 Phonon multimedia framework for Qt ii libqt4-dbus 4.5.1-2Qt 4 D-Bus module ii libqt4-network4.5.1-2Qt 4 network module ii libqt4-qt3support 4.5.1-2Qt 3 compatibility library for Qt ii libqt4-xml4.5.1-2Qt 4 XML module ii libqtcore44.5.1-2Qt 4 core module ii libqtgui4 4.5.1-2Qt 4 GUI module ii libstdc++64.4.0-5The GNU Standard C++ Library v3 ii perl 5.10.0-22 Larry Wall's Practical Extraction ii phonon4:4.3.1-1 metapackage for Phonon multimedia Versions of packages kmail recommends: ii procmail 3.22-16Versatile e-mail processor Versions of packages kmail suggests: pn clamav | f-prot-installer none (no description available) ii gnupg 1.4.9-4GNU privacy guard - a free PGP rep ii gnupg-agent 2.0.11-1 GNU privacy guard - password agent ii kaddressbook 4:4.2.2-1 KDE address book ii kleopatra 4:4.2.2-1 KDE Certificate Manager ii pinentry-gtk2 [pinentry-x11] 0.7.5-3GTK+-2-based PIN or pass-phrase en ii spamassassin 3.2.5-4Perl-based spam filter using text -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530741: set all my mails marked NEW as OLD
tags 530741 upstream thanks Hello, On 2009 m. May 27 d., Wednesday 15:27:53 Pierre THIERRY wrote: Package: kmail Version: 4:4.2.2-1 Severity: critical I'm using mutt to read my emails and kontact to use a variety of PIM application, especially for my calendar and contacts, occasionnally taking notes (but not email). Today I opened kontact and it complained about many .summary files not being up to date, and just after that, all my mails previously marked NEW in the Maildirs in ~/Mail were suddenly marked OLD instead, which is a huge loss of information for me (I now have to browse them all to try and recover which mails I already have read or not). How come kmail's component in kontact MODIFIED my data without me using it?! And why such a nonsensical modification?! If ~/Mail is where kmail is set up to store your mails, what do you expect? ~/Mail has not been default since some 3.x version ( ~/.kde/share/apps/kmail is now default). I see that you could not have known kmail defaults but I don't think this is only kmail fault, it is also a user error as both applications are set up to use the same folder for mail storage. Hence I believe the severity should be lowered but I'm not doing it just now. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#530741: set all my mails marked NEW as OLD
Scribit Modestas Vainius dies 27/05/2009 hora 16:14: If ~/Mail is where kmail is set up to store your mails, what do you expect? I used kmail a bit, ages ago, so maybe this setup was just carried through various upgrades. Still, what is the meaning of turning all my nex mails into old ones without me even seeing their subject? I see that you could not have known kmail defaults but I don't think this is only kmail fault, it is also a user error as both applications are set up to use the same folder for mail storage. Couldn't the two applications be nice to each other? mutt wouldn't do any modifications to the mail storage without a clear request from the user, I'd like the same behaviour from kmail. Hence I believe the severity should be lowered but I'm not doing it just now. Kmail's current behaviour combined with me having used before led me to lose a whole lot of valuable information, without even asking anything from kmail, so I still think the severity is that high, but I'm obviously biased, as I'm pissed by what happened, so you should have the final word. Quickly, Pierre -- nowhere@levallois.eu.org OpenPGP 0xD9D50D8A signature.asc Description: Digital signature
Bug#530741: set all my mails marked NEW as OLD
severity 530741 important thanks Hello, On 2009 m. May 27 d., Wednesday 19:04:49 Pierre THIERRY wrote: I used kmail a bit, ages ago, so maybe this setup was just carried through various upgrades. Still, what is the meaning of turning all my nex mails into old ones without me even seeing their subject? I see that you could not have known kmail defaults but I don't think this is only kmail fault, it is also a user error as both applications are set up to use the same folder for mail storage. Couldn't the two applications be nice to each other? mutt wouldn't do any modifications to the mail storage without a clear request from the user, I'd like the same behaviour from kmail. kmail is known not to be very reliable when it comes to handling corrupt or out-of-sync indices. This is exactly what happened in your case. kmail went mad and made all mails read (as per default I guess). I agree that kmail should improve its index handling but this is a long standing issue and it will go away once kmail gets akonadi support for mail storage (at least that's how I understand it). Hence I believe the severity should be lowered but I'm not doing it just now. Kmail's current behaviour combined with me having used before led me to lose a whole lot of valuable information, without even asking anything from kmail, so I still think the severity is that high, but I'm obviously biased, as I'm pissed by what happened, so you should have the final word. I agree but it is still an error on your side. I believe such kind of problems were the main reason the default mail storage folder was changed to kmail private location. So you are a victim here only because you used to be a kmail user a LONG LONG item ago and set up the same mail folder for mutt. Hence lowering severity. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#530741: set all my mails marked NEW as OLD
severity 530741 normal thanks On Wednesday 27 May 2009 18:04:49 Pierre THIERRY wrote: Scribit Modestas Vainius dies 27/05/2009 hora 16:14: If ~/Mail is where kmail is set up to store your mails, what do you expect? I used kmail a bit, ages ago, so maybe this setup was just carried through various upgrades. Still, what is the meaning of turning all my nex mails into old ones without me even seeing their subject? I see that you could not have known kmail defaults but I don't think this is only kmail fault, it is also a user error as both applications are set up to use the same folder for mail storage. Couldn't the two applications be nice to each other? mutt wouldn't do any modifications to the mail storage without a clear request from the user, I'd like the same behaviour from kmail. Hence I believe the severity should be lowered but I'm not doing it just now. Kmail's current behaviour combined with me having used before led me to lose a whole lot of valuable information, without even asking anything from kmail, so I still think the severity is that high, but I'm obviously biased, as I'm pissed by what happened, so you should have the final word. The core problem here is that you configured several apps to use the same data, data in a format that is not very well defined, and have left several important details of being effective implementation specific. I'm pretty sure that if Maildir had been a very well defined format with a well defined semantics of new, seen and other flags, several apps could nicely access the same maildir without problems, but this is as I see it not the case. I'm pretty sure that considering mutt the reference implementation is also not right. I'm downgrading the severity, and I'm in doubt wether this is a bug at all in kmail. /Sune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
