Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: ignore bcc when followup
Date: Wed, 22 Feb 2017 23:03:44 +0100	[thread overview]
Message-ID: <87bmttdgsf.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87ino1hpu1.fsf@mat.ucm.es>

Uwe writes:

> I receive an email which goes like
>
> From: Joe
> To: John
> Bcc: Uwe
>
> Now I, Uwe hit, by mistake, followup, instead of reply, then they mail
> looks at it should
>
> From: Uwe
> To: Joe
> CC: John
>
> Which is bad, because John did not know that mail was sent to me.

Ah, I misunderstood you. I thought you meant that the follow up
contained a copy of the Bcc.

It would make sense for Gnus to ask you, when doing a wide reply/follow
up (i.e. including the original recipient) to an email you were Bcc'ed
on, if that is really what you meant.

I have an advice on gnus-summary-reply that asks me if I really wanted
to reply, if I am in a newsgroup (where I usually want to follow up) -
similar to that.

> Did I explain myself?

Yup.

I actually did what you described just the other day.


  Best regards,

    Adam

-- 
 "Vi är inte riktigt kloka när man tänker efter."             Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2017-02-22 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 13:50 Uwe Brauer
2017-02-22 19:10 ` SOLVED (was: ignore bcc when followup) Uwe Brauer
2017-02-23  7:46   ` SOLVED David Engster
2017-02-23  8:41     ` Bcc Adam Sjøgren
2017-02-23 18:21       ` Bcc David Engster
2017-02-22 19:54 ` ignore bcc when followup Adam Sjøgren
2017-02-22 21:34   ` Uwe Brauer
2017-02-22 22:03     ` Adam Sjøgren [this message]
2017-02-22 22:23     ` Adam Sjøgren
2017-02-23 10:24       ` Uwe Brauer
2017-02-23 12:49         ` Adam Sjøgren
2017-02-23 14:10           ` Uwe Brauer
2017-02-23 14:54             ` Adam Sjøgren
2017-02-23 15:33               ` 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=87bmttdgsf.fsf@tullinup.koldfront.dk \
    --to=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).