Gnus development mailing list
 help / color / mirror / Atom feed
From: Francisco Solsona <solsona@deprof.fciencias.unam.mx>
Cc: ding@gnus.org
Subject: Re: Proper way to create new foreign groups
Date: 21 Jul 1998 09:28:11 -0500	[thread overview]
Message-ID: <m2emvfmg78.fsf@dep1.fciencias.unam.mx> (raw)
In-Reply-To: Jake Colman's message of "21 Jul 1998 09:27:13 -0400"

Jake Colman <colman@ppllc.com> writes:

> I use a named nnml backend to process mailing lists.  I've set up
> nnmail-split-methods to sort the mail to the proper group.  What is the
> approved method of introducing new foreigh groups to gnus?

	You don't normally create (G m) new mail groups, you wait for
Gnus to show them. If you're talking about groups in a foreign server, 
for instance, then you can browse the server and use "u" to
(un)subscribe to new groups.

> 1) Use 'G m' to create the group.

	Don't do this. Gnus will create the "mail" (not foreign) group 
for you.

> 2) Set up nnmail-split-method to process the group
> 3) Wait for mail to arrive.

	That's it, that's all you have to do. Sometimes the new group
is listed as zombie (use `A Z` to list all zombie groups). What I
normally do, is check if mail has arrived to the new group, and if it
has, then I do `j <new-group>`, set its level at 2, and then enter it.

	Note that <new-group> includes the name of the backend and the 
"server name", e.g. I use the following:

      (setq gnus-secondary-select-methods '((nnml "private")))

so, my mail groups are named: nnml+private:mail-group-name

> I think the problem is that I use a named nnml backend in my
> secondary-select-method. 

	I don't think so, I also use a named nnml backend and I've
never had problems with it.

>  When I create the foreign group, it gets associated with the
>  default, unnamed, nnml backend.  When mail arrives, the next time I
>  enter gnus I see the group two times: once with an unnamed nnml
>  backend, and once with the named nnml backend.  Is there a better
>  way to do this?

	Yep, let Gnus take care of the creation of the group. The
problem is that a group has a name and a select method; where the
select method is a list with the first element being the backend and
the second the server name and AFAIK you cannot pass that list when
using `G m`.

hth,
Francisco
-- 
Matrimony is the root of all evil.


      parent reply	other threads:[~1998-07-21 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-21 13:27 Jake Colman
1998-07-21 14:24 ` Lars Magne Ingebrigtsen
1998-07-21 14:28 ` Francisco Solsona [this message]

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=m2emvfmg78.fsf@dep1.fciencias.unam.mx \
    --to=solsona@deprof.fciencias.unam.mx \
    --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).