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: Sun, 10 Feb 2019 18:54:14 +0100	[thread overview]
Message-ID: <87lg2nlebd.fsf@mat.ucm.es> (raw)
In-Reply-To: <87pns0hld8.fsf@portable.galex-713.eu>

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

>>> "GA" == Garreau, Alexandre <galex-713@galex-713.eu> writes:

> I’d say use Bcc, which possibly won’t be replicated among bcc’ed
> people, while putting “undisclosed-recipients” in the To: fields. It
> will be bogus but your mail client/server will typically notice it
> itself.

Right, gnus reject to send such messages.
I can either put in the To field

    1. undisclosed-recipients <myemail@gmail.com>

    2. Or as Eric suggested leave it blank, which is probably better. 
       But I cannot do:

    3. To undisclosed-recipients; that gets rejected by gnus.



> However putting “undisclosed recipients” in “To:” when there’s no
> mailing list address seems a common convention among spammers and some
> mail-listing software and features from mail clients (already received
> news from friends like this): do you know where do that come from?
> maybe to paliate the fact the “To” is mandatory according mail RFCs?
> Is there a RFC talking about “undisclosed recipients”?

> Because it is always that two words, sometimes with a dash, sometimes
> without, sometimes with semi-colon, sometimes not, etc.

> Any idea?

I would really like to know, I have the feeling it is some mailing list
software. 

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

      parent reply	other threads:[~2019-02-10 17:54 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         ` 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   ` Uwe Brauer [this message]

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=87lg2nlebd.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).