Subject: pine 3.90 as a POP client

From: "Julian M. Gordon" <[email-masked]>
Date: Thu, 18 Jan 1996 14:20:55 -0800 (PST)

I was wondering if pine 3.90 could be used as a POP client?

If you're interested, here are the results of my investigations:
My answer at this point would be NO, as when I try
	incoming-folders= {mail.bnbcomp.net/pop}jewels
in my pinerc. 
I get:
	[Can't open mailbox {mail.bnbcomp.net/pop}jewels: invalid remote 
	specification]
The "invalid ..." says it all.

What I am less clear about is whether IMAP is a superset of POP, and 
then I would assume that IMAP would be backward compatible.
But this might be true for the server, not for the client..
So I try:
	incoming-folders= {mail.bnbcomp.net/imap}jewels
I get
	[Can't connect to branwyn.bnbcomp.NET,143: Connection refused]
Same for 
	incoming-folders= {mail.bnbcomp.net}jewels
Upon doing some digging, I come to the conclusion that 143 is the tcp 
port for the IMAP protocol and that my server does not have an IMAP  
server.

I posted my question on comp.mail.pine, and received two answers,
one was off-base, the other gave me the idea to use incoming-folders.

Thanks for any help you can give me,

Julian Gordon.

--------------------------------------------------------------------
| /\/\ Julian Gordon             /\/\     ([email-masked])       ->
| \/\/ 9411 Glen Arbor Rd,      /\/\/\    (408) 335-8397          ->
| /\/\ Ben Lomand, CA 95005
--------------------------------------------------------------------

---

From: Terry Gray <[email-masked]>
Date: Fri, 19 Jan 1996 11:47:58 -0800 (PST)

Julian,
Your conclusion is correct: IMAP is a functional, but *not* a syntactic,
superset of POP, and the two protocols use different ports.  You are also
correct in inferring that your site is probably not running an IMAP server
if you get a connection refused on port 143.

POP does not have the capability to name mailboxes; it only has the notion
of a single "maildrop"  (i.e. your INBOX) --hence the "jewels" name made
the specification invalid.

As a test, press G (for GoTo) and enter:  {mail.bnbcomp.net/pop}
or use that string as your "inbox-path".

Note also that:

 o There are some bugs in the POP driver that was distributed with Pine
   3.91.  If you are serious about using POP, you should rebuild Pine with
   the current c-client 3.6 library.

 o Pine does not yet support offline mode, which is what POP was
   designed for, and what most people want when they speak of POP support.
   Using the POP driver for accessing your INBOX, Pine will attempt to
   operate in online mode even with the limitations of POP.  A future
   release of Pine (*not* 3.92, alas) will offer true offline support.

 o Pine 3.90 was replaced by 3.91 shortly after it came out (over a year
   ago) because of some serious addressbook bugs.  You should encourage
   your site to upgrade.

 o The UW imap server is easy to install and coexists with pop daemons
   (especially, but not necessarily, if you use the pop daemon that comes
   with our IMAP distribution.)

-teg

---

From: [email-masked] (Ashok Aiyar)
Date: 21 Jan 1996 02:04:37 GMT

>	[Can't open mailbox {mail.bnbcomp.net/pop}jewels: invalid remote 

I do not recall if 3.90 could be used to access a pop3 mailbox.  I do not
know that 3.91 can (albeit this is not supported by Pine developers).

In either event, the syntax above is incorrect.  You may wish to
try "incoming-folders=jewels{mail.bnbcomp.net/pop3}"

Later,
Ashok
--
Ashok Aiyar
http://biocserver.bioc.cwru.edu/pp/aiyar/aiyar.html
--
Change is the essential process of all existence.
		-- Spock, "Let That Be Your Last Battlefield", stardate 5730.2

---

From: Jean Pierre LeJacq <[email-masked]>
Date: Fri, 26 Jan 1996 12:10:36 -0500 (EST)

I've recently installed inn-1.4sec for my news server and have pine
working with mostly.  However, when I post messages, my site-name is
listed twice and my user-id is listed instead of not-for-mail.  For
example:

    Path: quoininc.com!quoininc.com!jplejacq

"inews -h" works correctly and produces:

    Path: quoininc.com!not-for-mail

My system is:

    pine-3.91
    inn-1.4sec
    gcc-2.6.3
    linux-1.2.11

Any ideas on how to correct this? TIA

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jean Pierre LeJacq                                           Quoin Inc

Suite 200 North                   Voice (local):       +1.207.858.0338
124 Mount Auburn Street                   Voice:       +1.617.576.5885
Cambridge, MA 02138-5700                    Fax:       +1.617.576.5876
U.S.A.                                 Internet: [email-masked]

---

From: Mike Brudenell <[email-masked]>
Date: Mon, 29 Jan 1996 09:09:48 +0000 (GMT)

I suspect this indicates a problem with your INN software configuration 
rather than a problem with Pine....

Hostname appearing twice
------------------------
This is covered in the INN FAQ, Part 3.  See "How come my host name comes 
out twice in the path line?" in the "INN is running, but I have this 
small problem..." section.

Not-for-mail
------------
This _might_ be related to the above.  It would be worth checking the 
config.data you used to build INN and make sure that you used:
	PATHMASTER          not-for-mail
Otherwise try asking in the "news.software.nntp" newsgroup.

Cheers,

Mike Brudenell                                         <[email-masked]>
------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/

---

From: Jean Pierre LeJacq <[email-masked]>
Date: Mon, 29 Jan 1996 10:54:44 -0500 (EST)

I recently saw an article that briefly mentioned that there is an RFC
that specifies signatures in email/news messages.  Can anyone point
out which RFC mentions this subject and summarize the major points?

Thanks,

---

From: Jean Pierre LeJacq <[email-masked]>
Date: Mon, 29 Jan 1996 11:32:22 -0500 (EST)

Thanks for your help and suggestions.

I did see the "hostname appearing twice" item in the FAQ and
configured INN to handle it.  Same for the "not-for-mail".  That is
why the "inews -h" command seems to work.

Since my posting, I've modified the inn.conf file to:

  server:           news.quoininc.com
  pathhost:         news.quoininc.com

which produces with pine:

  Path: news.quoininc.com!quoininc.com!jplejacq
  NNTP-Posting-Host: quoininc.com

and with "inews -h":

  Path: news.quoininc.com!not-for-mail
  NNTP-Posting-Host: quoininc.com

I still believe that pine is overriding the inn settings.  The path it
generates may actually be ok.  Any further ideas?

---

From: Terry Gray <[email-masked]>
Date: Mon, 29 Jan 1996 09:25:07 -0800 (PST)

> generates may actually be ok.  Any further ideas?

Pine posts the message to the NNTP server, and has no access to it
thereafter.  There is no way Pine can over-ride anything INN does.

-teg

---

From: Jean Pierre LeJacq <[email-masked]>
Date: Mon, 29 Jan 1996 22:29:12 -0500 (EST)

> thereafter.  There is no way Pine can over-ride anything INN does.

But it seems that pine sets the Path: header before passing the
message to INN.  INN then adds to this header.

It doesn't seem appropriate for an MUA to do this.  Can this behavior
be disabled?

Thanks for the help,

Jean Pierre