Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: undisclosed-recipients
Date: Sun, 10 Feb 2019 21:52:06 +0100	[thread overview]
Message-ID: <87imxr8iyx.fsf@igel.home> (raw)
In-Reply-To: <878syn8np9.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Sun, 10 Feb 2019 20:09:54 +0100")

On Feb 10 2019, Adam Sjøgren <asjo@koldfront.dk> wrote:

>   To: undisclosed-recipients:;

This is the RFC2822 group of mailboxes, with the list of mailboxes being
empty.

   When it is desirable to treat several mailboxes as a single unit
   (i.e., in a distribution list), the group construct can be used.  The
   group construct allows the sender to indicate a named group of
   recipients. This is done by giving a display name for the group,
   followed by a colon, followed by a comma separated list of any number
   of mailboxes (including zero and one), and ending with a semicolon.
   Because the list of mailboxes can be empty, using the group construct
   is also a simple way to communicate to recipients that the message
   was sent to one or more named sets of recipients, without actually
   providing the individual mailbox address for each of those
   recipients.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



  reply	other threads:[~2019-02-10 20:52 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         ` Andreas Schwab [this message]
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=87imxr8iyx.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=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).