From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Fri, 13 Apr 2018 22:59:59 +0200 [thread overview]
Message-ID: <87lgdqakkw.fsf@mat.ucm.es> (raw)
In-Reply-To: <87k1tasuz9.fsf@mouse.gnus.org>
>>> "Lars" == Lars Ingebrigtsen <larsi@gnus.org> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>> I investigated further and indeed there is a problem.
>> As I said my university switched to gmail. Now someone sent me, using
>> his Apple Mail app, a mail with the following headers
>>
>> From: User1 <user@ucm.es>
>> Subject: Blabla
>> To: User2 <user2@ucm.es>
>> Date: Wed, 22 Feb 2017 08:39:23 +0100 (1 year, 7 weeks, 1 day ago)
>> Bcc: oub@mat.ucm.es
>>
>> So you see I am only on the BCC field which is displayed. Now I hit F
> Hm... `F'? What's that bound to? Is this in a mail group?
gnus-summary-followup-with-original
I thought this is the standard binding
>> (as I do automatically and which in this case was a big mistake because
>> it results in
>> To: User1 <user@ucm.es>
>> Subject: Blabla
>> CC: User2 <user2@ucm.es>
>> Date: Wed, 22 Feb 2017 08:39:23 +0100 (1 year, 7 weeks, 1 day ago)
>> Bcc: oub@mat.ucm.es
> Hm? That's exactly the same as the first message? Including Date: and
> all?
> If I `F' on a mail with a Bcc in it, Message seems to ignore the Bcc as
> it should...
Ok this is a misunderstanding. It is not about the BCC is about the CC
field when the original message contained a BCC field.
I try to say it again.
I am the recipient in the BCC field.
The message was not sent to me, (I was only on the BCC)
I did not pay attention and wanted to answer the sender, so when hitting
gnus-summary-followup-with-original
gnus put up the correct
TO field, which was ok
but also the CC field
extracting that information from the CC field.
Gnus behavior is correct!
If I had used gnus-summary-reply-with-original (as I should) everything
would have been fine, but I am so used to followup, (because people
often complained in the that they don't get a message when they are only
on the CC field and I use gnus-summary-reply-with-original, that is why
I am so used to gnus-summary-followup-with-original, but in the
situation I described that can for the careless user lead to
embarrassing solution, and that is why I wrote that small hack, which
might come in handy for people in similar situation.
Did I explain my problem now better?
next prev parent reply other threads:[~2018-04-13 20:59 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 [this message]
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
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=87lgdqakkw.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).