Gnus development mailing list
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: various  independent  "mail servers" and the nnml backend
Date: Tue, 19 Jul 2005 15:54:25 -0400	[thread overview]
Message-ID: <y68u0iqzi4u.fsf@all-night-tool.mit.edu> (raw)
In-Reply-To: <87u0iq1ox5.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 19 Jul 2005 21:11:50 +0000")

Uwe Brauer <uwe_brauer@mat.ucm.es> writes:

> I just deleted all my .newsrc newsrc.eld files and restarted gnus, I
> add a nnml server, so the corresponding buffer looks like (nnml
> "NNML")
>
> However independent whether I edit the server in order to obtain
> something like this
>
> (nnml "NNML-Archive" (nnml-directory "/home/oub/Mail/NNML-Archive"))

Out of curiousity, why do you want two separate nnml backends?  Within
a single backend, you could create, say, nnml:archive.* and
nnml:current.* groups and achieve segregation that way.

> Another question: it seems that I can use the secondary select
> method in order to select a server, but I could also to it in the
> way described above, even for nnimap or nntp servers. Which method
> is better?

From what I can tell, your mail backend (the thing that sucks in mail
as per mail-sources) must be either gnus-select-method or one of
gnus-secondary-select-methods; the backend that gets the "blessed"
group names without prefixes is gnus-select-method (or you can set
that to nnnil); and otherwise it's fine for all of your other backends
to be in neither list and subscribe to individual foreign groups from
them.  If you have to do some configuration to make the backend work
it might be useful to put into gnus-secondary-select-methods too, but
otherwise subscribing to nntp+my.news.server:gnu.emacs.gnus seems to
work just fine.

(I have two separate Gnus setups.  The one I'm posting from uses nnnil
as gnus-select-method, has nnml in gnus-secondary-select-methods, and
I read a couple of foreign nntp groups.  On the other one
gnus-select-method is nnimap, gnus-secondary-select-methods is nil,
and there are a couple of nnrss groups.)

  --dzm




  reply	other threads:[~2005-07-19 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 16:09 Uwe Brauer
2005-07-18 15:22 ` Ted Zlatanov
2005-07-18 17:47   ` Uwe Brauer
2005-07-19 14:16     ` Ted Zlatanov
2005-07-19 17:03       ` Uwe Brauer
2005-07-19 19:36       ` Uwe Brauer
2005-07-19 21:11       ` Uwe Brauer
2005-07-19 19:54         ` David Z Maze [this message]
2005-07-20 19:14           ` Uwe Brauer

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=y68u0iqzi4u.fsf@all-night-tool.mit.edu \
    --to=dmaze@mit.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).