110061 - Can't determine attachment type (other than view-source)

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[GA]

Hello Mail / News --

I'm on WinTel and do business with folks on Mac (hahahah).   I frequently
receive msgs from them with attachments -- with no wintel suffix to determine
file type (eg. .doc, .xls, .gif).    The messages I receive have content-type
correctly specified by mac client MUA.  

Issue -- I can't determine content-type for unknown attachment in Mozilla
Mail/News without viewing msg source (LAME).   Yes, Mail/News automatically
takes care of this for me upon open -- but this doesn't help me when I want to
save (and add appropriate wintel doc-type suffix).

I recommend the "attachments" in msg view pane to be hot-link to popup window
detailing attachments:  a) content-type (from mime encoding), b) individual size
of each message.

Note:  Messenger v4x DID show content-type for such messages.
example:
http://www.garretta.com/attach-messeng4.jpg

now same message with Mozilla Mail/News (bad):
http://www.garretta.com/attach-mozilla1.jpg

Thx -GA

Comment 1

[scottputterman]

The icons give some indication at least.  Reassigning to ducarroz.  This may be
a dup.

Comment 2

[Jean-Francois Ducarroz]

the icon tell you which kind of document it it but I agree we can do better.
Normally, the front-end should already have all the needed info to do the job.
Reassign to varada. 

Comment 3

[Brant Gurganus]

[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420