Subject: Pine for OS/2 uploaded to hobbes

From: David Nugent <[email-masked]>
Date: Sun, 14 Jan 1996 21:47:50 GMT

The long-awaited OS/2 port of the Pine mail/news reader version 3.91 has 
been uploaded to hobbes.nmsu.edu in /incoming as pine391.zip.

-- README.OS2 --

This is a port of the Pine 3.91 mail user agent to OS/2 32-bit
compiled with the emx 0.09b development system, gcc 2.7.2. This
includes only the mail UA client and the pico editor, no imapd.

Notes on the OS/2 version of Pine:

 . This is a text mode only version of Pine.

 . Like the PC & Windows versions, this version of Pine is intended
   to be run primarily as a network client.

 . The following client mailstream drivers are supported by Pine-OS2:

     imap,nntp,pop3,bezrk,tenex,dawz,dummy

   This is the same as PC-Pine, with the addition of pop3.
   To enable pop3 over a network link, use the folder
   specification:

     {site.domain/pop3}INBOX

   The pop3 driver has not been extensively tested, however.

 . The "alternate editor" command is active in this version via
   the ^_ key.

 . The spell checker is enabled, by default calling gnu ispell.
   Internal spell checking facilities are disabled in Pine, so
   the spell checker itself must provide the interface (as is
   the case with ispell). The "SPELL" environment variable
   can specify an alternative spell checking program.

 . All help is included within the executable itself.

 . The mouse is enabled and working under OS/2 to the same
   extent as that available under Windows/MSDOS; ie. it works
   for some functions but does not include anything very advanced.

 . Unlike the PC versions of Pine, the addressbook functions work.

 . Attempts have been made to ensure that all files produced and
   used by Pine conform to 8.3 mapping of the FAT filesystem. It
   has not, however, been tested on FAT. Needless to say, the HPFS
   filesystem is fully supported.

 . The pipe command '|' is enabled and functional. Avoid piping
   mail to any interactive command, however - it will not work.

 . Printing has not been tested. For expedience, the UNIX model of
   piping output to a command has been used. You may like to use
   the OS/2 port of the BSD lpr command or similar, or pipe to any
   other command according to preference.

 . Pine-OS2 maps itself to the current display mode, adapting to
   the current screen size to suit.

 . Pine-OS2 provides 16 foreground colours and 8 background colors
   to select from (rather than 8 and 8 with PC-Pine).

 . This version of pine is fully UNIX shell aware, and uses the
   SHELL environment variable in preference to COMSPEC when spawning
   other process. This was tested with the csh and ksh ports.

 . Debugging is not enabled.

INSTALLATION

Requirements: OS/2 2.x with TCPIP 2.0 or later installed (IBM's IAK is
fine). emx.dll version 0.09b or later placed somewhere in the LIBPATH.

Set the HOME environment variable in your CONFIG.SYS to a directory you wish
to use for a work area. Reboot. Move Pine.exe (and optionally Pico.exe) to
any directory in the system PATH. Set the TMP and/or TEMP directory to point
to a directory to be used for temporary files. NOTE: This directory must
exist prior running pine or bad things may result. You may use the PINERC
environment variable to point to an alternative configuration file if
necessary.

Run Pine. Follow the directions presented, and before doing anything else
you should select S)etup C)onfigure and run through all configuration items
and preferences. You may have to exit and restart to access folders.

Read the documentation for further information. Note the syntax of setting
up network folders, folder collections and so on:

  Network folder:  {site.domain}path
  News collection: News *{site.domain}[]

If you specify 'INBOX' as path, this is magic for the inbound mailbox on the
specified server. Note that over a 14.4K link I've had more luck with using
imap to read news than nntp from a performance point of view. NNTP seems
very slow - imap works better. To set this up:

  NNTP-Server: site.domain
  News Collection: News *{site.domain/imap}[]

imapd needs to be running on the news server, and you need to have an
account on that machine, of course, otherwise nntp must be used.
Irrespective of which method you use to read mail, nntp is still used for
posting, hence the requirement for the nntp server name.

Enjoy!

