157836 - other protocols need to be blocked from within mail messages

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

We recently implemented the pref for "don't load remote images in mail 
messages".

does that block just http or other protocols?  I think just http.

I'm worried about someone doing this:

<img src="ftp://foo.com/cheese.gif">

and we'll send the email address that you can set as your anonymous FTP 
password.  (see Prefs | Advanced)

ducarroz says:

FTP images are not blocked in email, neither they are in the browser. If you 
think we should block them, please file a bug (assigned to myself and cc'ing 
morse).

I am pretty sure the fix would take only one line of code (add test for ftp in 
function ShouldBlockImageBySheme in nsImgManager.cpp)

Comment 1

[Jean-Francois Ducarroz]

cc'ing morse as I thing we should block ftp images as well in the browser window!

Comment 2

[Mitchell Stoltz (not reading bugmail)]

Steve, does this fall under Image Manager? If not, could you please reassign it
to a better owner?

Comment 3

[Stephen P. Morse]

I think this falls under the auspices of the mail team.  Reassign if you think
I'm wrong.

Comment 4

[Jean-Francois Ducarroz]

Y\that's true if we decide to block ftp images only in email. But I think we
should do it as well for the browser! Any thought?

Comment 5

[Samir Gehani]

Mail triage team: nsbeta1+/adt2

Comment 6

[(not reading, please use [e-mail] instead)]

re-assigning nsbeta1+ bugs

Comment 7

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 8

[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 9

[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