From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: nnimap sent mail
Date: Mon, 11 Jun 2007 20:44:38 +0200 [thread overview]
Message-ID: <87fy4yz5yh.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <y68ir9u8i2a.fsf@contents-vnder-pressvre.mit.edu>
On Mon, 11 Jun 2007 14:25:17 -0400, David wrote:
> Not the popular answer, I know, but I have Gnus Bcc: outgoing mail to
> myself.
> (setq message-required-mail-headers
> (nconc message-required-mail-headers
> (list '(Bcc . "dmaze@mit.edu"))))
> Then my sorting rules pick out mail either to or from an individual, so
> all of my correspondence with people that have their own mail groups can
> show up as a threaded conversation in the respective group.
Another way to get the same effect is to set the group parameter
gcc-self for your mailgroups:
`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::).
(Not that I suggest you change your setup, of course).
Best regards,
Adam
--
"Money always takes the place of life" Adam Sjøgren
asjo@koldfront.dk
prev parent reply other threads:[~2007-06-11 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 9:02 Dick Hoogendijk
2007-06-10 10:42 ` poppyer
2007-06-10 11:38 ` Dick Hoogendijk
2007-06-10 16:50 ` Andrew Aylett
2007-06-10 17:01 ` Hadron
2007-06-10 17:43 ` Mark T.B. Carroll
2007-06-10 20:20 ` Dick Hoogendijk
2007-06-10 11:54 ` Hadron
2007-06-10 11:27 ` Adam Sjøgren
2007-06-10 11:40 ` Dick Hoogendijk
2007-06-11 18:25 ` David Z Maze
2007-06-11 18:44 ` Adam Sjøgren [this message]
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=87fy4yz5yh.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).