From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus-message-archive-group not producing a Gcc header
Date: Mon, 06 Dec 2010 11:32:33 -0500 [thread overview]
Message-ID: <87d3pezwta.fsf@uwo.ca> (raw)
In-Reply-To: <sa3tyirdj0i.fsf@cigue.easter-eggs.fr>
Julien Danjou <julien@danjou.info> writes:
> On Mon, Dec 06 2010, Dan Christensen wrote:
>
>> I have gnus-message-archive-method set to nil and
>> gnus-message-archive-group set to "nnimap+rocky:Sent", but I don't get
>> any Gcc header on my outgoing messages.
>>
>> Until the last pull I used gnus-outgoing-message-group for this purpose
>> and it worked fine, but now it's obsolete. Any ideas?
>
> I've the same setup without any problem.
> FYI, the code in `gnus-inews-insert-gcc' does this
>
> (var (or gnus-outgoing-message-group gnus-message-archive-group))
>
> So both var should work the same.
>
> Could you try to edebug this function and see what it does for you?
That function contains
((null gnus-message-archive-method)
;; Ignore.
nil)
so nothing happens. I don't like having an extra "archive" server
in the server buffer, when I just use an existing server for saving
outgoing messages.
I tried setting gnus-message-archive-method to '("dummy") and things
seem to work, but I think nil should be a valid value when
gnus-message-archive-group contains a server prefix. (And this
seems to match the documentation.)
Actually, the documentation is unclear. I think this paragraph is
left over from when gnus-outgoing-message-group was not obsolete:
That's the default method of archiving sent messages. Gnus offers a
different way for the people who don't like the default method. In
that case you should set `gnus-message-archive-group' to `nil'; this
will disable archiving.
Dan
next prev parent reply other threads:[~2010-12-06 16:32 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 [this message]
2010-12-16 17:46 ` Lars Magne Ingebrigtsen
2010-12-16 22:29 ` Dan Christensen
2010-12-17 0:17 ` Dan Christensen
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=87d3pezwta.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).