Bug 91598

Summary:	KMail tries to relaunch to view text/rfc822-headers attachment
Product:	[Unmaintained] kmail	Reporter:	Tristan Miller <psychonaut>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	martin
Priority:	NOR
Version First Reported In:	1.7.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	E-mail message with offending attachment Screenshot of nonsensical dialog prompt

Description Tristan Miller 2004-10-18 17:11:35 UTC

Version:           1.7.1 (using KDE KDE 3.3.1)
Installed from:    SuSE RPMs

When clicking on an attachment of type text/rfc822-headers, KMail opens a dialog window asking how to view the attachment.  The dialog incorrectly specifies the name of the attachment as a double quote character (`"').  The default option is to open the attachment with KMail.  Selecting the default option causes KMail to try to launch itself again in order to view the attachment.

A couple things need to be fixed:

1) Unnamed attachments should trigger the message `Open unnamed attachment of type foo/bar?' instead of the nonsensical `Open attachment "?'

2) KMail should not launch a separate process to view an attachment of type text/rfc822-headers.  It should be opened in a new window just like a message/delivery-status attachment.

See attached test case and screenshot.

Comment 1 Tristan Miller 2004-10-18 17:12:28 UTC

Created attachment 7931 [details]
E-mail message with offending attachment

Comment 2 Tristan Miller 2004-10-18 17:14:44 UTC

Created attachment 7932 [details]
Screenshot of nonsensical dialog prompt

Comment 3 Tristan Miller 2009-04-25 23:32:01 UTC

Confirming bugs still exists in KDE 4.2.2. I suspect this might not have anything to do with the MIME type, but rather the fact that the attachment has no name.

Comment 4 Martin Koller 2009-09-03 23:01:23 UTC

KDE 4.3.1 simply displays the headers when I select the attachment in the message structure viewer, so no problem here.