On Fri Aug 01 9:54 -0400, David Walser wrote:
> Think of it like this. If Kmail is download stuff with POP and putting it in
> ~/Mail, then it's mail from another server, not the local machine (which is a
> different server), so mails from two different servers are getting mixed in one set
> of folders (maybe desirable, but maybe not). If however Kmail is really only
> getting mail from the local server, it should probably just be doing that using the
> IMAP protocol, then it won't mess around directly in ~/Mail, and there will be no
> locking issues (it's a good general principle, don't muck with files directly when
> there's a protocol).
I propose a policy that's simple:
* The only things that can be put into ~/Mail are mbox-format
mailboxes (or symlinks thereto). Any other behavior should
be patched, either by Mdk or upstream. Packages not conforming
should be removed from the distribution.
* Ditto wrt ~/Maildir and Maildir-format mailboxes
* Users may have the option to configure their software to not
follow this policy; however, all packages must by default obey
this policy.
There is no good reason why anything but an mbox (or a symlink to an
mbox) should be in ~/Mail, and the same is true wrt ~/Maildir and the
corresponding format. AFAIC, anything else is broken and asking for
trouble. The directories in this proposed policy have been selected to
minimize disconnect with traditional policy.
> They can easily make symlinks.
Why shouldn't KMail be the one to change its behavior, especially when
it's the one that's breaking a long-standing tradition in the Unix world
for, AFAICT, no good reason.
--
Levi Ramsey
[EMAIL PROTECTED] [EMAIL PROTECTED]
Take due notice and govern yourselves accordingly.
Currently playing: Rush - Test for Echo - Test For Echo
Linux 2.4.21-3mdk
11:57:01 up 5 days, 14:44, 10 users, load average: 0.48, 0.40, 0.44
