From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus-message-archive-group not producing a Gcc header
Date: Thu, 16 Dec 2010 19:17:08 -0500 [thread overview]
Message-ID: <87aak5l0cb.fsf@uwo.ca> (raw)
In-Reply-To: <87ipytl5cg.fsf@uwo.ca>
To elaborate, I think the code should be changed to allow
gnus-message-archive-method to be nil (which should be the default), and
that the manual page Archived Messages should start with something like:
To have your outgoing messages saved in an archive group, simply set
the variable gnus-message-archive-group to the full group name,
including the select method prefix. For example,
(setq gnus-message-archive-group "nnimap+imap.example.com:Sent")
And that should be enough for most users, especially those using imap.
Then the manual page could go on to more complicated set-ups:
If you don't have an existing server that can be used for storing
outgoing mail, see gnus-message-archive-server below.
The variable gnus-message-archive group can also be set to:
a list of strings
... [fill in the same list of possibilities]
If you want to set-up a special server for archiving messages,
you can use the gnus-message-archive-method variable.
... fill in more here ...
But this last part is so complicated. The default nnfolder "archive"
server created on first use, the gnus-update-message-archive-method
variable, etc. Maybe it can be avoided? Maybe just give sample code the
user can use to add an nnfolder server to gnus-secondary-select-methods,
and then they can use the it in the -archive-group variable?
Dan
next prev parent reply other threads:[~2010-12-17 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 1:43 Dan Christensen
2010-12-06 14:45 ` Lars Magne Ingebrigtsen
2010-12-06 15:21 ` Julien Danjou
2010-12-06 16:32 ` Dan Christensen
2010-12-16 17:46 ` Lars Magne Ingebrigtsen
2010-12-16 22:29 ` Dan Christensen
2010-12-17 0:17 ` Dan Christensen [this message]
2010-12-17 9:29 ` Julien Danjou
2010-12-17 16:41 ` Lars Magne Ingebrigtsen
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=87aak5l0cb.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).