Port by David Nugent ([email-masked])

         David Nugent, [email-masked], 3:632/348@fidonet
               Unique Computing Pty Ltd, Melbourne, Australia
                   +61-3-9791-9547 Bbs/Fax +61-3-9792-3507

---

From: [email-masked] (Christian Chen)
Date: 15 Jan 1996 15:08:31 GMT

David Nugent ([email-masked]) wrote:
: The long-awaited OS/2 port of the Pine mail/news reader version 3.91 has 
: been uploaded to hobbes.nmsu.edu in /incoming as pine391.zip.

It's been moved to the /new directory already, and probably will be
moved to the os2/network/tcpip directory soon.

Thank you very very much for doing this port! It runs faster than
the windows version, too!

Christian Chen 

: -- README.OS2 --

: This is a port of the Pine 3.91 mail user agent to OS/2 32-bit
: compiled with the emx 0.09b development system, gcc 2.7.2. This
: includes only the mail UA client and the pico editor, no imapd.

: Notes on the OS/2 version of Pine:

:  . This is a text mode only version of Pine.

:  . Like the PC & Windows versions, this version of Pine is intended
:    to be run primarily as a network client.

:  . The following client mailstream drivers are supported by Pine-OS2:

:      imap,nntp,pop3,bezrk,tenex,dawz,dummy

:    This is the same as PC-Pine, with the addition of pop3.
:    To enable pop3 over a network link, use the folder
:    specification:

:      {site.domain/pop3}INBOX

:    The pop3 driver has not been extensively tested, however.

:  . The "alternate editor" command is active in this version via
:    the ^_ key.

:  . The spell checker is enabled, by default calling gnu ispell.
:    Internal spell checking facilities are disabled in Pine, so
:    the spell checker itself must provide the interface (as is
:    the case with ispell). The "SPELL" environment variable
:    can specify an alternative spell checking program.

:  . All help is included within the executable itself.

:  . The mouse is enabled and working under OS/2 to the same
:    extent as that available under Windows/MSDOS; ie. it works
:    for some functions but does not include anything very advanced.

:  . Unlike the PC versions of Pine, the addressbook functions work.

:  . Attempts have been made to ensure that all files produced and
:    used by Pine conform to 8.3 mapping of the FAT filesystem. It
:    has not, however, been tested on FAT. Needless to say, the HPFS
:    filesystem is fully supported.

:  . The pipe command '|' is enabled and functional. Avoid piping
:    mail to any interactive command, however - it will not work.

:  . Printing has not been tested. For expedience, the UNIX model of
:    piping output to a command has been used. You may like to use
:    the OS/2 port of the BSD lpr command or similar, or pipe to any
:    other command according to preference.

:  . Pine-OS2 maps itself to the current display mode, adapting to
:    the current screen size to suit.

:  . Pine-OS2 provides 16 foreground colours and 8 background colors
:    to select from (rather than 8 and 8 with PC-Pine).

:  . This version of pine is fully UNIX shell aware, and uses the
:    SHELL environment variable in preference to COMSPEC when spawning
:    other process. This was tested with the csh and ksh ports.

:  . Debugging is not enabled.

: INSTALLATION

: Requirements: OS/2 2.x with TCPIP 2.0 or later installed (IBM's IAK is
: fine). emx.dll version 0.09b or later placed somewhere in the LIBPATH.

: Set the HOME environment variable in your CONFIG.SYS to a directory you wish
: to use for a work area. Reboot. Move Pine.exe (and optionally Pico.exe) to
: any directory in the system PATH. Set the TMP and/or TEMP directory to point
: to a directory to be used for temporary files. NOTE: This directory must
: exist prior running pine or bad things may result. You may use the PINERC
: environment variable to point to an alternative configuration file if
: necessary.

: Run Pine. Follow the directions presented, and before doing anything else
: you should select S)etup C)onfigure and run through all configuration items
: and preferences. You may have to exit and restart to access folders.

: Read the documentation for further information. Note the syntax of setting
: up network folders, folder collections and so on:

:   Network folder:  {site.domain}path
:   News collection: News *{site.domain}[]

: If you specify 'INBOX' as path, this is magic for the inbound mailbox on the
: specified server. Note that over a 14.4K link I've had more luck with using
: imap to read news than nntp from a performance point of view. NNTP seems
: very slow - imap works better. To set this up:

