From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Gnus and nil secondary select methods?
Date: 19 Apr 2001 15:30:05 +0200 [thread overview]
Message-ID: <vafvgo1qaoy.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87lmox6n5y.fsf@harpo.homeip.net> (Samuel Padgett's message of "19 Apr 2001 09:20:57 -0400")
On 19 Apr 2001, Samuel Padgett wrote:
> Hm. Wonder why nnml is in there? Could this be causing the
> problem?
>
> (setq gnus-message-archive-method '(nnml ""))
Yes.
> If so, how can I archive messages using the nnml, but persuade Gnus
> not to read from my mail spool?
(setq mail-sources nil)
Or maybe (setq gnus-message-archive-method '(nnml ""
(nnml-get-new-mail nil))).
kai
--
The passive voice should never be used.
next prev parent reply other threads:[~2001-04-19 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 2:14 Samuel Padgett
2001-04-19 9:07 ` Kai Großjohann
2001-04-19 13:20 ` Samuel Padgett
2001-04-19 13:30 ` Kai Großjohann [this message]
2001-04-19 14:05 ` David S. Goldberg
2001-04-20 1:02 ` Samuel Padgett
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=vafvgo1qaoy.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).