Subject: Re: Bug (ID WZ5DY): Port specification not honored in folder description

From: Mark Crispin <[email-masked]>
Date: Wed, 15 Feb 1995 22:48:21 -0800

This is a known bug in collection expansion in Pine 3.91.  Pine fails to 
build a full mailbox expanded name from the collection with the port 
specification.

The c-client library (Pine's low-level code) does, in fact, implement
*{host2:11919/nntp}comp.foo.bar, as a test with the G command will
demonstrate. 

-- Mark --

On Wed, 15 Feb 1995, Penio Penev wrote:

> I have the pollowing lines in my .pinerc
> 
> news-collections=News *{host1/nntp}[],
> 	More news *{host2:11919/nntp}[]
> 
> host1 is my primary server, and there is a server on host2:11919 for 
> experimental purpouses.
> 
> When I try to expan the folder in the folder list screen, I get the 
> complain, that host2,119 rejects connection. That is true -- nobody is 
> listening to 119. But why is pine going to 119 at all? It should try to 
> connect to 11919 instead.
> 
> I know why -- most probably it was not envisioned, and thus -- not
> implemented. Implementation of this feature could have potentially many uses.
> Mailing list archives and news groups archives can be maintained and served
> by NNTP and IMAP, besides gopher and WAIS. Pine is a fine front end for
> message-based archive searching, and its potential uses as such should be
> encouraged. 
> 
> Along these lines, if pine is used to connect to a large archive 10s of Ks
> of messages, it is better _not_ to read all headers before giving control 
> to the user to place their selection.
> 
> --
> Penio Penev <[email-masked]> 1-212-327-7423

---

From: Penio Penev <[email-masked]>
Date: Wed, 15 Feb 1995 16:13:42 GMT