:   NNTP-Server: site.domain
:   News Collection: News *{site.domain/imap}[]

: imapd needs to be running on the news server, and you need to have an
: account on that machine, of course, otherwise nntp must be used.
: Irrespective of which method you use to read mail, nntp is still used for
: posting, hence the requirement for the nntp server name.

: Enjoy!

: Port by David Nugent ([email-masked])

:          David Nugent, [email-masked], 3:632/348@fidonet
:                Unique Computing Pty Ltd, Melbourne, Australia
:                    +61-3-9791-9547 Bbs/Fax +61-3-9792-3507

---

From: Brent Blumenstein <[email-masked]>
Date: Mon, 15 Jan 1996 10:34:28 -0800 (PST)

I would like to extend my thanks to David Nugent for doing this port.

--
Brent A. Blumenstein                   | tel.:   206 667 4623
Fred Hutchinson Cancer Research Center | fax:    206 667 4408
1124 Columbia Street  MP-557           | e-mail: [email-masked]
Seattle, WA 98104    USA               |

---

From: [email-masked] (Ralph Goers)
Date: 16 Jan 1996 00:16:31 GMT

In message <[email-masked]> - [email-masked] (Christian C
hen) writes:
:>
:>David Nugent ([email-masked]) wrote:
:>: The long-awaited OS/2 port of the Pine mail/news reader version 3.91 has 
:>: been uploaded to hobbes.nmsu.edu in /incoming as pine391.zip.
:>
:>It's been moved to the /new directory already, and probably will be
:>moved to the os2/network/tcpip directory soon.
:>
:>Thank you very very much for doing this port! It runs faster than
:>the windows version, too!
:>
:>Christian Chen 

The only problem is, its buggy (and like all other versions of Pine, as far 
as I can tell, somewhat frustrating).

It took me quite a while to determine that in order to access your inbox 
using IMAP you must specify it as {imap.host/imap}inbox.  The doc implies 
that /imap is not needed. 

I also tried setting my sentmail folder to {imap.host/imap}sentmail.  This 
doesn't work so I can't access any folders which are managed by IMAP. 
However, you can do {imap.host}sentmail, which creates a sentmail file in 
your home directory, but that is not how an IMAP client is suppossed to 
create remote folders. 

The worst bug seems to be that when I only have 1 new message in the inbox I 
can see that I have one message but I cannot access it.  When a second 
message arrives I can then see both.

When I deleted messages, if I did not "expunge" them then the messages sit in 
the inbox marked deleted. If I exit Pine and then restart it the messages 
still show as in the inbox, but without header information and are not 
accessable.  Worse, they can't be expunged by Pine (although Simeon was able 
to delete them).

The annoyances:  Esc should take you back one level.  It's not a PM app.  
Although a mouse "pointer" shows up, it apparently doesn't do anything.

Pine is MUCH faster than Simeon, but since I can't access my remote folders 
(other than the inbox) and it can't read my inbox with only one message in it 
(a frequent occurance - I move them to other folders), I'm pretty much stuck.

Ralph

---

From: Bob Wroblewski <bwrob@bwrob>
Date: Mon, 15 Jan 1996 20:49:43 +0000

Yes Thank You very much for this port.
bob

---

From: [email-masked] (Dale Pontius)
Date: 16 Jan 1996 08:47:38 -0500

> been uploaded to hobbes.nmsu.edu in /incoming as pine391.zip.
deletia
>      imap,nntp,pop3,bezrk,tenex,dawz,dummy
I don't see smtp here. Is that so basic it's a no-brainer, or is it
missing. My provider has pop3 to deliver mail to me, but I use smtp
to send it.

Thanks,
Dale Pontius
(NOT speaking for IBM)

---

From: mkeintz@
Date: 17 Jan 1996 14:46:37 GMT

>been uploaded to hobbes.nmsu.edu in /incoming as pine391.zip.

I installed PINE for OS/2 on my Warp/connect machine.  BUT ... it sucks up all 
available cycles, even when doing no more that waiting for keyboard input.  
This is indicated both by very balky behavior (i.e. bringing another window to 
the foreground may take 30 seconds to a minute), and buy the Pulse cpu 
monitor that comes with Warp.

