Bug 53734 – Bad default mailcap entries for postscript

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 53734 - Bad default mailcap entries for postscript

Summary:	Bad default mailcap entries for postscript

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	mailcap (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-09-17 09:06 EDT by bac
Modified:	2014-03-16 22:23 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-09-17 09:06:31 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bac 2001-09-17 09:06:26 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808

Description of problem:
The default mailcap entries for postscript print out the file, which
is almost certainly not what the user intended.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Attempt to view a postscript document in a mailcap enable appication
(e.g. mutt).

	

Expected Results:  Either no action should be associated with the type, or
a postscript
viewer should be invoked (suitably set up to avoid postscript security issues).

Additional info:

There is also `print' field in the mailcap format, which can be used
to allow the user to print a document if desired (instead of printing
being the default).

Comment 1 Bill Nottingham 2001-09-17 14:11:03 EDT

Fixed in 2.1.7-1.

Note You need to log in before you can comment on or make changes to this bug.