Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: undisclosed-recipients
Date: Thu, 14 Feb 2019 20:53:11 +0100	[thread overview]
Message-ID: <87sgwqtae0.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87a7j2m01f.fsf@mat.ucm.es>

Uwe writes:

> Thunderbird/Seamonkey does not support it neither.

Thunderbird puts "To: undisclosed-recipients: ;" (notice the space!) in
the email when I try sending an email with two Bcc values and no To.

The email in the Sent folder looks like this:

 · https://koldfront.dk/misc/tb-bcc-no-to.png

And here is the explanation, from the Thunderbird 60.5.0 source code, as
included in Debian:

  asjo@tullinup:/usr/src/thunderbird$ ag -B1 -A3 undisclosed-recipients thunderbird-60.5.0/comm/mailnews/compose/src/nsMsgCompUtils.cpp
  383-  // If we don't have disclosed recipient (only Bcc), address the message to
  384:  // undisclosed-recipients to prevent problem with some servers
  385-
  386-  // If we are saving the message as a draft, don't bother inserting the undisclosed recipients field. We'll take care of that when we
  387-  // really send the message.

The email received like this:

  From: Adam Sjøgren <irene@koldfront.dk>
  Subject: Test Bcc, no To in Thunderbird 60.5.0
  To: undisclosed-recipients: ;
  Date: Thu, 14 Feb 2019 20:33:31 +0100

  Testing two Bcc values, nothing in To:

So I guess you are using a different version of Thunderbird?


  Best regards,

    Adam

-- 
 "It's my chainsaw                                            Adam Sjøgren
  Division is mine"                                      asjo@koldfront.dk




  reply	other threads:[~2019-02-14 19:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 13:23 undisclosed-recipients Uwe Brauer
2019-02-09 18:23 ` undisclosed-recipients Garreau, Alexandre
2019-02-10  4:56   ` undisclosed-recipients Eric Abrahamsen
2019-02-10 17:51     ` undisclosed-recipients Uwe Brauer
2019-02-10 19:09       ` undisclosed-recipients Adam Sjøgren
2019-02-10 20:52         ` undisclosed-recipients Andreas Schwab
2019-02-10 23:15           ` undisclosed-recipients Eric Abrahamsen
2019-02-11 19:09           ` undisclosed-recipients Uwe Brauer
2019-02-11 19:12             ` undisclosed-recipients Adam Sjøgren
2019-02-11 20:37               ` undisclosed-recipients Uwe Brauer
2019-02-11 20:43                 ` undisclosed-recipients Adam Sjøgren
2019-02-11 21:30                   ` undisclosed-recipients Andreas Schwab
2019-02-11 21:41                     ` undisclosed-recipients Adam Sjøgren
2019-02-11 22:19                       ` undisclosed-recipients Uwe Brauer
2019-02-18 21:07                       ` undisclosed-recipients Uwe Brauer
2019-02-18 21:26                         ` undisclosed-recipients Adam Sjøgren
2019-02-11 22:20                     ` undisclosed-recipients Uwe Brauer
2019-02-11 22:29                     ` undisclosed-recipients Uwe Brauer
2019-02-14 19:53                       ` Adam Sjøgren [this message]
2019-02-14 20:03                         ` undisclosed-recipients Adam Sjøgren
2019-02-11 22:18                   ` undisclosed-recipients Uwe Brauer
2019-02-14 19:58                     ` undisclosed-recipients Adam Sjøgren
2019-02-11 19:18             ` undisclosed-recipients Adam Sjøgren
2019-02-11 19:03         ` undisclosed-recipients Uwe Brauer
2019-02-11 19:08           ` undisclosed-recipients Adam Sjøgren
2019-02-11 20:33             ` undisclosed-recipients Uwe Brauer
2019-02-11 19:10         ` undisclosed-recipients Eric Abrahamsen
2019-02-11 19:14           ` undisclosed-recipients Adam Sjøgren
2019-02-10 17:54   ` undisclosed-recipients Uwe Brauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgwqtae0.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).