What can I do about this?

thanks,
mark

Mark Keintz
[email-masked]

---

From: Mark Crispin <[email-masked]>
Date: Tue, 16 Jan 1996 15:10:57 -0800

> missing. My provider has pop3 to deliver mail to me, but I use smtp

It's so basic that it's a no-brainer.

A "mailstream driver" in the sense of Pine's internals refers to reading
email.  Posting is a different issue.  NNTP is listed because it's used
for both reading and posting.

Pine as distributed by UW has both SMTP and NNTP posting code.  It would
be work to remove it.

-- Mark --

DoD #0105, R90/6 pilot, FAX: (206) 685-4045  ICBM: N 47 39'35" W 122 18'39"
Science does not emerge from voting, party politics, or public debate.

---

From: [email-masked] (Christian Chen)
Date: 18 Jan 1996 09:26:43 GMT

Dale Pontius ([email-masked]) wrote:

: I don't see smtp here. Is that so basic it's a no-brainer, or is it
: missing. My provider has pop3 to deliver mail to me, but I use smtp
: to send it.

It supports smtp, in fact asks you for the smtp server.

Christian Chen

: Thanks,
: Dale Pontius
: (NOT speaking for IBM)

---

From: [email-masked] (Christian Chen)
Date: 18 Jan 1996 09:30:35 GMT

Ralph Goers ([email-masked]) wrote:
: It took me quite a while to determine that in order to access your inbox 
: using IMAP you must specify it as {imap.host/imap}inbox.  The doc implies 
: that /imap is not needed. 

Most of the problems you have are problems configuring it correctly, not
problems with PINE per se. I use:

{imap.host.domain.}INBOX

and it works just fine.

: I also tried setting my sentmail folder to {imap.host/imap}sentmail.  This 
: doesn't work so I can't access any folders which are managed by IMAP. 
: However, you can do {imap.host}sentmail, which creates a sentmail file in 
: your home directory, but that is not how an IMAP client is suppossed to 
: create remote folders. 

I use

{imap.host.domain.}mail/sent-mail

To access the folder collections I have on the server, i use

{imap.host.domain}mail/[]

Of course, I already had been using pine via a telnet account, so
perhaps things were set up a little easier for me. But I don't see why
you should have any problems reading your folders or having your
sent-mail configured correctly. It's just a matter of discovering the
correct syntax.

The other problems are wierd. Haven't experienced them, but also haven't
been in a position to experience them.

Christian Chen

: The worst bug seems to be that when I only have 1 new message in the inbox I 
: can see that I have one message but I cannot access it.  When a second 
: message arrives I can then see both.

: When I deleted messages, if I did not "expunge" them then the messages sit in 
: the inbox marked deleted. If I exit Pine and then restart it the messages 
: still show as in the inbox, but without header information and are not 
: accessable.  Worse, they can't be expunged by Pine (although Simeon was able 
: to delete them).

: The annoyances:  Esc should take you back one level.  It's not a PM app.  
: Although a mouse "pointer" shows up, it apparently doesn't do anything.

: Pine is MUCH faster than Simeon, but since I can't access my remote folders 
: (other than the inbox) and it can't read my inbox with only one message in it 
: (a frequent occurance - I move them to other folders), I'm pretty much stuck.

: Ralph

---

From: Barry Landy <[email-masked]>
Date: Thu, 18 Jan 1996 09:57:59 +0000

I have just managed to download this (problems with X-atlantic bandwidth 
earlier this week stopped me doing it before). At first glance it seems 
to work beautifully. Only one gripe .. no nice pine icon. (:-))

>                    +61-3-9791-9547 Bbs/Fax +61-3-9792-3507

-------------------------------------------------------------------------------
Barry Landy                        Computer Laboratory:+44 1223 334600
Head of Systems and Development    Direct line:        +44 1223 334713
University of Cambridge Computing Service
New Museums Site                   Email:[email-masked]
Pembroke Street, Cambridge CB2 3QG

---

From: Barry Landy <[email-masked]>
Date: Thu, 18 Jan 1996 12:45:50 +0000

