597973 - all custom html tags are stripped when put in signature. for examle, the moz-do-not-send=true tag.

Status: RESOLVED DUPLICATE of bug 596797

(Thunderbird :: Message Compose Window, defect)

Description

[Gabe Hiemstra]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4

none of the custom tags works in signatures. moz-do-not-send used to work, but now this simple tag gets stripped, thus disabling me from using dynamic images.

because i was using this feature for over 7 months, i could track when it stopped working:

"thursday 9 september, 2010 12:14:56, updated with version 3.1.3 (20100825123352)"

What did i try to fix it:

- tried to attach both HTML files and enter HTML manually in account setup
- tried using the style="" to append custom attributes / values in the style tag, instead of using tags directly.
- using a "-" (dash) prefix to the tag (-moz-do-not-send)
- every possible combination of the above statement
- using the about:config editor to append the "img" of the following preference name: "mailnews.display.html_sanitizer.allowed_tags" : img(alt,title,longdesc,src,moz-do-not-send,style)

none of this worked. all custom tags / style attributes get stripped

Reproducible: Always

Steps to Reproduce:
1. use any custom html-tag in signature or custom style= attribute
2. send email
3. read email
Actual Results:  
custom tag/attribute is no longer present in signature.

Expected Results:  
custom tag/attribute should be present in signature no matter what i want to enter!

why am i required to send a screenshot of the bug???

Comment 1

[Mark Banner (:standard8)]

I believe most of this is a duplicate of bug 596797

Comment 2

[Gabe Hiemstra]

some of it yes, but i could not find this using the search provided when creating this ticket.

also, this covers the entire lack of functionality, whereas the other ticket only gives details on 1 specific feature.

anyway, im not here to judge

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)
> some of it yes, but i could not find this using the search provided when
> creating this ticket.
yep sometimes earching sucks ...

> 
> also, this covers the entire lack of functionality, whereas the other ticket
> only gives details on 1 specific feature.

I'll make it a dup. Feel free to open tickets for the other issues. Try to keep one ticket per issue.

Comment 4

[Gabe Hiemstra]

fine with me, i just hope this issue gets solved very soon ! lots of customers are missing all the action ;)