This is Pine for OS/2, a text mode IMAP-capable mail and news client for 32-bit OS/2, including OS/2 version 2.0 and later.
You can download the current PineOS2 via the following URL:
This version of Pine is a network client, and requires you to have IBM TCP/IP 2.0 or later installed. The OS/2 Warp IAK is sufficient to run this program across either a SLIP or PPP link.
Note on mailboxes: The default mailbox type uses the IMAP v2bis protocol. To use IMAP, you will need to be connecting to a mail server with an IMAP server that supports IMAP version 2 or later. Pine may also be used with POP v2 or v3 servers, but is not as functional by a large margin.
To define an IMAP mailbox, you enter the following:
FDQN means "fully qualified domain name", meaning the full hostname of your provider, including the domain portion
To define a POP3 style mailbox, you enter:
Note that POP only supports one mailbox on your server - that is the standard mailbox for incoming mail. With IMAP, you can access other folders on that mailbox, and mailboxes on other servers as well, all in the same session. If you have IMAP available, you can also use your provider's system for storage of folders, and definition of multiple incoming folders (enable the configuration option if you wish to do this), and use procmail or some other mail filtering system on your provider's machine to automatically move incoming mail into the correct folder.
This version of Pine uses smtp delivery only, and is not suitable for an OS/2 system set up as a mail server. That would require a great many changes to the c-client system (for OS/2, at least). Before you can send mail you MUST have a valid smtp-server entry in your PINERC. Use S)etup C)config to enter or modify your current smtp server. When running Pine for the first time on your machine, it will request these sorts of details, but many people do not enter them correctly and may have to correct these before pine will become functional.
Local mail folders created and maintained by PineOS2 are in "dawz" format, which is identical to the format used by the MSDOS and Windows builds of Pine (this is NOT the same format that most UNIX systems use, and you should not attempt to edit or modify these files in any way except via Pine). This version of Pine is also able to read "Berkeley" style mail folders, but only in read-only mode. Since you can copy between folders using the S)ave command from the mail folder index, you can move mail freely from Berkeley format mail folders to dawz, but not the reverse.
If you wish to log in automatically to your server without having to specify a login name or password each time, create an empty file called "PINE.PWD" in the same directory where Pine creates its PINERC configuration file. Something similar to the following will do that:
Before running Pine, set either the HOME environment variable or the PINEHOME variable (if you have other software that uses HOME but wish to place Pine elsewhere) in your CONFIG.SYS - and remember to reboot.
Files in the "bin" subdirectory should be placed somewhere in your PATH. Files in the "dll" subdirectory should be placed in a directory that is specified in your LIBPATH setting in CONFIG.SYS. Files under the "emx" subdirectory should also be placed into a directory in your LIBPATH, but check first to ensure that there are no other files of the same name on your system. These files come from the EMX runtime version 0.9b, and you will need these or the equivalent later versions to run Pine without problems.
For the convenience of WPS users, this version of Pine
includes a -w
When you run INSTPINE.CMD, you must be in the same directory as pine.exe.
Example scripts are provided as a sample of how you might configure Pine to automatically sign messages with PGP, and verify signatures on incoming messages so signed. You need to have PGP installed correctly with a valid secret and/or public keyring on your system before these scripts will be of any use.
The "misc" subdirectory contains a program called "addff" which may be configured as a filter via the Custom Printer to add a formfeed after all output is done (Pine's internal "formfeed" setting only adds a formfeed BETWEEN messages, but does not add one at the end). Read the comments in the .c source file for program use.
Please read the documentation carefully before email the porter for technical support, and do so only as a last resort. Due to many other committements, at this time I am not able to guarantee prompt response to email. Bug reports, on the other hand, are always welcome and I will definitely read and test these before the next Pine release.
OS/2 Port: David Nugent
Email: davidn@blaze.net.au
FidoNet: 3:632/348@fidonet
Note that Pine 3.95 may well be the last of the 3.xx releases of Pine. The development team at UW are working hard on version 4.x, which will support IMAP version 4.x extensions.
The port to OS/2 has been incorprated into the standard Pine source distribution, which can be found at
Before building PineOS2, you will need:
All can be obtained from the OS/2 archives at hobbes.nmsu.edu.
You will also need to convert the files build.cmd in the Pine source root directory and imap\ANSI\c-client\drivers.cmd from "UNIX" newline delimited files to standard DOS CRLF files so that IBM REXX will be able to read them correctly. You need not convert any other files, which will be accepted as is by gcc.
Other than that, just type 'build' in the top level directory and that should build Pine for OS2 with no further action necessary. "pineicon.cmd" has been provided in the misc\ directory of this distribution to add the pine.ico icon resource to the pine executable using the RC resource compiler that is included with OS/2 2.1 and Warp (and the various superset distributions of OS/2).