[Bug 79685] kmail does not honour umask on saving attachments

davidblunkett dav1dblunk3tt at hotmail.com
Thu Jun 19 09:00:30 BST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=79685         




------- Additional Comments From dav1dblunk3tt hotmail com  2008-06-19 10:00 -------
RO when I open a document or drag a document to the Desktop, I haven't tried saveas...

It appears that my concern is with a different but (outlined below)

My main concern is opening a document directly - a long time back opened documents were R/W (umask in fact) but some newbies lost edits because they did not realise they were opened in /tmp and kmail cleaned them before quitting.  The developers then enforced RO opening.  In my opinion this was wrong - the correct action would be to: get kmail to check for changes and only clean if no changes had been made to files in /tmp but to optionally issue a warning otherwise AND for the RO to be optional and by default selected.  In this case no one who didn't know what was going on would have a problem and the rest of us could have RW / umask if we wanted.


For several years I just built my own kmail with a hack to remove the RO enforcement but ran into trouble building lately and filed a bug which got marked as the same as this one.

What I am after is an option to set the perms of documents you open directly from kmail and a bit of smart handling of changes to tmp files. I only personally care about the former.  My problem is I get sent loads of word docs, the formatting breaks in translation to OO and OO won't let you change RO documents so you have to go through a save:as process (currently broken in the current SUSE OO) or drag the file to the Desktop, change its perms and then open it. All just to fix the borken font so you can read it and discard it.  This happens to me 1/2 dozen times a day and is really annoying.  Yes, I agree OO should be wiser, yes I agree my colleagues should be more enlightened etc but no of this can change and it does not seem unreasonable that kmail allows the user to set the permissions of the files it opens.



More information about the Kdepim-bugs mailing list