From: Tassilo Horn <tsdh@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: gnus gmail bcc question
Date: Tue, 30 Apr 2013 15:52:32 +0200 [thread overview]
Message-ID: <87fvy8dt27.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: m2r4ht8eu3.fsf@gmail.com
Guido Van Hoecke <guivho@gmail.com> writes:
Hi Guido,
> I always send a blind copy to myself in order to attach a specific
> label to my messages, e.g. send a Bcc: guivho+emacs@gmail.com to
> attach the 'emacs' label to that message and have it automagically
> appearing in my emacs maul folder.
I use Gnus gcc-self parameter for exactly the same purpose:
--8<---------------cut here---------------start------------->8---
(setq gnus-parameters
`((,(rx "nnimap+")
;; Place a copy of sent mail in the group I'm writing from...
(gcc-self . t))
(,(rx "nnimap+Fastmail:INBOX.mailinglists.")
;; ...except for mailing list groups
(gcc-self . "nnimap+Fastmail:INBOX.Sent Items"))))
--8<---------------cut here---------------end--------------->8---
,----[ (info "(gnus)Group Parameters") ]
| `gcc-self'
| If `(gcc-self . t)' is present in the group parameter list, newly
| composed messages will be `Gcc''d to the current group. If
| `(gcc-self . none)' is present, no `Gcc:' header will be
| generated, if `(gcc-self . "string")' is present, this string will
| be inserted literally as a `gcc' header. This parameter takes
| precedence over any default `Gcc' rules as described later (*note
| Archived Messages::), with the exception for messages to resend.
|
| *Caveat*: Adding `(gcc-self . t)' to the parameter list of `nntp'
| groups (or the like) isn't valid. An `nntp' server doesn't accept
| articles.
`----
Bye,
Tassilo
next prev parent reply other threads:[~2013-04-30 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 16:46 gnus gmail bcc question Guido Van Hoecke
2013-04-29 21:58 ` eqyiel
2013-04-30 6:39 ` Guido Van Hoecke
2013-04-30 10:00 ` eqyiel
2013-04-30 13:52 ` Tassilo Horn [this message]
2013-04-30 19:20 ` Guido Van Hoecke
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvy8dt27.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).