Suggestion: New feature for Thunderbird: A "Bcc" category, possibly called "BccV" that makes all BccV's visible just to each other.
Please suggest, to the authors of Thunderbird, the addition of a new feature that I think would be widely embraced: The option to make some, or all, of the recipients receiving blind copies visible to each other, even though still invisible to the principal recipients marked “To:”. This new feature might be called “BccV:” with the capital “V” standing for “Visible”, and capitalized to call attention to it, so that it is not confused with the current, and continuing feature, “Bcc:”.
Here are the details:
(1) Recipients marked “BccV:” would be visible to all other recipients marked “BccV:” and only to them.
(2) Recipients marked “Bcc:” would continue to be invisible to all other recipients (as now), and that would include all recipients marked “To:”, and all recipients also marked “Bcc:”, AND all recipients marked “BccV:”.
Chosen solution
Thunderbird operates according to internet standards, known as RFCs (Request For Comments).
e.g. https://tools.ietf.org/html/rfc5321 https://tools.ietf.org/html/rfc3501 https://tools.ietf.org/html/rfc1939
You would have to change these first. There's no point in any one email client doing something unilaterally, since servers and other clients wouldn't understand it.
Read this answer in context 👍 1All Replies (2)
Chosen Solution
Thunderbird operates according to internet standards, known as RFCs (Request For Comments).
e.g. https://tools.ietf.org/html/rfc5321 https://tools.ietf.org/html/rfc3501 https://tools.ietf.org/html/rfc1939
You would have to change these first. There's no point in any one email client doing something unilaterally, since servers and other clients wouldn't understand it.
Zenos said
Thunderbird operates according to internet standards, known as RFCs (Request For Comments). e.g. https://tools.ietf.org/html/rfc5321 https://tools.ietf.org/html/rfc3501 https://tools.ietf.org/html/rfc1939 You would have to change these first. There's no point in any one email client doing something unilaterally, since servers and other clients wouldn't understand it.
excellent answer :)