Sun mail attachments get displayed incorrectly

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
enhancement
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Philip Andrew, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

16 years ago
Descr.
Reporter:
Please read http://www.mozilla.org/quality/bug-writing-guidelines.html.

1. What build are you using ?
2. What do you mean with "Sun mail attachment" ? 
   (Can you can add a attachment to this bug with a sample mail)
*** Bug 108368 has been marked as a duplicate of this bug. ***
*** Bug 108370 has been marked as a duplicate of this bug. ***
(Reporter)

Comment 4

16 years ago
Created attachment 56437 [details]
Raw mail message text
(Reporter)

Comment 5

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012
BuildID:    2001101202

Lately, I've started interacting via e-mail with someone who reads and sends
mail from a Sun system (I haven't checked, but I think they're using 'mailtool'
or 'dtmail').

Whenever this person sends me messages with attachments, the attachment gets
garbled and displayed as text in the message pane; additionally, it doesn't
appear in the "attachments" pane with the proper name, just a name of the form
"Part X.Y".  This is particularly problematic when the attachment is large,
because viewing, replying to, or forwarding the message takes an huge amount of
time (and even sometimes hangs Mozilla, although I haven't been able to
reproduce this on a reliable basis).

See the attached file for the raw text of the mail message.


Reproducible: Always
Steps to Reproduce:
1. Save the raw text attachment as a new message folder file
2. Start up Mozilla-Mail
3. Open new folder
4. View message

Actual Results:  1. The attachment is named "Part 1.2" in the "Attachments" pane.
2. The following is displayed on my message pane:

----- Begin message pane view -----
Hi Phil,

Here's an example of bad data from a Sun mailer.

-Bob

[ Separator line ]

??ï?]ð²Æ?á?ÅR
i~)îaJqÌÅ?[I»Ú??în¶?pqk?Aâq?â7Î?ûþ±NÀh#7÷½ÿyd÷?K²4N?Äî??Oiÿÿ?;÷ßë?rÍ¡;Iðïõ
x?G¡
îÑ~Þþdz?B!?B!?B!?B!ÓwÐ0ð
----- End of message pane view -----


Expected Results:  1. I should only see the text

    Hi Phil,

    Here's an example of bad data from a Sun mailer.

    -Bob

in the message pane.

2. The attachment name in the "Attachments" pane should be
   "testcase.tgz".

Comment 6

16 years ago
How many email clients actually display the message properly?

The message uses, what looks like, a special format for messages like a
multipart mime message except it being developed by sun.

reporter, is this a RFE for support for such a format?

Comment 7

16 years ago
Created attachment 77804 [details]
perl script to conver from mailtool format to mime format

maybe one day this will be part of mozilla. 
i doubt many people use this format anymore.
i couldn't find a spec for this format anywhere.
(Reporter)

Comment 8

16 years ago
I'm not sure whether this is an RFE.  I had been exchanging
e-mails with this correspondent before and it seems to me I
had never had the problem before 0.9.5; but i could be mis-
taken about this.

The format used here is an old way of doing attachments, as
UU-encoded blocks.  Is it only Sun that did things this way
in the "olden days"?

Anyway, my correspondent seems to have switched to 'dtmail', with
MIME encoding, so I don't have the problem anymore.  However, if
there are still people out there with clients sending attachments
as UU-encoded blocks, then this is a useful enhancement.

Comment 9

16 years ago
This is a valid RFE, people are still using mailtool ...

Though I doubt it will get implemented any time soon.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: esther → message-display

Comment 10

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 11

9 years ago
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 12

9 years ago
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
Group: core-security

Comment 13

9 years ago
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

Updated

9 years ago
Group: core-security

Comment 14

8 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.