Version: 1.7.1 (using KDE 3.3.1, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-3) OS: Linux (i686) release 2.6.9-1-686-smp Relating to 31498: This is not "easily configured". I would like to be able to have a logon with its Mail folder that he fully owns (instead of all the sharing kludges with which I have been playing) and sharable folders (permissions set by administrator and honored and left alone by KMail!) to which users could save non-private messages for common purposes. So one might have My Mail----inbox ----etc Public messages---category 1 ----------category 2 ----------etc etc. Should be straightforward to implement.
On Friday 17 December 2004 08:19, David Baron wrote: > This is not "easily configured". I would like to be able to have a logon > with its Mail folder that he fully owns (instead of all the sharing kludges > with which I have been playing) and sharable folders (permissions set by > administrator and honored and left alone by KMail!) to which users could > save non-private messages for common purposes. > > So one might have > My Mail----inbox > ----etc > Public messages---category 1 > ----------category 2 > ----------etc > etc. You can and should to this with an IMAP server running locally. It provides access control list based user management on a per folder basis, and allows to export the same folder on disk multiple times without concurrent access and locking problems. > Should be straightforward to implement. If you say so ....
Fair enough. Actually exim will distribute the mail to any mboxes I want and KMail need only display them and allow moving messages. It may or may not be really necessary or desirable to go to IMAP and Maildir and such (but I could be convinced :-))
Can we have this similar to how thunderbird allows you to have multiple pop3 profiles each with its own top level local folder? I mean imap is great and all, but still this pop3 isnt really done away with. Would be nice to have support for root level local folders
I thought I'd reply to this one as bug #31498 is closed... (In reply to comment #3) > Can we have this similar to how thunderbird allows you to have multiple pop3 > profiles each with its own top level local folder? I mean imap is great and I agree, I love the way how Mozilla/Thunderbird allows one to have its own top-level POP3 folders. That is an absolutely must for me. Filtering solutions or running a local IMAP server just doesn't seem like a clean/convenient way to do it. However, my issues with using Mozilla/Thunderbird right now is that they do not currently support maildir, which makes backing up huge mbox files a pain. > all, but still this pop3 isnt really done away with. Would be nice to have > support for root level local folders > Indeed, some of us still rely a lot on POP3 and having top-level POP3 folders just like the IMAP ones would be sweet. Now, I'm not quite sure what the OP was referring to in regards to the permissions thing, but I've had a quick look and it seems multiple top-level POP3 folders will not be trivial to implement, starting with accountdialog.cpp I presume. Nevertheless, I'm going to try to implement this, as it sure seems a lot easier than implementing maildir support in Mozilla. :)
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
On Sunday 19 August 2012 03:46:10 Luigi Toscano wrote: > https://bugs.kde.org/show_bug.cgi?id=95323 > > Luigi Toscano <luigi.toscano@tiscali.it> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - CC| |luigi.toscano@tiscali.it > Resolution|UNMAINTAINED |WAITINGFORINFO > > --- Comment #6 from Luigi Toscano <luigi.toscano@tiscali.it> --- > Instead of creating a new feature request, please confirm here if the > wishlist is still valid for kmail2. If still relevant, it would be still valid.
(In reply to comment #7) > If still relevant, it would be still valid. Given that the support for different account goes through akonadi and each account is a different resource, isn't this accomplished in kmail2? (this is a question/reminder to myself too :)