Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Why is my sent to recipient labeled UNDISCLOSED?

  • 3 réponses
  • 2 ont ce problème
  • 3 vues
  • Dernière réponse par car-nuts

more options

I sent an email for an address in my book with a copy to myself. The email I received had this recipient marked as Undisclosed. When I checked so did the sent email. Even though I am the author I cannot it appears Unmasked this recipient. What occurred and can I unmask to verify who got it?

I sent an email for an address in my book with a copy to myself. The email I received had this recipient marked as Undisclosed. When I checked so did the sent email. Even though I am the author I cannot it appears Unmasked this recipient. What occurred and can I unmask to verify who got it?

Solution choisie

Actually close. Think I figured it out. Apparently when there is No Recipient and only a BCC or maybe a CC, Thunderbird plugs in that false Undisclosed Recipient as a default. Not really an accurate default imo. The clue is that it was so identified on my sent message, not just the copy I got back. Thanks

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (3)

more options

That sounds rather like what should happen if you had set both addressees to use "Bcc:". Do you think that is possible?

If you're using gmail, then you won't see the Bcc'd addresses in your Sent folder either. Google choose to redact them.

more options

Solution choisie

Actually close. Think I figured it out. Apparently when there is No Recipient and only a BCC or maybe a CC, Thunderbird plugs in that false Undisclosed Recipient as a default. Not really an accurate default imo. The clue is that it was so identified on my sent message, not just the copy I got back. Thanks

more options

In my case I found this issue was related to double entries in the sent file, Haven't solved it yet: https://support.mozilla.org/en-US/questions/1183704