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: Sun, 10 Feb 2019 20:09:54 +0100	[thread overview]
Message-ID: <878syn8np9.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87pnrzlegr.fsf@mat.ucm.es>

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.

Let's try the same from outlook.com:

  From: Adam Sjøgren <[redacted]@outlook.com>
  Subject: This is a test of Bcc only from Outlook.com
  Date: Sun, 10 Feb 2019 18:17:07 +0000

  From: Adam Sjøgren <[redacted]@outlook.com>
  Subject: This is a test of Bcc only from Outlook.com
  Date: Sun, 10 Feb 2019 18:17:07 +0000

So at least one part of Microsoft doesn't.

Let's try from some smaller players; Tutanota:

  From:  <[redacted]@tutanota.com>
  Subject: Bcc only from Tutanota
  Date: Sun, 10 Feb 2019 19:22:59 +0100 (CET)

  From:  <[redacted]@tutanota.com>
  Subject: Bcc only from Tutanota
  Date: Sun, 10 Feb 2019 19:22:59 +0100 (CET) (10 minutes, 42 seconds ago)

nope; but Protonmail does, emulating Google:

  From: Adam Sjøgren <[redacted]@protonmail.com>
  Subject: Bcc only from ProtonMail
  To: undisclosed-recipients:;
  Date: Sun, 10 Feb 2019 18:27:28 +0000
  Reply-To: Adam Sjøgren <[redacted]@protonmail.com>

  From: Adam Sjøgren <[redacted]@protonmail.com>
  Subject: Bcc only from ProtonMail
  To: undisclosed-recipients:;
  Date: Sun, 10 Feb 2019 18:27:28 +0000
  Reply-To: Adam Sjøgren <[redacted]@protonmail.com>

Yahoo! Mail doesn't:

  From: Adam Sjøgren <[redacted]@yahoo.com>
  Subject: Bcc only from Yahoo! Mail
  Date: Sun, 10 Feb 2019 18:28:54 +0000 (UTC)
  Reply-To: Adam Sjøgren <[redacted]@yahoo.com>

  From: Adam Sjøgren <[redacted]@yahoo.com>
  Subject: Bcc only from Yahoo! Mail
  Date: Sun, 10 Feb 2019 18:28:54 +0000 (UTC)
  Reply-To: Adam Sjøgren <[redacted]@yahoo.com>

And neither does Aol Mail (guess they are the same these days, at least
the email sent from Aol Mail was delivered by a yahoo.com-host):

  From:  <[redacted]@mcom.com>
  Subject: Bcc only from Aol Mail.
  Date: Sun, 10 Feb 2019 18:31:17 +0000 (UTC)

(I'm too lazy to wait for the other one to arrive; I've got greylisting
on.)


Why do you find it attractive to have this value in To:‽


  Best regards,

    Adam

-- 
 "I pragmatically turn my whims into principles!"             Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2019-02-10 19:09 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       ` Adam Sjøgren [this message]
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         ` 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=878syn8np9.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).