From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: couple of questions about servers and agent
Date: Mon, 08 Jul 2002 16:14:37 +0200 [thread overview]
Message-ID: <dzcbs9iz4qa.fsf@mamut.elte.hu> (raw)
In-Reply-To: <dzcu1nal424.fsf@mamut.elte.hu>
On Mon, 08 Jul 2002, at 15:52, NAGY Andras <nagya@inf.elte.hu> wrote:
> Hm. I have `(nntp "news")' and `"nntp:news"' mixed together. I'm
> going to change everything to "nntp:news" and give the whole thing
> another try. :-)
Eliminated the duplicate nntp:news, but the double nnml:mail
persisted. Tracked it down to this line in my .newsrc.eld:
(setq gnus-server-alist '(("archive" nnml "mail")))
I'm using "nnml:mail" everywhere, but with
(setq gnus-server-alist '(("archive" . "nnml:mail")))
in .newsrc.eld Gnus signals and error ("nnml:mail" is not a list).
I've put this line here to prevent Gnus automatically creating an
(nnfolder "archive") group upon startup, which I do not need.
Removing this line eliminates the duplicate nnml:mail in the server
list, but then Gnus will create an nnfolder "archive" group and the
corresponding Mail/archive directory, despite I have the following
line in my .gnus:
(setq gnus-message-archive-method "nnml:mail")
[...Time goes by...]
Hm, the following in .newsrc.eld did the trick:
(setq gnus-server-alist '(("archive")))
No nnfolder group and no duplicates. :-)
Auto creating this nnfolder thingie independently of what select
method the user chooses for archiving should not be done, I think.
Andras
next prev parent reply other threads:[~2002-07-08 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 13:16 NAGY Andras
2002-07-08 13:25 ` NAGY Andras
2002-07-08 13:41 ` Simon Josefsson
2002-07-08 14:13 ` Kai Großjohann
2002-07-08 14:32 ` Bjørn Mork
2002-07-08 14:58 ` Kai Großjohann
2002-07-08 13:40 ` Simon Josefsson
2002-07-08 13:52 ` NAGY Andras
2002-07-08 14:14 ` NAGY Andras [this message]
2002-07-08 14:58 ` Kai Großjohann
2002-07-09 21:12 ` Paul Jarc
2002-07-08 14:45 ` NAGY Andras
2002-07-08 14:52 ` Bjørn Mork
2002-07-08 14:56 ` NAGY Andras
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=dzcbs9iz4qa.fsf@mamut.elte.hu \
--to=nagya@inf.elte.hu \
/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).