From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: mail-default-headers and gnus
Date: Wed, 31 Mar 2010 08:15:27 -0500 [thread overview]
Message-ID: <87r5n0d440.fsf@lifelogs.com> (raw)
In-Reply-To: <2a1fc4bf-4e5a-4f57-b12c-11d7e415154e@z35g2000yqd.googlegroups.com>
On Wed, 31 Mar 2010 02:21:00 -0700 (PDT) Francis Moreau <francis.moro@gmail.com> wrote:
FM> I tried to remove "Bcc" header field instead of "Gcc" (as your example
FM> do) but it doesn't work I still receive 2 copies of the email.
FM> Do you know why ?
Try it out as I explained, with `C-x C-e'. Do you see the Bcc removed
but the Gcc left in?
Ted
next prev parent reply other threads:[~2010-03-31 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 12:32 Francis Moreau
2010-03-30 13:27 ` Ted Zlatanov
2010-03-30 13:33 ` Francis Moreau
2010-03-30 21:03 ` Ted Zlatanov
2010-03-31 9:21 ` Francis Moreau
2010-03-31 13:15 ` Ted Zlatanov [this message]
2010-03-31 13:53 ` Francis Moreau
2010-03-31 16:54 ` Ted Zlatanov
2010-03-31 19:18 ` Lowell Gilbert
2010-03-31 20:07 ` Francis Moreau
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=87r5n0d440.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).