61810 - uuencoded attachments are not displayed when message is labeled as MIME

Status: NEW

(MailNews Core :: MIME, defect)

Description

[Henrik Gemal]

If Mozilla encounters a news/mail posting that has this in it's body:
begin 644 pc023.gif
M1TE&.#EA1@+2`?<`
CRM.>^O2G0`VJ4(=*%-2B&O6H2$VJ4
`
end

mozilla will uudecode the file and present it as an attachment with the filename 
"pc023.gif".

If could be *nice* if Mozilla would show image files inline.
So if the filename is ".gif", ".jpg", etc... then the uudecoded file would be 
shown inline.

Comment 1

[scottputterman]

reassigning to ducarroz

Comment 2

[Keyser Sose]

*** Bug 92352 has been marked as a duplicate of this bug. ***

Comment 3

[Jean-Francois Ducarroz]

Can somebody attach a sample test message to this bug report. Thanks

Comment 4

[carljohan]

Attachment: A MIME email with uuencoded images

Comment 5

[carljohan]

Attachment: A non-MIME email with uuencode images

Comment 6

[carljohan]

The first message doesn't display the images, but the second one
displays all three images, at least in Mozilla-0.9.3. (The nightly
I'm using doesn't show any images inline)

The offending line in the Mime-mail is:

MIME-Version: 1.0

Comment 7

[Wesha]

*** Bug 158573 has been marked as a duplicate of this bug. ***

Comment 8

[Mike Young]

updated behavior: build 20020721 Win98SE

The message with MIME-Version: 1.0 displays the uu-encoded text of the attachments.

The message without MIME specified displays the three images as attachments and
also inline.

Adjusting summary to reflect this.

Comment 9

[Mike Cowperthwaite]

*** Bug 233061 has been marked as a duplicate of this bug. ***

Comment 10

[Devoti Paolo]

Thunderbird 0.9
Just received an email with uuencoded pdf attachments from enel.it  
Had to export the email and **shame** import it with outlook to detach the files.
This is not a minor futurable.
At least in Thunderbird it should be fixed.

Comment 11

[Aleksandar Milivojevic]

Re: Additional Comment #10 From Devoti Paolo

Seems that for majority of people it is a minor thing.  I'm currently the only
one who voted for this bug to be fixed :-(

Comment 12

[Marcel Cox]

I just want to add some information to clarify the scope of this problem:

As indicated earlier, the problem occurs when reading a message with an
UUencoded attachment while the message header contains some MIME information
(either "MIME-Version: something" or "Content-Type: something").
This causes Netscape/Mozilla/Thunderbird not to parse the message body for
UUeconded attachments.

Now where does this problem occur mostly?

The problem mostly occurs in newsgroups. UU encoding is not common in email, but
it is very common for posting attachments in newsgroups. Now there are a couple
of newsreaders that include MIME information int he message header, even when
posting UUencoded attachements. Some examples of such newsreaders are:
Virtual-Access : http://www.virtual-access.org/
Gemini : http://www.intellegit.com/software/gemini/
Dialog : http://www.40tude.com/dialog/index.htm
I guess there might be others as well.

Now the Mozilla family is one of the only newsreaders that have this problem.
All newsreaders I have tried so far do not show this problem. Only the Mozilla
family suffers from this problem, and it makes the Mozilla family a rather
substandard newsreader compared to the competition.

Marcel

Comment 13

[Mike Cowperthwaite]

Henrik Gamal, your original report states that the UUencoded items show up as attachments -- do you still see this symptom with anything?  Using a 2a1 build of Thunderbird, the attachments on this bug exhibit the problem as described in comment 8: the undecoded text shows up in the message body.  If you have a message that exhibits the original symptom with a current build, please attach it to this bug.


(In reply to comment #12 [Marcel Cox])
> As indicated earlier, the problem occurs when reading a message with an
> UUencoded attachment while the message header contains some MIME information
> (either "MIME-Version: something" or "Content-Type: something").

Interesting; where did you see a reference to the Content-Type issue?  It's not mentioned earlier in this bug.  But you're quite correct; for instance, if attachment 52366 [details] from this bug is given a Content-Type header, it displays as undecoded text as well.

Comment 14

[Marcel Cox]

(In reply to comment #13)
> Interesting; where did you see a reference to the Content-Type issue?  It's not
> mentioned earlier in this bug.  But you're quite correct; for instance, if
> attachment 52366 [details] [edit] from this bug is given a Content-Type header, it displays as
> undecoded text as well.

I found this from my own investigations. At the time I posted the information, I was mostly using VA as newsreader and the Mozilla people were always mad at me because they couldn't read my attachments.

Marcel

Comment 15

[Dan Yefimov]

*** Bug 335100 has been marked as a duplicate of this bug. ***

Comment 16

[Man-wai Chang]

Is this "bug" being ignored?

Thunderbird 3.1.7 still does NOT decode inline UUencode text as an attachment. I need to View Message Source, File, Save Page As (test.txt), then use uudecode.exe on test.txt to see the image.

I added another example UudecodeFailedMsgSource.txt as attachment.

Comment 17

[Man-wai Chang]

Attachment: Thunderbird 3.1.7 failed to decode and display inline UUencode text

UudecodeFailedMsgSource.txt

Comment 18

[Ludovic Hirlimann [:Usul]]

(In reply to comment #16)
> Is this "bug" being ignored?

No we are just waiting for someone to write a patch as the helpwanted keyword tells.

Comment 19

[Serguei E. Leontiev]

Thunderbird 17.0.10esr and Thunderbird 24 failed to decode and display attachments 52365 and 499639

Comment 20

[james]

Still a problem Thunderbird 24.5.0

Comment 21

[Ludovic Hirlimann [:Usul]]

Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.