Bug 3048 - mailcap-2.0.1-2 cannot process TeX attachements
mailcap-2.0.1-2 cannot process TeX attachements
Status: CLOSED NEXTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: mailcap (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-25 16:16 EDT by Steingold, Sam
Modified: 2014-03-16 22:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-09-24 23:51:44 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)

  None (edit)
Description Steingold, Sam 1999-05-25 16:16:22 EDT
I got mail with 3 attached TeX files.
I read them in Emacs/Gnus and got this:

Content-Type: application/applefile; name="edcmmhs.sty"
Content-Transfer-Encoding: base64
Content-Description: Apple file in AppleSingle stream
Content-Disposition: attachment; filename="edcmmhs.sty"

Please give a name for this Macintosh file: No name given,
exiting
Command failed:  rcvAppleSingle /tmp/mm.AxGXyH
Content-Type: application/applefile; name="edcgeo12.sty"
Content-Transfer-Encoding: base64
Content-Description: Apple file in AppleSingle stream
Content-Disposition: attachment; filename="edcgeo12.sty"

Please give a name for this Macintosh file: No name given,
exiting
Command failed:  rcvAppleSingle /tmp/mm.SJmIS4
Content-Type: application/applefile; name="edcabbrevs.tex"
Content-Transfer-Encoding: base64
Content-Description: Apple file in AppleSingle stream
Content-Disposition: attachment; filename="edcabbrevs.tex"

Please give a name for this Macintosh file: No name given,
exiting
Command failed:  rcvAppleSingle /tmp/mm.wRYaSs
Comment 1 Cristian Gafton 1999-07-28 04:14:59 EDT
assigned to notting
Comment 2 Bill Nottingham 1999-09-24 23:51:59 EDT
Fixed in mailcap-2.0.3-1.

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