Subject: PINE for WINDOWS

From: [email-masked]
Date: 02 Mar 93 16:24:55 UT

Is there  a PINE Version for Windows3.1 available ?
In which Directory can i find this Vers. ?

Which Files must i copy to my PC?

H.U.Heeb
eMail [email-masked]

---

From: Steve Hole <[email-masked]>
Date: Tue, 2 Mar 1993 12:09:23 -0700

On Tue, 2 Mar 1993 09:24:55 -0700 [email-masked] wrote:

> From:[email-masked]> Date: Tue, 2 Mar 1993 09:24:55 -0700
> Subject: PINE for WINDOWS
> To: [email-masked]
> 
> 

There is a Windows MUA that is based (somewhat loosely now) on Pine.   It is
called ECSMail and I have included a short description of its features in this 
message.   

--
Steve Hole  		        Director of Research and Communications
ISA Corporation			mail:  [email-masked]
Suite 835, 10040 - 104 St.      phone: (403) 420-8081
Edmonton, Alberta, Canada       fax:   (403) 420-8037
T5J 0Z2

ISA has developed a new Mail User Agent (MUA) for processing electronic
mail on networks.  It is named "ECSMail".

ECSMail can function as both a "remote" MUA and a "local" MUA.   While
functioning in remote mode, it will access a remote message store using
standards based mail access protocols.   In local mode, it will access
a local message store using system dependent message store access
routines.  

ECSMail is has been designed and implemented to be as independent as
possible from operating system, display, and network protocols.  We have
achieved this by building driver libraries for the OS and displays, and
using Mark Crispin's c-client drivers for message store access (both
local and remote message stores).

Using this strategy, we are planning to support the following operating
systems, display, and mail protocol combinations:

 OS        - Unix, DOS, OS/2 v2, MacOS, NT
 Displays  - X11 (R4, R5, Openlook, Motif), MS Windows v3, Presentation
             Manager, Mac Finder
 MAP Protocols - IMAP2, P7, PP7
 MTP Protocols - SMTP, P1

It is our full intention to make this run on as many platforms, with as
many different mail application protocols as possible.  

With ECSMail we plan to provide many interesting features, such as:

  * Multi-part, multimedia mail messages:

    - supporting both MIME and X.400 message formats

    - files (e.g. binaries, images, text, voice, application) can be
      attached and sent along with the message.

    - the different parts of the messsage can be extracted
      and displayed (using the necessary application) to the user.

  * Multiple simultaneous folder access and management (drag and drop
    messages or blocks of messages between folders).

  * Hierarchical folder structures.

  * Virtual folders within folders.   Messages can be grouped using any
    combination of message header criteria into a virtual folder.
    Messages in a virtual folder can be listed and manipulated as
    a single object.   This supports threading of messages within
    folders. 

  * Integration of multicast (mail) and broadcast (NEWS, BBS) message
    stores via into a single interface.  NEWS groups appear as a list of
    folders and threading of broadcast messages will be supported.

  * Privancy Enhanced Mail (PEM).   Support encryption of message parts,
    digital signatures, and digital timestamps.

  * Forms mail.  Messages can be composed inside of a forms interface
    as a special message part.   It will include form design and
    display tools.

  * Draft message support.   Users will be able to create and store
    standard draft messages, and select draft messages from both public
    and private draft message stores.

  * Integration with "mail enabled applications".  

  * Personal configuration files.

  * Asynchronous new mail notification.

  * Personal address book lookup and management. Addresses can be loaded
    manually, copied from incoming mail, or copied from an X.500 DUA
    (see next).

  * Integration with X.500 Directory Services.  The user can query local
    and network-wide address information while composing messages.
    Addresses can be copied from the Directory User Agent to the user's
    local address book. This facility will be optionally available for
    those who have the X.500 Directory Service capability.

What Is Available Now
---------------------

A BETA demonstration version of the Microsoft Windows version of ECSMail is
available via anonymous ftp from

  ftp.srv.ualberta.ca

in the directory

  /pub/networking/win/mail/ecs.tar.Z

This version of ECSMail only supports the TCP/IP based mail access and
transport protocols (IMAP2, SMTP), and can deliver MIME format messages.
It provides what we term "basic functionality" - it does the things that
most mailers do.   Features such as the virtual folders, and NEWS
message sources have not been implemented at this time.

We encourage you to get the software and try it out.  This version of
ecs is released for demonstration purposes only - IT IS NOT CURRENTLY IN
THE PUBLIC DOMAIN.  As I have mentioned earlier, we are not currently
charging for the product, and are in the process of evaluating different
forms of funding for the software.

There are some restrictions on what you can do with the software at this
time.   The mailer is designed to support several different TCP/IP
stacks through the use of Windows DLLs.   Currently we support the
following TCP/IP stacks:

  * Beame and Whiteside - BWTCP 2.x
  * Sun Microsystems - PCNFS 4.x
  * DEC Pathworks v

We are currently working on providing:

  * Microsoft WinSock DLL compliance
  * FTP Software - PCTCP 2.04

If you are interested in supporting another TCP/IP stack, then provide
us with a copy of the stack and development kit - it must have a sockets
API - and we'll try to provide a DLL interface for it.  

How will we fund ECSMail?
-------------------------

There are two funding methods for ECSMail - maintenance contracts and
development contracts.

Maintenance contracts are signed with organizations that want support
and software maintenance on the ECSMail software.   This will include
free software upgrades and immediate response to software problems.

The cost of the maintenance is designed to be far less than
purchase->upgrade cost of conventional shrinkwrapped software.  The cost
is based on the number of installations that are in place.  The
organization will never be charged more than an agreed upon maximum.  As
the number of installations increases, the per seat cost decreases such
that maximum is never exceeded.  An organization can install as many
copies of ECSMail as they like.

Development contracts are signed to produce new functionality in the
ECSMail product.   ISA has identified a number of potential
functionality improvements that it would like to make to ECSMail.
We also believe that clients will have a number of features that they
would like to see added to the product.

The cost of the contract is determined by the amount of work required to
complete the development, and the number of organizations contributing
to the development.   The more organizations that contribute, the lower
the cost.   ISA publishes a detailed list of feature development
projects that it plans to run in the ecs-info mailing list (see below).  

Mailing lists
-------------

There is an ecs mailing list.   To join the mailing list send a message
to

  [email-masked]

To submit messages to the mailing list, send mail to

  [email-masked]

If there are problems with the list, then send mail to

  [email-masked]