Closed Bug 273104 Opened 20 years ago Closed 20 years ago

Option to choose from HTML or Plain Text per contact instead of domain

Categories

(Thunderbird :: Preferences, defect)

defect
Not set
minor

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bugzilla, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: 

If you compose your messages in html, to send a message in plain text to a
contact, as a rule, you have to go to option->composition->send
options...->plain text domains tab->add.
And you have to add the domain you want it to send the message in plain text.
If you select an adress with that restriction, you still compose the email in
HTML, and you have no indication that the e-mail will be sent in plain text.

Another problem I think exists ( I couldn't test this )is if you have a
restrition about html e-mail in some adressess of a domain( i.e. company
internal mailing list ) but not in others ( i.e. co-workers ). As far as I can
understand having this option, based on domain, don't allow users to have this
flexbility.

My sugestion is that this is moved to an option in the contact sheet for each
contact, so when you view the properties of a contact in your address book, you
can set up how do you like to send e-mail to that contact ( html or plain text
), and when you add one e-mail address that can only receive plain text emails
to a to: cc: or bcc: field maybe changes it's background color ( like https in
firefox) to inform the user that that adress will only be sent a plain text
version of the email.

I see that as a radio input with 3 options:
None selected: Use the default setting in the options
HTML selected: Send all emails to that user using html
Plain text select: Send all emails to that user using plain text

Reproducible: Always
Steps to Reproduce:
I'm ashamed of myself to not see that what I've asked was already there

Sorry for the spam
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.