262052 - MailNews shows alert "is not a registered protocol" with php attachments

Status: RESOLVED EXPIRED

(MailNews Core :: MIME, defect)

Description

[[:nickname]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 MultiZilla/1.6.4.0b
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910

I've sent myself an email which two PHP script attachments. The next day I tried
to view them, the Suite always hangs when I click to view this message (I see
the sender and the list of attachments, but then everything hangs).

I've made a (hopefully) 1:1 mime dump of the message (with mutt). I've tried
e.g. bouncing the email with mutt to my account again, mozilla still hangs with
the bounced message too.

The email contains data I can't make public but I'm willing to bounce it to
anyone who is seriously into fixing this bug, given that the content will not be
made public.

Thanks for you understanding.

Reproducible: Always
Steps to Reproduce:
1. Login to my imap account
2. Select the specific message
3. the compelte suite hangs

Actual Results:  
Mozilla hangs

Expected Results:  
Mozilla should not hang

Comment 1

[[:nickname]]

some addition:
I was able to move the message around by right clicking on it and specify the
destination folder; this way the message would not get displayed and saved me
from a hang of the suite. So it really seems to be about displayed the message I
guess. HTH

Comment 2

[[:nickname]]

With
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040927
I get a "Alert" message box saying "is not a registered protocol".

As it seems, MailNews tries to display the *.php files as html, because I see
the form control in these files, etc. I'm attaching a screenshot. Note that I've
disabled Javascript and Plugins for Mailnews.

Comment 3

[[:nickname]]

Attachment: Screenshot showing the alert box

Comment 4

[[:nickname]]

regarding my last comment: it does not hang the browser anymore and I can
download the attachments with no problems. Only the alert box is remaining.

Adjusted subject and severity.

Comment 5

[Mike Cowperthwaite]

See bug 236212.  In order for the .php attachments to not be detected as 
text/html when sending the message, you have to add a type (e.g. text/php) to 
the Helper Applications preference.

Comment 6

[[:nickname]]

Ok, but what does MailNews do here, see the Screenshot? Does it try to execute
any javascript? Is this the right thing to do?

Thanks for the bug reference!

Comment 7

[Mike Cowperthwaite]

(In reply to comment #6)
> Ok, but what does MailNews do here, see the Screenshot? Does it try to execute
> any javascript? Is this the right thing to do?

The one thing I've seen where that error message comes up -- specifying the 
error without an actual protocol (i.e. unlike "irc: is not a...") -- is a bug 
having to do with following a link to a local anchor within an HTML mail.  I 
have no idea whether or how that might apply to your situation.

Comment 8

[[:nickname]]

Thanks for this pointer. I try and see if I can narrow down it. The documents
contain only a small fraction of PHP code, actually. Most part of the page is
Markup, CSS and much JS.

Comment 9

[Mike Cowperthwaite]

I just ran across bug 210164, that had a patch checked in yesterday, which 
addresses the "not a registered protocol" popup issue.  Try a build from today 
and see if the problem still exists.

Comment 10

[Mike Cowperthwaite]

Markus Fischer, is this bug still a problem for you?  See comment 9.

Stefan, I'm cc'ing you because you wrote the patch for bug 210164, which might 
have fixed this bug.  Altho it's not clear to me what the patch status *is* for 
that bug, as the sr'd patch has been marked obsolete.

Comment 11

[Stefan Borggraefe]

(In reply to comment #10)
> Stefan, I'm cc'ing you because you wrote the patch for bug 210164, which might 
> have fixed this bug.

No, Scott wrote it.

> Altho it's not clear to me what the patch status *is* for 
> that bug, as the sr'd patch has been marked obsolete.

I think the most current patch of bug 210164 was checked in. It fixed the bug
for Thunderbird only. MailNews wasn't fixed and the fix that was used for
Thunderbird is not suitable for the suite. ;-)

Markus: is this bug a duplicate of bug 210164? See bug 210164 comment 4.

Comment 12

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 13

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.