Make default encoding (for composition) a per-identity (account) option



17 years ago
10 years ago


(Reporter: Erich.Iseli, Unassigned)


Firefox Tracking Flags

(Not tracked)




17 years ago
Right now you can set the default encoding of a folder inside of an account. For
certain situations, this is a quite uncomfortable solution, since all mails
could require a specific encoding. And when composing a new message, you still
have to set the encoding manually, before you file it into a folder.

Timeless suggested to create a template with the needed encoding and request a
feature which could allow to define a template to be the standard when composing

The trouble is: I'm not really using templates... And the solution with
templates, even if nifty, is not really straight forward either... What do you
guys think?

Comment 1

17 years ago
Reporter, you should distinguish folder encoding (which is 
display encoding default) from the compose encoding (which is 
send encoding default).

1. You can set the folder viewing default with:

Edit | Prefs | Mail & Newsgroup | Message Display | Languages

which will be used to set the encoding for all newly created

2. You can set the per folder encoding with: 

Edit | Properties

** This will change each folder's default encoding.

3. You can set the default encoding for the outgoing messages

Edit | Prefs | Mail & Newsgroup | Message Composition | Composing
  Messages | Character Coding

Please explain which function does not work for you well.


Comment 2

17 years ago
Ok, imagine you have business with Chinese people and Russian people. You have a
special account for each language. However, your primary language is English.

So of course you want by default to send your mail by default with the encoding
of iso-8859-1 or similar. But
1) all folders created within the Russian account should have a russian encoding
2) all newly created messages within the Russian e-mail address should have the
russian encoding.
3) 1 and 2 also apply for the chinese account.

Now, what I need to do is manually change the encoding of every single folder
within the Russian and Chinese accounts. And manually set the message encoding
before sending a message. Because I always get the alert "The message you
composed contains characters not found in the selected Character Coding, so your
message may become UNREADABLE after you send or save it..."

I hope this is clearer.

Comment 3

16 years ago
[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.
Severity: normal → enhancement

Comment 4

14 years ago
*** Bug 145620 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey


14 years ago
Assignee: sspitzer → mail


12 years ago
Assignee: mail → nobody
Component: MailNews: Main Mail Window → MailNews: Backend
OS: Windows 98 → All
Product: Mozilla Application Suite → Core
QA Contact: esther → backend
Hardware: PC → All
Summary: [RFE]: Be able to set default encoding to an e-mail account → Make default encoding (for composition) a per-identity (account) option

Comment 5

11 years ago
It's not just the language, there are many things that should, IMO, be related to an identity:
 The language to spell check against (think bilingual writer)
 The language and the string to place above a reply (X wrote, etc) (think multilingual correspondence) The header may be in the addressee's language which may be different from the text you write in the reply.
 The encoding to use (think UTF-8 or ASCII for Chinese or English)
 The font to use (think Arial for both English and German, but not Chinese)
 The signature file to use (think different jobs by one person)
 Whether a message is signed (think personal v business)
 What column lines are wrapped at
All of this might be on a single e-mail address with a single inbox.

It is almost worth thinking that instead of identities, it ought to be possible to create separate accounts but with a shared e-mail address.


11 years ago
Duplicate of this bug: 346807


11 years ago
Duplicate of this bug: 270081


10 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.