From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: undisclosed-recipients
Date: Mon, 11 Feb 2019 21:37:11 +0100 [thread overview]
Message-ID: <87k1i6njt4.fsf@mat.ucm.es> (raw)
In-Reply-To: <875ztqyw9b.fsf@tullinup.koldfront.dk>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
>>> "AS" == Adam Sjøgren <asjo@koldfront.dk> writes:
> Uwe writes:
>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> 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.
> [...]
>> Thanks but any idea how gnus could be configured to show that behavior
>> of inserting undisclosed recipient into the To field?
> Just type in the value; I just tried, and the resulting received email looked
> like this:
I must be really tired but I tried
From: Uwe Brauer <oub@mat.ucm.es>
To: ;
Subject: test
Bcc: Uwe Brauer <blabla@blabla>, Uwe Brauer <blabla2@gmail.com>
Gnus does not send it
From: Uwe Brauer <oub@mat.ucm.es>
To: ,
Subject: test
Bcc: Uwe Brauer <blabla@blabla>, Uwe Brauer <blabla2@gmail.com>
Gnus does not send it
What do I miss?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-02-11 20:37 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 ` Uwe Brauer [this message]
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=87k1i6njt4.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).