Subject: The COLLECTION LIST again

From: Murphy <[email-masked]>
Date: Wed, 5 Jun 2002 10:54:43 +0200 (MEST)

Hi,

I defined the different collection list, each one for the different news groups:

1)  Nickname:NEWS-SONY
    Server:news.sonytel.be/nntp
    Path:#news.
    View:

2)  Nickname  : News Wrocław
    Server    : news.ict.pwr.wroc.pl/service=NNTP
    Path      : #news.
    View:

On the Collection List it looks like this:

    NEWS - SONY
        News groups on news.sonytel.be/nntp

    News Wrocław
        News groups on news.ict.pwr.wroc.pl/service=NNTP

The problem is that if go into a 1) and add some news lists like this:

    sony.sysadm
    sony.utilities

then I add some news lists from 2) like:

    pl.rec.gry.komputerowe.sprzet

I should have the such entries in each Folder List for each collection:

            News groups on news.ict.pwr.wroc.pl/service=NNTP
------------------------------------------------------------------------

    pl.rec.gry.komputerowe.sprzet

                  News groups on news.sonytel.be/nntp
------------------------------------------------------------------------

    sony.sysadm
    sony.utilities

But in fact in each collection I have all entries (all 3 news lists). It causes
the usage of each news list because from the collection 1) I can't access to
the "pl.*" news lists, and from collection 2) - to the "sony.*" lists.

I think it should be separated because otherwise it mess up the things which
should be separated. Is there a way to set it correctly, to have each
collection consist with only the elements (news-list) which belongs to this
NNTP server?

Regards,
Murphy

-- 
  __   __
  ||   ||
 -++- -++- --------------------------------------------------------
  ||\ /||  e-mail: [email-masked]           GG 107745
  ||   ||  Everything is possible - this is only a question of time
  \/564\/  --------------------------------------------------------

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------