Version:           3.5 (using KDE 3.5.2 Level "a" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.11-default

When getting an ics attachment with kmail and clicking it, kmail offers to import the file into Korganizer.  

KOrganizer then pops up asking for confirmation on action being taken on the file 'file:///tmp/kde-username/meeting.ics_[XXXXXX].ics' where XXXXXX is again a random string (presumably from mkstemp()).

I did a little trace on this and it appears that this file is created and korganizer is being fed the correct path to it (by somehow exec-ing 'korganizer --import %u'). 

After doing some tracing I see that korganizer clones or forks itself upon startup and the original process exits shortly thereafter. Now, kmail unlinks the file as soon as the 'handler' (korganizer in this case) exits and the cloned korganizer process doesn't try to open it until after asking the user if he wants to merge with existing calendar yadayada and getting a response.  By that time the file no longer exists and nothing gets (silently) imported. 

Since Kmail's behavior is propably the most correct behavior, methinks Korganizer should get a handle on the file before the call to fork/clone and/or make a copy of it to use in the import.

cheers.