From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Sat, 14 Apr 2018 12:12:01 +0200 [thread overview]
Message-ID: <87a7u6jdvy.fsf@mat.ucm.es> (raw)
In-Reply-To: <87r2ni9kpm.fsf@tullinup.koldfront.dk>
> Uwe writes:
> You keep saying this, and it keeps being baffling.
> Are you SURE that the email you are looking at is one you _received_ and
> not a copy that was _stored_ in your local archive (equivalent of "Sent"
> folder)?
Well now I tried out the webmail interface of this particular gmail
account and the fields
from: Uwe Brauer <oub@mat.ucm.es>
to: Uwe Brauer <oub.oub.oub@gmail.com>
cc: Uwe Brauer <oub@mat.ucm.es>
bcc: Uwe Brauer <burrurr@gmail.com>
date: Sat, Apr 14, 2018 at 12:07 PM
subject: test bcc via webmail
mailed-by: mat.ucm.es
Then after sending in my INBOX there is a message
which contains the BCC field.
And I received mails from colleagues which contained BCC fields
Ok what about the following? I sent you offline a mail with a BCC field
and you tell me whether you can see it?
That would settle it?
I did that sending to my other gmail account and in that INOBOX I could
see the BCC field.
Would you do that experiment?
Uwe
next prev parent reply other threads:[~2018-04-14 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 12:06 Uwe Brauer
2018-04-11 19:52 ` Lars Ingebrigtsen
2018-04-11 21:25 ` Dan Christensen
2018-04-13 18:44 ` Uwe Brauer
2018-04-13 20:29 ` Uwe Brauer
2018-04-13 20:38 ` Lars Ingebrigtsen
2018-04-13 20:59 ` Uwe Brauer
2018-04-13 21:15 ` Lars Ingebrigtsen
2018-04-13 22:23 ` Uwe Brauer
2018-04-13 22:28 ` Lars Ingebrigtsen
2018-04-14 7:15 ` Uwe Brauer
2018-04-14 9:54 ` Adam Sjøgren
2018-04-14 10:12 ` Uwe Brauer [this message]
2018-04-14 10:38 ` Adam Sjøgren
2018-04-14 17:05 ` Uwe Brauer
2018-04-14 17:58 ` Lars Ingebrigtsen
2018-04-19 11:58 ` [Partial solution: how to warn about a possible BCC field] (was: warn about a BCC field) Uwe Brauer
2018-04-13 22:31 ` warn about a BCC field Uwe Brauer
2018-04-13 22:42 ` Adam Sjøgren
2018-04-14 7:09 ` 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=87a7u6jdvy.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).