371783 - Certain scam mails cannot be forwarded inline as HTML

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Mike Cowperthwaite]

Noticed this while testing bug 325637.  That bug has a sample scam message that uses <area> with the illegal URL but has a valid URL for the <a> link.

When I set up to compose as HTML and use Forward Inline on that message, the compose window is a plain-text compose window, and the scammy content has been discarded because the <area> is dropped in the conversion to plain text.

If I edit the message to remove the <area> entirely, and change the URL of the <a> link to one that tests positive for scam, Forward Inline works as expected.

If I edit the message to replace both URLs with a non-scam one, Forward Inline works as expected.

Steps to reproduce:
1) Integrate attachment 210513 [details] into a mail folder.
2) Open the message; observe that it's detected as a scam.
3) Forward Inline as HTML (may require changing setting for the identity used to actually reply -- note that the cited attachment has an X-Account-Id header)

Actual results:
3) Plain Text compose window, showing the legal URL (plus the junk-filter-deception text, in this particular message).  (No message in Error Console.)

Expected results:
3) HTML compose window with all HTML contents as in original message

I see this with TB 2b2-0221 and 3a1-0226, Win2K.

Comment 1

[Mike Cowperthwaite]

Oh -- testing with Seamonkey 1.1 and 1.5a-0210, this symptom doesn't occur -- it's specific to Thunderbird.

Comment 2

[buovjaga]

Now it works correctly. Closing.

Thunderbird 52.1.0 (32-bit)
Windows 7 64-bit