WinPMail 2.0 Extensions

This directory contains several sample extensions you can use with WinPMail
version 2.0 and later. All the samples are provided both as executables and 
with complete source code. Each extension's DLL and source code are located 
in a matched subdirectory of this directory. This directory also contains 
the header file necessary when writing extensions, and a document called 
WPMFORMS.TXT which describes the development process. The following sample
extensions are provided:

   FINGER   - Implements the unix "finger" protocol for user lookup
   PH       - Implements the Internet "PH" (or QI) address lookup protocol
   TPHONE   - A simple telephone message form
   MAILMRGE - A mail merge facility for boilerplating mass mailings
   LOG      - A simple extension showing how logging events work.


Using the sample binary extensions

Assuming you have used a default installation of WinPMail (namely you 
have unpacked WINPMAIL.ZIP using the -d flag to PKUNZIP), the extensions 
which ship with WinPMail v2.0 can be used simply by issuing the command:

     COPY *.FFF ..

This will copy the form definition files into the WinPMail base directory 
where they will be found the next time you run WinPMail. The definition 
files have been designed to be as general as possible and the only 
modifications they require are optional default strings (see each file for 
information about what can be defaulted).

Extensions are accessed in WinPMail by selecting "Extensions" from the file 
menu. This will open the Extensions Manager with a list of the extensions 
found at startup.


Compiling the sample extensions

The extensions supplied with WinPMail 2.0 were written using Borland C++ 
v3.1, although they can be compiled using later versions as well simply by 
loading the .PRJ project file. They should compile without warnings or 
errors provided you adjust the location of the file BWCC.LIB which appears 
in the project list (the easiest way to adjust the location is to remove 
the entry from the project and re-add it). They are reasonably well-
commented and should serve as a practical basis for your own extensions.

