From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: self contained nnfolder
Date: Mon, 03 Sep 2001 19:51:59 -0400 [thread overview]
Message-ID: <m3ae0bn87e.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafzo8c60l1.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 03 Sep 2001 12:16:42 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> Gnus creates the archive server by default! (If
> gnus-message-archive-group is non-nil.) See the variable
> gnus-message-archive-method.
I think it works like this: if gnus-message-archive-method is set to a
select method, then it gets added to gnus-server-alist if it's not
already there.
I've successfully eliminated my archive server. I always used
fully-qualified group names in Gcc, so I just stopped using
gnus-message-archive-group, set g-m-a-m to nil, restarted Gnus, and
killed the "archive" server in the *Server* buffer. Now my
gnus-server-alist is nil, and my *Server* buffer has no listing for
the archive server. (But my gnus-server-line-format seems to be
clobbered when I start Gnus. Maybe I should upgrade to a fresh
checkout.)
> So even if you don't mention `archive' anywhere in your init files, it
> might still be there.
Depends, I guess. It is possble to get rid of it for good, if the
right piece of cruft can be found and cleaned up.
paul
next prev parent reply other threads:[~2001-09-03 23:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 16:53 Simon Josefsson
2001-08-26 16:30 ` Raymond Scholz
2001-08-26 21:20 ` Simon Josefsson
2001-08-26 22:24 ` Nevin Kapur
2001-08-27 1:22 ` Steve Youngs
2001-08-27 16:19 ` Simon Josefsson
2001-08-27 16:36 ` Nevin Kapur
2001-09-01 22:22 ` Dan Christensen
2001-09-01 23:03 ` Dan Christensen
2001-09-01 23:31 ` Kai Großjohann
2001-09-02 6:34 ` Paul Jarc
2001-09-01 23:26 ` Kai Großjohann
2001-09-02 4:41 ` Dan Christensen
2001-09-02 6:11 ` Paul Jarc
2001-09-02 10:36 ` Kai Großjohann
2001-09-02 15:51 ` Dan Christensen
2001-09-02 16:48 ` Kai Großjohann
2001-09-02 23:58 ` Paul Jarc
2001-09-03 3:35 ` Dan Christensen
2001-09-03 10:16 ` Kai Großjohann
2001-09-03 15:07 ` Dan Christensen
2001-09-03 16:31 ` Kai Großjohann
2001-09-04 1:22 ` Dan Christensen
2001-09-03 23:51 ` Paul Jarc [this message]
2001-09-04 1:38 ` Dan Christensen
2001-09-04 6:58 ` Paul Jarc
2001-09-04 14:45 ` Dan Christensen
2001-09-02 23:54 ` Paul Jarc
2001-09-03 3:49 ` Dan Christensen
2001-09-03 15:12 ` Dan Christensen
2001-09-03 23:36 ` Paul Jarc
2001-09-03 10:18 ` Kai Großjohann
2001-09-03 15:01 ` Dan Christensen
2001-09-03 15:22 ` Dan Christensen
2001-09-03 16:34 ` Kai Großjohann
2001-09-03 17:00 ` Amos Gouaux
2001-09-03 21:31 ` Kai Großjohann
2001-09-03 23:17 ` Paul Jarc
2001-09-04 0:43 ` Amos Gouaux
2001-09-04 13:41 ` Kai Großjohann
2001-09-04 14:10 ` Amos Gouaux
2001-09-03 23:23 ` Paul Jarc
2001-09-04 1:14 ` Dan Christensen
2001-09-04 1:33 ` Dan Christensen
2001-09-04 13:42 ` Kai Großjohann
2001-09-02 9:53 ` Simon Josefsson
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=m3ae0bn87e.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).