> monitor that comes with Warp.

I just copied the pinerc's I had existing, and am running is on Warp 
(with TCPIP 2.0, not connect) and have no troubls or large CPU consumption.

---

From: [email-masked] (Ralph Goers)
Date: 19 Jan 1996 04:29:49 GMT

In message <[email-masked]> - [email-masked] (Christian C
hen) writes:
:>
:>Ralph Goers ([email-masked]) wrote:
:>: It took me quite a while to determine that in order to access your inbox 
:>: using IMAP you must specify it as {imap.host/imap}inbox.  The doc implies 
:>: that /imap is not needed. 
:>
:>Most of the problems you have are problems configuring it correctly, not
:>problems with PINE per se. I use:
:>
:>{imap.host.domain.}INBOX
:>
:>and it works just fine.

After a couple of email messages with David we both came to the conclusion 
that the problem must be due to the fact that we are using the University of 
Washington IMAP4 server. Apparently, the Pine IMAP server is IMAP2.

Ralph

---

From: "David L. Miller" <[email-masked]>
Date: Fri, 19 Jan 1996 10:48:19 -0800 ()

On 19 Jan 1996, Ralph Goers wrote:

> Errors-To: [email-masked]
> Sender: [email-masked]
> To: [email-masked]
> From: Ralph Goers <[email-masked]>
> Subject: Re: Pine for OS/2 uploaded to hobbes
> Date: 19 Jan 1996 04:29:49 GMT
> Message-ID: <[email-masked]>
> References: <[email-masked]> <[email-masked]>
>

Pine should work equally well with either the IMAP4 server or the
IMAP2bis server distributed with Pine...

---

From: [email-masked] (Vince Vielhaber)
Date: 20 Jan 1996 12:26:09 GMT

In article <[email-masked]>, [email-masked] says...
>to work beautifully. Only one gripe .. no nice pine icon. (:-))

Hmmm.  How 'bout a pine tree growing out of an envelope??

Vince.
-- 
-----------------------------------------------------------------------------
Vince Vielhaber -- KA8CSH     Email: [email-masked]      Flame mail: /dev/null
             Database Manager Michigan Area Repeater Council
                  MSEN.COM is NOT the Microsoft Network!
# include <std/disclaimer.h>                              TEAM OS/2
-----------------------------------------------------------------------------

---

From: [email-masked] (Allan)
Date: Sun, 21 Jan 1996 05:56:48 GMT

I read some concern about an icon for pine... this might be of some
use:

---

From: Mark Crispin <[email-masked]>
Date: Fri, 19 Jan 1996 18:33:59 -0800

Pine is fully compatible with both IMAP2 and IMAP4, or more accurately,
IMAP4 supports IMAP2 compatibility.  If you are having problems, please
send a message to [email-masked] detailing the symptoms.

The /imap switch should never be necessary.  However, I don't know what
the author of the OS/2 port may have done.

-- Mark --

---

From: [email-masked] (Ralph Goers)
Date: 20 Jan 1996 10:02:35 GMT

In message <[email-masked]
n.EDU> - Mark Crispin <[email-masked]> writes:
:>
:>Pine is fully compatible with both IMAP2 and IMAP4, or more accurately,
:>IMAP4 supports IMAP2 compatibility.  If you are having problems, please
:>send a message to [email-masked] detailing the symptoms.
:>
:>The /imap switch should never be necessary.  However, I don't know what
:>the author of the OS/2 port may have done.

After making a few changes based on David's pinerc I find I no longer need 
the /imap.  I have no clue why it now works.  The most important thing I had 
wrong was that folder-collections was set to nothing.  Once I set this to 
point to the directory where my folders are things were much better.  David 
also had a lot more "switches" set.  I pretty much left all that blank.

I printed the Pine Technical Notes.  I think the next step is to read that.

BTW - the online help is useful, but not altogether clear.

Ralph

---

From: [email-masked] (Jon Hacker)
Date: Mon, 29 Jan 1996 16:53:03 GMT

>> monitor that comes with Warp.

You need the later pine391a.zip version that fixes the
CPU hogging.

Jon Hacker