From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: archiving oddness
Date: Thu, 09 Aug 2001 13:37:38 -0400 [thread overview]
Message-ID: <m3bslpb0cn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafelql40lu.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 09 Aug 2001 19:14:21 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> prj@po.cwru.edu (Paul Jarc) writes:
>> This doesn't (do I need to restart Gnus?):
>> (setq gnus-message-archive-method nil) ; Is this wrong?
>> (setq gnus-message-archive-group "nnmaildir:sent")
...
> I have gnus-message-archive-group set to "nnimap:INBOX" but leave
> gnus-message-archive-method at the default value. That works.
I wonder if this should be changed. If g-m-a-m is so troublesome,
then maybe people should be able to use g-m-a-g without creating a new
server. Or maybe not - maybe this is why g-o-m-g isn't going away.
> There is a difference between gnus-message-archive-group and
> gnus-outgoing-message-group: if you set the gcc-self parameter on a
> group, you get two Gcc headers with gnus-outgoing-message-group but
> only one (the gcc-self one) for gnus-message-archive-group.
I suppose one could work around that by setting g-o-m-g to a function
that checks for the gcc-self parameter. Where would such a function
find the current group name?
paul
next prev parent reply other threads:[~2001-08-09 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 16:44 Paul Jarc
2001-08-09 17:14 ` Kai Großjohann
2001-08-09 17:37 ` Paul Jarc [this message]
2001-08-09 21:56 ` Kai Großjohann
2001-08-09 21:57 ` Kai Großjohann
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=m3bslpb0cn.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).