Thunderbird for Android: CC and BCC for each identity

[tstumpf]

Hi there!

I suggest to add the option to set CC and BCC separately/additionally for each identity on Thunderbird for Android.


Reasons:

1. Compliance and archiving obligations
Certain professions (legal, finance, healthcare) are required to archive outbound communications, typically via BCC to a dedicated archive address. This obligation is identity-specific — the private address is unaffected, the professional one is not. Setting BCC manually on every message is error-prone and unreliable in practice.

2. Team mailboxes and role-address routing
When sending from a role address (e.g. orders@, support@), users frequently need to CC or BCC a shared team mailbox or ticketing system. This is structurally tied to the identity, not to individual messages.

3. Per-account self-BCC
Many users maintain a manual sent archive in a second account (e.g. a local IMAP mailbox). Which address receives the BCC depends directly on the sending identity — a single global setting cannot cover this.

4. Error prevention in multi-identity workflows
Without per-identity defaults, the user must manually check and set CC/BCC on every message. With three or more identities carrying different requirements, this is systematic cognitive overhead that reliably produces mistakes — missed copies, wrong CC on the wrong identity.

5. Consistency with the existing identity model
Thunderbird already models identities as first-class configuration units with signature, reply-to address, and display name. CC/BCC defaults are conceptually equivalent — their absence is this rather an inconsistency in the existing model.


The option to define various identities is a great feature and a "selling point". It is a distinctive option, which moved me from inbuilt Samsung e-mail client to Thunderbird on my Android mobile.

I'm using Thunderbird 19.2 for Android app.


At work I have one Public and internal identity each one will BCC different addresses.

Regards.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.