Bug 56489

Summary:	keylock pid for local files
Product:	[Applications] kmail	Reporter:	Daniel Moyne <dmoyne>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	bjoern
Priority:	NOR
Version:	1.5
Target Milestone:	---
Platform:	Mandrake RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Daniel Moyne 2003-03-27 13:40:00 UTC

Version:           1.5 (using KDE 3.1.0)
Installed from:    Mandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-1mdk)
OS:          Linux (i686) release 2.4.21pre4-1mdk

a) Now when deleting messages they no more go automatically go to the KMail garbage bin where process of these messages can be specifically handled; they are simply destroyed !
b) on mail directories when adding an e-mail list address for sending messages there is no more the possibility to send a message with a specific item with the directory pop-up menu !
c) When using a local mail box the lock file cannot be stored under "/var/spool/mail" by default as apparently no permissions are given which is ridiculous as messages are though stored there for each user until they are read by KMail !

Comment 1 Ingo Klöcker 2003-03-27 18:37:32 UTC

First of all, the next time please file a different bug reports for each bug/wish. 
 
ad a) The KMail introduction which was shown to you when you first started the new version of 
KMail told you in large friendly letters: 
"IMPORTANT CHANGE: The 'Delete' Action now irrevocably deletes messages. Use 'Move to 
Trash' to put messages into the trashcan." 
The next time please take the time to actually read the introduction. 
Why did we change it? Because KMail's behavior is now consistent with other KDE 
applications like Konqueror where you also have Delete and Move to Trash. 
 
ad b) Click with the middle mouse button on the folder to send a new message to the 
configured mailing-list. 
 
ad c) Sorry but I don't understand your problem. On my system /var/spool/mail has the 
permissions drwxrwxrwt which means everyone can create a lock file there. 
 
It seems the only problem that's left is c). I changed the summary of your bug report 
accordingly.