Bug 95526

Summary: "The specified folder does not exist or was not readable." error when trying to save attachment
Product: [Unmaintained] kmail Reporter: Tristan Miller <psychonaut>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tristan Miller 2004-12-20 18:54:46 UTC 
Version:            (using KDE KDE 3.3.2)
Installed from:    SuSE RPMs

Someone has sent me an attachment with the following filename:

file:///C|/DOKUME%7E1/SAUERM%7E1/LOKALE%7E1/TEMP/nsmail-1.tmp

When I right-click on the attachment and select "Save as...", up pops an error dialog that says, "The specified folder does not exist or was not readable.".  After I click on OK, I am taken to the normal file selector dialog to save the file, which proceeds without error.

I don't experience this problem with other attachments, so I think this is a consequence of the funny name.  Perhaps KMail needs to strip out the slashes from the filename before passing it on to the file selector...?
Comment 1 Tristan Miller 2005-05-08 22:15:25 UTC 
This bug seems to be a violation of RFC 2183:

2.3  The Filename Parameter

   The sender may want to suggest a filename to be used if the entity is
   detached and stored in a separate file. If the receiving MUA writes
   the entity to a file, the suggested filename should be used as a
   basis for the actual filename, where possible.

   It is important that the receiving MUA not blindly use the suggested
   filename.  The suggested filename SHOULD be checked (and possibly
   changed) to see that it conforms to local filesystem conventions,
   does not overwrite an existing file, and does not present a security
   problem (see Security Considerations below).

   The receiving MUA SHOULD NOT respect any directory path information
   that may seem to be present in the filename parameter.  The filename
   should be treated as a terminal component only.  Portable
   specification of directory paths might possibly be done in the future
   via a separate Content-Disposition parameter, but no provision is
   made for it in this draft.
Comment 2 Tristan Miller 2009-04-25 23:26:22 UTC 
Bug seems to be fixed in KDE 4.2.2.