[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#24783: option missing for interoperability: leave/keep mails in local inbox
From:       hans () ecke ! ws
Date:       2001-04-25 23:44:19
[Download RAW message or body]

Package: kmail
Version: 1.2 (using KDE 2.1.1 )
Severity: wishlist
Installed from:    Red Hat Linux 7.0
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-79)
OS:                Linux 2.2.17-8smp i686
OS/Compiler notes: 

Hi!

First thanks for a really nice program. I tried it the last couple days and \
it is really slick. I like especially the PGP/GPG connectivity.

However, I will never use it alone on this computer. A very simple reason: \
sometime I will login from outside with a character terminal and use pine \
(mutt/elm) to check my mail. Or if I don't want to wait for kmail to \
startup (start X, start kde, start kmail) I will use a console based \
mailer.

In this, it is quite unfortunate that kmail uses its own inbox in \
                Mail/Inbox. Imagine: 
* I read a mail with kmail and decide to leave it in my inbox to answer it \
                later
* the next time, I use pine - but the above mail is gone into ~Mail/inbox. \
Now I have to tell pine to go into this special folder. My whole workflow \
is broken.

The same problem with procmail. Why do I need to do something special to \
use procmail? Pine is fine if procmail writes into ~Mail. Why can't kmail?

I suppose its all an issue of the .index files. I see at least a couple \
                ways how to solve this:
* check modification time on mail folders (or checksums). If somebody other \
                than kmail changed a folder, rebuild the .index files
* How does pine do it? AFAIK they also use persistent information in some \
special mail in each folder (or only the inbox?). Yet pine is able to play \
nice with other mailers and procmail.

I really appreciate all the time you put into this. But if kmail doesn't \
get more interoperable on the local system I won't be able to use this. Of \
course this is no great threat, but I image other people having the same \
problem.

Thanks a lot

Hans

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)


[prev in list] [next in list] [prev in thread] [next in thread]