Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: undisclosed-recipients
Date: Mon, 11 Feb 2019 20:03:47 +0100	[thread overview]
Message-ID: <87wom6i1v0.fsf@mat.ucm.es> (raw)
In-Reply-To: <878syn8np9.fsf@tullinup.koldfront.dk>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

>>> "AS" == Adam Sjøgren <asjo@koldfront.dk> writes:

> Uwe writes:
>>> I always thought it was added automatically by a MTA somewhere if you
>>> left the To: field blank. I don't think anyone types it in there manually.
>> 
>> Well not gnus.

> Like Eric Abrahamsen, I think that this bogus value
> "undisclosed-recipients" is inserted by Microsoft Exchange, Gmail or
> similar, when there is no To: field.

> To test this, I tried composing an email in the Gmail web-interface with
> two recipients in Bcc: and nowhere else. The resulting emails arrived
> with:

>   From: Adam Sjøgren <[redacted]@gmail.com>
>   Subject: Test Bcc only from Gmail
>   To: undisclosed-recipients:;
>   Date: Sun, 10 Feb 2019 19:06:20 +0100

>   From: Adam Sjøgren <[redacted]@gmail.com>
>   Subject: Test Bcc only from Gmail
>   To: undisclosed-recipients:;
>   Date: Sun, 10 Feb 2019 19:06:20 +0100

> So Gmail inserts the bogus value "undisclosed-recipients:;" in To: when
> you only put recipients in the Bcc field and leave To and Cc empty.

I use gnus and gmail smtp mail server run your experiment and received 

From: Uwe Brauer <blabla@gmail.com>
Subject: test undisclosed
Date: Mon, 11 Feb 2019 20:01:07 +0100 (2 minutes, 3 seconds ago)
Reply-To: Uwe Brauer <blabla@gmail.com>



So no undisclosed-recipients:; is inserted.

Sort of odd?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]

  parent reply	other threads:[~2019-02-11 19:03 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                       ` undisclosed-recipients Adam Sjøgren
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         ` Uwe Brauer [this message]
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=87wom6i1v0.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).