[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#332473: kmail: dangerous handling of dimap-folders



Package: kmail
Version: 4:3.4.2-2
Severity: normal

Hi KDE-maintainers,

I've posted a grave bug against kmail a few weeks ago and now I've found
another one, which is similar but not quite the same. Again it's
dangerous-dimap and it's pretty easy to lose your mails when you move
folders.

I try to reconstruct it the best I can, maybe you create a dimap account
yourself with a few folders and fill them with some spam mails in order
to see the effect.

NOTE: I'm translating the german menu-entrys into english so maybe they
are not 100% correct, I hope you still get the idea.

Assume we have two folders A and B filled with a few mails 

(1) Rightclick a folder A and choose "move to".
(2) Now chose folder B  where folder A  should be moved to.
(3) Now you should see something like this:
   B (filled with mails)
   `-A (filled with mails)

The first problem: A is *not* moved into a at this stage -- allthough the
user thinks so, because he sees it. For the users point of view
everything seemed to work well. But:

(4) Now click "Send & Receive"... A stupid panel pops up, asking what
kind of data is stored into this (which?!) folder: folders or messages.

Here are two problems:
	(a) The user has absolutely no idea whats going on here, since
	    he thinks his folder has allready been succesfully moved.
	(b) Under bad circumstances (happend to my today) you make more
	    than one move operation or even create a new subfolder and
	    then move some folder in the new created one -- now two of
	    those panels pop up -- one for the newly created subfolder
	    and one for the moved one. The problem is, that you cannot
	    see which one kmail means, because its not shown to which
	    folder the question is referring. If you choose "messages"
	    instead of "folders" for the first subdir all your mails in
	    this subdir are lost, but kmail still shows them! AGAIN:
	    kmail shows your mails are still there, but they are gone
	    because of the wrong decision.

(5) Now comes the funniest part. You've clicked "Send Receive" and think
all changes have been commited, but wrong -- you have to *restart* kmail
in order that the new mails are uploaded to the new folders. This is the
second time in one operation where kmails pretends to have done some
work but actually has not. Let's assume you forget to restart kmail and
just close it. After a while you start kmail on a different machine
(maybe laptop) but you are accessing the same dimap-account -- guess
what happens to your not-yet-uploaded mails...


I hope you where able to follow my steps please don't hesitate to ask if
I was unclear in certain points -- I know my english is not the best,
exspecially when I've lost some mails this day :)


Kind regards

Bastian



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686-smp
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages kmail depends on:
ii  kdebase-kio-plugins       4:3.4.2-3      core I/O slaves for KDE
ii  kdelibs4c2                4:3.4.2-4      core libraries for all KDE applica
ii  kdepim-kio-plugins        4:3.4.2-2      KDE pim I/O Slaves
ii  libart-2.0-2              2.3.17-1       Library of functions for 2D graphi
ii  libaudio2                 1.7-3          The Network Audio System (NAS). (s
ii  libc6                     2.3.5-6        GNU C Library: Shared libraries an
ii  libfontconfig1            2.3.2-1        generic font configuration library
ii  libfreetype6              2.1.10-1       FreeType 2 font engine, shared lib
ii  libgcc1                   1:4.0.2-2      GCC support library
ii  libice6                   6.8.2.dfsg.1-8 Inter-Client Exchange library
ii  libidn11                  0.5.18-1       GNU libidn library, implementation
ii  libjpeg62                 6b-10          The Independent JPEG Group's JPEG 
ii  libkcal2b                 4:3.4.2-2      KDE calendaring library
ii  libkdepim1a               4:3.4.2-2      KDE PIM library
ii  libkleopatra0a            4:3.4.2-2      KDE GnuPG interface libraries
ii  libkmime2                 4:3.4.2-2      KDE MIME interface library
ii  libkpimidentities1        4:3.4.2-2      KDE PIM user identity information 
ii  libksieve0                4:3.4.2-2      KDE mail/news message filtering li
ii  libmimelib1c2             4:3.4.2-2      KDE mime library
ii  libpng12-0                1.2.8rel-5     PNG library - runtime
ii  libqt3-mt                 3:3.3.5-1      Qt GUI Library (Threaded runtime v
ii  libsm6                    6.8.2.dfsg.1-8 X Window System Session Management
ii  libstdc++6                4.0.2-2        The GNU Standard C++ Library v3
ii  libx11-6                  6.8.2.dfsg.1-8 X Window System protocol client li
ii  libxcursor1               1.1.3-1        X cursor management library
ii  libxext6                  6.8.2.dfsg.1-8 X Window System miscellaneous exte
ii  libxft2                   2.1.7-1        FreeType-based font drawing librar
ii  libxi6                    6.8.2.dfsg.1-8 X Window System Input extension li
ii  libxinerama1              6.8.2.dfsg.1-8 X Window System multi-head display
ii  libxrandr2                6.8.2.dfsg.1-8 X Window System Resize, Rotate and
ii  libxrender1               1:0.9.0-2      X Rendering Extension client libra
ii  libxt6                    6.8.2.dfsg.1-8 X Toolkit Intrinsics
ii  perl                      5.8.7-5        Larry Wall's Practical Extraction 
ii  xlibs                     6.8.2.dfsg.1-8 X Window System client libraries m
ii  zlib1g                    1:1.2.3-4      compression library - runtime

Versions of packages kmail recommends:
ii  kdebase-kio-plugins           4:3.4.2-3  core I/O slaves for KDE
ii  kdepim-kio-plugins            4:3.4.2-2  KDE pim I/O Slaves
ii  procmail                      3.22-11    Versatile e-mail processor

-- no debconf information



Reply to: