1 Introduction

1.1 Features
1.2 Documentation Set
1.3 Example Program
1.4 Installation
1.5 Uninstalling
1.6 Pricing
1.7 Updates

2 Library Overview

2.1 Dynamic Link Libraries
2.2 Keycode
2.3 Win32 STDCALL and DECLSPEC
2.4 Using Threads
2.5 Error Display
2.6 Adding SEE to a PowerBASIC Program
2.7 PowerBASIC Declaration Files
2.8 Editing EMAIL.INC
2.9 Include Files

3 Compiler Issues

3.1 PowerBASIC Console Compiler
3.2 PowerBASIC DLL Compiler
3.3 PowerBASIC Windows Compiler
3.4 Compiling Example Programs

4 Example Programs

4.1 Connectionless Example Programs
4.2 SMTP Example Programs
4.3 POP3 Example Programs

5 Revision History

1 Introduction

The SMTP/POP3 Email Engine for PowerBASIC (SEE4PB) library is a powerful toolkit that allows software developers to quickly develop SMTP and POP3 email applications in PowerBASIC (PB/CC, PB/DLL, and PB/WIN). SEE is implemented as a component library of functions providing direct and simple control of the SMTP (Simple Mail Transport Protocol) and POP3 (Post Office 3) protocols.

A simple interface allows sending and receiving email, including multiple MIME base64 and quoted-printable encoded attachments. Knowledge of Winsock and TCP/IP is not needed.

The SMTP/POP3 Email Engine for PowerBASIC component library supports and has been tested with PowerBASIC console compiler (PB/CC) and PowerBASIC for Windows (PB/DLL and PB/WIN). SEE4PB includes numerous example programs that demonstrate SMTP and POP3 functions to help software developers easily build software applications using SEE4PB.

SEE4PB runs under all versions of Windows (Windows 95, Windows 98, Windows ME, Windows 2000, Windows NT and Windows XP). The SMTP/POP3 Email Engine SDK DLL (SEE32.DLL) can also be used from any Win32 language (C/C++, .NET, Visual Basic, VB. NET, VBA, Delphi, Visual FoxPro, COBOL, Xbase++, dBase, etc.) capable of calling the Windows API.

When comparing the SMTP/POP3 Email component library against our competition, note that:

• SEE4PB is a standard Windows DLL and is much smaller than an OCX or ActiveX control.
• SEE4PB does NOT depend on ActiveX or similar "support" libraries.
• SEE4PB (SEE32.DLL) is fully threadable.
• The SEE4PB functions can be called from applications not capable of using controls.

MarshallSoft also has versions of the SMTP/POP3 Email Engine library for Visual Basic (SEE4VB), Delphi (SEE4D), C/C++ (SEE4C), Visual FoxPro (SEE4FP), Visual dBASE (SEE4DB), and Xbase++ (SEE4XB). All versions of SEE use the same DLLs (SEE16.DLL or SEE32.DLL). However, the examples provided for each version are written for the specified computer language.

The latest versions of SMTP/POP3 Email Engine (SEE) can be downloaded from our web site at

http://www.marshallsoft.com/email-component-library.htm

Our goal is to provide a robust SMTP/POP3 email component library that you and your customers can depend upon. A fully functional evaluation version is available. Contact us if you have any questions.

1.1 Features

Some of the many features of the SMTP/POP3 Email Engine component library are as follows:

• SMTP client for sending email.
• POP3 client for receiving email.
• Send email with optional MIME or Quoted Printable attachments.
• Send email with inline embedded HTML, GIF, TIF, JPG, BMP and Rich Text attachments.
• Get the number of messages on the POP3 email server.
• Get the header lines from any email on the POP3 email server, without reading the entire email.
• Delete any email on the POP3 server without reading it first.
• Copy any email on the POP3 server without deleting it.
• Check for the number of emails on the POP3 server.
• Receive any email on the POP3 server including MIME attachments.
• Forward Email.
• Decoding email from a File
• Run up to 128 independent WIN32 threads concurrently.
• Can send email to mail addresses on a distribution list.
• Supports SMTP (ESMTP) and POP3 authentication.
• Set return receipt; add TO, CC, BCC recipients
• Set minimum and maximum wait times for server response.
• Supports ISO-8859 (European character sets) and UTF-8 (16 bit character sets) messages.
• Can specify custom Content-Types; add custom header fields
• Includes over 36 functions for SMTP and POP3 control.
• Dozens of switches provided to control how email is sent or received.
• Supports setting priority via X-Priority header field.
• Can be used from GUI mode or console mode programs.
• Is fully thread safe.
• Implemented as a standard Windows DLL, which will work with all versions of Windows.
• Supports PBCC, PBDLL, and PBWIN compilers.
• Does not depend on support libraries. Makes calls to core Windows API functions only.
• Can be used with any program (in any language) capable of calling Windows API functions.
• Supports Windows 95/98/Me/NT/2000/2003/XP.
• Royalty free distribution with your compiled application.
• Free technical support and downloadable updates for one year.

Registration includes one year of free updates.

1.2 Documentation Set

The complete set of documentation consists of three manuals in three formats. This is the first manual (SEE_4PB) in the set.

• SEE4PB Programmer's Manual (SEE_4PB.DOC, SEE_4PB.TXT, SEE_4PB.HTM)
• SEE User's Manual (SEE_USR.DOC, SEE_USR.TXT, SEE_USR.HTM)
• SEE Reference Manual (SEE_REF.DOC, SEE_REF.TXT, SEE_REF.HTM)

Each manual comes in three formats:

• Microsoft Word (files ending in .DOC). The best format for printing manuals.
• Hyper Text (files ending in .HTM). Use any web browser to read.
• ASCII Text (files ending in .TXT).

The SEE_4PB Programmer's Manual is the language specific (PowerBASIC) manual. All language dependent programming issues such as compiling, compilers and example programs are discussed in this manual. Read this manual first.

The SEE User's Manual (SEE_USR) discusses email processing as well as language independent programming issues such as application notes and licensing. Read this manual second.

The SEE Reference Manual (SEE_REF) contains details on each individual SEE function.

Use Microsoft Word or Microsoft WordPad to print the document files. The online documentation can be accessed on the SMTP/POP3 Email Engine for PowerBASIC product page at:

    http://www.marshallsoft.com/pb-email-component.htm

1.3 Example Program

The following example demonstrates the use of some of the SMTP/POP3 Email for PowerBASIC component library functions:

     Dim Code As Integer
     Dim xServer, xIsNull, xTo, xFrom As Asciiz * 64
     Dim xSubject, xMessage As Asciiz * 64
     xIsNull  = Chr$(0)
     xServer  = "mail.yourisp.com
     xFrom = "my name<me@myisp.biz>"
     xTo   = "<support@marshallsoft.com>"
     xSubject = "PowerBASIC Test"
     xMessage = "Emailed from SEE4PB!"
     Code = seeAttach(1, %SEE_KEY_CODE)
     If Code < 0 Then
       ' error calling seeAttach !
       . . .
     End If
     Code = seeSmtpConnect(0,xServer,xFrom,xIsNull)
     If Code < 0 Then
       ' error calling seeSmtpConnect !
       . . .
     End If
     Code = seeSendEmail(0,xTo,xIsNull,xIsNull,xSubject,xMessage,xIsNull)
     If Code < 0 Then
       ' error calling seeSendEmail !
       . . .
     End If
     Code = seeClose(0)
     Code = seeRelease()

In the example program above, seeAttach is called to initialize SEE and then seeSmtpConnect is called to connect to the SMTP mail host. The SMTP server host name and your email address are required, while the "Reply-To" entry is optional.

seeSendEmail is then called, passing the addressee lists. The primary addressee is provided in the "To List". The CC ("Carbon Copy") lists additional recipients, as does the BCC (Blind Carbon Copy) list. The subject contains the email subject line. The message text is next. If it starts with the '@' symbol, it is considered the name of the file containing the email message. Lastly, the filename of any ASCII or binary attachment is specified. All fields, except the first, in seeSendEmail are optional.

After returning from seeSendEmail, the seeClose function is called to close the connection to the SMTP server. Lastly, seeRelease is called to perform SEE termination processing and release the Winsock.

1.4 Installation

1. Before installation of SEE4PB, your PowerBASIC compiler (PB/CC, PB/DLL, and PB/WIN) should already be installed on your system and tested.
   
   
2. Unzip SEE4PB40.ZIP (or SEExxxx.ZIP where xxxx is your Customer ID) using any Windows unzip program.
   
   
3. Run the installation program SETUP.EXE which will install all SEE4PB files, including copying SEE32.DLL to your Windows directory. No Windows system files are modified.
   
   
4. Edit the INCLUDE file EMAIL.INC (which is included by most of the example programs) with your TCP/IP parameters.
   
   
5. You're ready to compile the example programs. Compile and run SEEVER.BAS first.

Note that the Windows registry is not modified during the installation process.

1.5 Uninstalling

Uninstalling SEE4PB is very easy. SEE does not modify the registry.

First, run UINSTALL.BAT, which will delete SEE32.DLL from your Windows directory, typically C:\WINDOWS for Windows 95/98/Me/XP or C:\WINNT for Windows NT/2000.

Second, delete the SEE project directory created when installing SEE4PB.

1.6 Pricing

A developer license for SEE4PB can be registered for $115. Purchasing details can be found in Section 1.3 "How to Purchase" in the SEE User's Manual (SEE_USR). Also See INVOICE.TXT or

     http://www.marshallsoft.com/order.htm

1.7 Updates

When a developer license is purchased for SEE4PB, you will be sent the registered DLL plus a license file (SEExxxx.LIC) that can be used to update your registered DLL's for a period of one year from purchase. Updates can be downloaded from

     http://www.marshallsoft.com/oem.htm

After one year, your license must be updated if you want to be able to download updates. Your license can be updated for $30 if ordered within one year of the original purchase (or previous update). After one year, licenses can be updated for $55.

Note that registered DLLs never expire.

Also see file UPDATES.TXT.

2 Library Overview

The Windows Standard Serial Communications Library (WSC) has been tested on multiple computers running Windows 95/98/Me/XP, and Windows NT/2000.

2.1 Dynamic Link Libraries

The SEE4PB SMTP/POP3 Email library component (SEE32.DLL) is implemented as a Win32 dynamic link libraries (DLL). A DLL is characterized by the fact that it need not be loaded until required by an application program and that only one copy of the DLL is necessary regardless of the number of application programs that use it. Contrast this to the traditional static library that is bound to each and every application that uses it at link time.

An important advantage that DLLs have over other "popular" library formats such as VBX or OCX is that DLLs are callable by all Windows applications. Since DLLs are the building blocks of the Windows Operating System, they will not be replaced by a "newer technology".

2.2 Keycode

The SEE32.DLL has a keycode encoded within it. Your keycode is a 9 or 10 digit decimal number (unless it is 0), and will be found in the file KEYCODE.H. The keycode for the evaluation (shareware) version is 0. You will receive a new keycode and a set of new DLL's when registering. The KEYCODE is passed to SeeAttach.

If you get an error message (value -74) when calling seeAttach, it means that the keycode in your application does not match the keycode in the DLL. After registering, it is best to remove the evaluation version of SEE16.DLL from the Windows search path or delete it.

2.3 Win32 STDCALL and DECLSPEC

SEE32 is written in ANSI C and is compiled using the STDCALL and DECLSPEC keywords. This means that SEE4PB uses the same calling conventions and file naming conventions as the Win32 API. . In particular, function names are NOT decorated. There are neither leading underscores nor trailing "@size" strings added to function names.

The SEE32.DLL functions may be called by any Windows application program capable of calling the Windows API provided the proper declaration file is used.

2.4 Using Threads

SEE4PB is thread safe, and can be used from any Windows application capable of using threads. Refer to the TSTAT example program, which demonstrate the use of threads.

The necessary Win32 thread functions are declared in the PowerBASIC INCLUDE file "WIN32API.INC"

2.5 Error Display

The error message text associated with SEE error codes can be displayed by calling seeErrorText. Refer to the SMTP/POP3 Email Reference Manual (SEE_REF.HTM or SEE_REF.DOC).

2.6 Adding SEE to a PowerBASIC Program

In order to add SEE to a PowerBASIC program, add

     $INCLUDE "SEE32.PBI"
     $INCLUDE "KEYCODE.PBI"

after any other $INCLUDE statements. Then add

     Code = SeeAttach(1,%SEE_KEY_CODE)
     If Code < 0 Then
       '... display error code to user here...
       EXIT FUNCTION
     END IF

as the fist executed SEE function.

2.7 PowerBASIC Declaration Files

SEE constants are defined and all SEE functions are declared in the file SEE32.PBI and are included in all of the example programs.

2.8 Editing EMAIL.INC

The file EMAIL.INC is included by most of the example programs and contains the following defines:

     #define YOUR_EMAIL_ADDR     "!your_email_address
     #define SMTP_HOST_NAME      "!smtp_server_name"
     #define SMTP_USER_NAME      "!smtp_account_name"
     #define SMTP_PASSWORD       "!smtp_account_password "
     #define POP3_HOST_NAME      "!pop3_server_name"
     #define POP3_USER_NAME      "!pop3_account_name"
     #define POP3_PASSWORD       "!pop3_account_password ".

This file must be edited with your email configuration before compiling any of the example programs. This information is required for all email clients. If you are unsure of any of these settings, look in your email client program (Outlook, Eudora, Pegasus, etc.).

SMTP_USER_NAME and SMTP_PASSWORD are required only if you will be doing SMTP authentication. They are usually the same as POP3_USER_NAME and POP3_PASSWORD. Refer to the SEE User's Manual (SEE_USR) for more information on authentication.

SMTP_HOST_NAME is the name (or IP address) of your SMTP email server. POP3_HOST_NAME is the name of your POP3 server, which is typically the same as the SMTP server. YOUR_EMAIL_ADDR is your email address. Brackets "<>" are required. POP3_USER_NAME is the account name for your email (POP3) account. POP3_PASSWORD is the password for you email (POP3) account. For example,

     #define YOUR_EMAIL_ADDR   "Mike Marshall<info@marshallsoft.com>"
     #define SMTP_HOST_NAME    "mail.yourisp.net"
     #define SMTP_USER_NAME    "marshallsoft"
     #define SMTP_PASSWORD     "qwerty"
     #define POP3_HOST_NAME    "mail.hiwaay.net"
     #define POP3_USER_NAME    "marshallsoft"
     #define POP3_PASSWORD     "qwerty"
     #define SMTP_USER_NAME    "marshallsoft"
     #define SMTP_PASSWORD     "qwerty"

Note that EMAIL.INC is used only in the example programs. Strings passed to SEE functions can be taken from any source (hard-coded, read from keyboard, read from file, etc.).

Not all of the #defines are used by the example programs. For example, SMTP_USER_NAME and SMTP_PASSWORD are used only by the AUTHEN example program.

2.9 Include Files

There are three include files. The first two are included by all example programs.

• SEE32.PBI -- Contains the function declarations for SEE32.DLL.
• KEYCODE.PBI -- Contains your key code. See the following section.
• GETARGS.PBI -- Read and parses command line arguments.
  
  
  
  

3 Compiler Issues

The SMTP/POP3 Email Engine for PowerBASIC component library supports and has been tested with the PowerBASIC Console Compiler (PBCC), the PowerBASIC DLL Compiler (PBDLL). and PowerBASIC for Windows (PB/WIN).

3.1 PowerBASIC Console Compiler (PBCC)

Most of the example programs are written for the PowerBASIC Console Compiler (PBCC). Be sure to read the comments at the beginning of each example program. Also see section 4.0 "Example Programs" below.

3.2 PowerBASIC DLL Compiler (PBDLL)

SEE functions can be called from programs written for the PowerBASIC DLL Compiler (PBDLL). The same DLL (SEE32.DLL) is used for both PowerBASIC and Visual Basic. SEE functions are defined in SEE32.PBI for PowerBASIC and in SEE32.BAS for Visual Basic. The Visual Basic version can be downloaded from www.marshallsoft.com/see4vb.htm

See the PB_STAT.BAS example program.

3.3 PowerBASIC Windows Compiler (PBWIN)

SEE functions can be called from programs written for the PowerBASIC Windows Compiler (PBWIN). There are no differences in how SEE functions are called in programs written in any of the Windows PowerBASIC compilers.

See the HELLO.BAS example program.

3.4 Compiling Example Programs

Twenty example programs are included. All are compiled at the command line with the PowerBASIC Console Compiler (PBCC), except for PB_STAT what uses the PowerBASIC DLL compiler (PBDLL), and HELLO.BAS what uses the PowerBASIC Windows compiler (PBWIN).

   
     PBCC  AUTHEN.BAS
     PBCC  AUTO.BAS
     PBCC  BCAST.BAS
     PBCC  CODETEST.BAS
     PBCC  DELETE.BAS
     PBCC  FORWARD.BAS
     PBCC  GB2312.BAS
     PBCC  GETRAW.BAS
     PBCC  HTML.BAS
     PBCC  MAILER.BAS
     PBCC  MPARTS.BAS
     PBDLL PB_STAT.BAS
     PBCC  POP3RD.BAS
     PBCC  READER.BAS
     PBCC  SEEVER.BAS
     PBCC  STAT.BAS
     PBCC  STATUS.BAS
     PBCC  TSTAT.BAS
     PBCC  VERUSR.BAS
   

Compiling programs using the PowerBASIC Console Compiler is very easy.  For example, to compile MAILER.BAS, type

     PBCC MAILER.BAS

PBCC programs (such as TSTAT.BAS) that reference WIN32API.INC must specify the WINAPI directory on the command line. For example, if your PowerBASIC Console Compiler is installed at C:\PBCC, you would compile TSTAT with

     PBCC TSTAT.BAS -IC:\PBCC\WINAPI

Compile and run SEEVER as the first example to check your installation. SEEVER does not require a TCP/IP connection. Also see Section 4 "Example Programs" for more information on each of the example programs.

4 Example Programs

Before compiling the example programs, edit the include file EMAIL.INC with your SMTP/POP3 host and email address. Refer to section "Your SMTP/POP3 Host Name" in the SEE User's Manual (SEE_USR) for more information on SMTP/POP3 server names.

All example programs are compiled with PBCC except for PB_STAT.BAS that is compiled with PBDLL and HELLO.BAS that is compiled with PBWIN.

4.1 Connectionless Example Programs

Three example programs do not require a connection to a server.

4.1.1 SEEVER

The SEEVER example program displays the SEE library version number and registration string and verifies that SEE32.DLL is being found and loaded by Windows. Compile with PBCC.

4.1.2 CODETEST

The CODETEST example program demonstrates how to use seeEncodeBuffer and seeDecodeBuffer, which BASE64 encodes and decodes a test string. The CODETEST example program also demonstrates the use of seeEncodeUTF8 and seeDecodeUTF8. Compile with PBCC.

4.1.3 HELLO

The HELLO is the same program as SEEVER except that it is compiled with the PowerBASIC Windows (PBWIN) compiler.

4.2 SMTP Email Example Programs

There are ten SMTP email example programs. SMTP programs send email. Don't forget to edit EMAIL.INC before compiling.

4.2.1 AUTHEN

AUTHEN is an example program that connects to an SMTP server using SMTP Authentication. You must connect to a SMTP server that allows authentication.

AUTHEN takes no command line arguments.

4.2.2 AUTO

AUTO ("auto-responder") uses two channels concurrently to automatically respond to all new email. AUTO will read (but not delete) all email on your server and reply to each that "your email was received".

AUTO (and TSTAT) are the only example programs that use more than one channel concurrently.

4.2.3 BCAST

BCAST (Broadcast) emails the same message to each recipient from a file of email addresses. Along with your SMTP server and your email address, you must create the file containing the email message to send, and create another file containing the list of recipients. See BCAST.EML for an example.

Please DO NOT use this to send spam!

4.2.4 GB2312

The GB2312 example program sends a text message that is GB2312 (simplified Chinese) encoded. The recipient's email client will be able to display the email message using the specified GB2312 character set provided that it is capable of identifying GB2312 MIME parts (such as MS OutLook).

4.2.5 HTML

The HTML example program connects to an SMTP server and emails an HTML file containing inline graphics. The graphics files are attached to the HTML email message.

To email the test file (TEST.HTM with image attachments IMAGE1.GIF and IMAGE2.GIF) to address <you@my-isp.com> , type

     HTML  you@my-isp.com

Note that the HTML example program uses the seeSendHTML function rather than the seeSendEmail function to send the email.

4.2.6 ISO8859

The ISO8859 example program sends a text message and subject line that are ISO-8859 encoded. The recipient's email client will be able to display the email message using the specified ISO character set provided that it is capable of identifying ISO-8859 MIME parts (such as MS OutLook).

4.2.7 MAILER

MAILER emails a message, including optional MIME attachments. All required parameters are input using a dialog box at runtime.

For example, to mail TEST.TXT with attachment TEST.ZIP to info@marshallsoft.com with subject "TEST" (Note that <> brackets are required around the email address.):

     MAILER  "@test.txt"  TEST  "<info@marshallsoft.com>" test.zip

4.2.8 MPARTS

The MPARTS example program sends a multipart MIME email in which the Content-Type headers for each attachment are specified by the programmer.

The two attachment types specified in this example are a sound file (.wav) and of PDF file (.pdf).

4.2.9 VERUSR

VERUSR (Verify User) connects to a specified SMTP server and requests verification of the user.

Due to security concerns, some SMTP servers will not honor a "verify user" request. A user that does not verify does NOT necessarily mean that the email address is not good.

4.2.10 Forward

The FORWARD example program forwards an (undecoded) email to a new recipient. Only undecoded email can be forwarded.

4.3 POP3 Example Programs

There are nine POP3 example programs. These examples read email. Don't forget to edit EMAIL.INC before compiling.

4.3.1 AUTO

AUTO ("auto-responder") uses two channels concurrently to automatically respond to all new email. AUTO will read (but not delete) all email on your server and reply to each that "your email was received".

AUTO (and TSTAT) are the only example programs that use more than one channel concurrently.

4.3.2 DELETE

The DELETE program deletes an email message from the server. Be careful! Once deleted, email messages cannot be recovered.

4.3.3 GETRAW

GETRAW is a program that downloads a specified email message without decoding it. This is used to see what the email looks like on the server. Email can also be downloaded without decoding by the READER example program.

For example, to download message 2 from the POP3 account mail.myisp.biz as user "mike" and password "qwerty", type

     GETRAW  "mail.myisp.biz"  "mike"  "qwerty"  2

4.3.4 PB_STAT

The PB_STAT example program demonstrates how to call DLL's created by the PowerBASIC DLL compiler from Microsoft Visual Basic. PB_STAT.BAS is compiled by

     PBDLL PB_STAT.BAS

You must also compile the Visual Basic program PB_STAT.FRM by loading PB_STAT.VBP in Visual Basic version 4.0 or above.

4.3.5 READER

READER reads an email message from your server, including any MIME attachments. The email message is saved as a file.

For example, to read message 1 to file FILE1.TXT, type

     READER  1  FILE1.TXT

4.3.6 STAT

The STAT program is the simplest POP3 example. It logs onto the POP3 server and gets the number of messages waiting.

STAT takes no command line arguments.

4.3.7 STATUS

STATUS reads the number of email messages waiting on your POP3 server, and displays the "DATE:", "FROM:", and "SUBJECT:" header fields from each email.

STATUS takes no command line arguments.

4.3.8 TSTAT

TSTAT checks several POP3 mailboxes using multiple threads. Edit TSTAT.BAS with the POP3 accounts to check before compiling. Note that since TSTAT references the WINAPI directory, it must appear on the command line. For example (assuming PBCC is installed at C:\PBCC):

     PBCC TSTAT.BAS -IC:\PBCC\WINAPI

TSTAT takes no command line arguments. Be sure to edit TSTAT.BAS before compiling.

4.3.9 POP3RD

The POP3RD example program uses the seePop3Source function to specify an (undecoded) email message file to be decoded.

5 Revision History

The SMTP/POP3 Email Engine DLL (SEE32.DLL) is written in ANSI C. All language versions of SEE (C/C++, Delphi, Visual Basic, PowerBASIC, FoxPro, Delphi, Xbase++, COBOL, and Fortran) use the same identical DLLs.

Version 1.0: June 22, 1998.

• Initial release (for C/C++).

Version 2.0: October 2, 1998.

• Initial PBCC release.

Version 2.1: December 9, 1998.

• Time zone calculated automatically.
• Fixed bug in seeClose.
• Corrected POP3 problem when boundary definition on 2nd line.
• Added support for alternate MIME boundaries.
• Added seeVerifyUser function.
• Added SEE_GET_REGISTRATION and SEE_GET_CONNECT_STATUS.
• Added SEE_GET_ATTACH_COUNT and SEE_GET_LAST_RESPONSE.
• Added GETDOC, SEEVER, and VERUSR example programs.
• SMTP performance improved.
• Added seeEncodeBuffer and seeDecodeBuffer functions.
• Added SEE_FILE_PREFIX and SEE_SET_REPLY parameters.

Version 3.0: April 5, 1999.

• Modified SEE to be fully threadable (adding seeAttach and seeRelease).
• Added seeGetEmailUID function.
• Handles "inline" email text properly.
• Optionally decodes unnamed attachments.
• Added ability to add header lines (SEE_SET_HEADER).
• Can use alternate ports for SMTP or POP3.
• Win16 version can get time zone from TZ environment variable.
• Quoted-printable messages can handle soft line breaks.
• Quoted-printable message can handle embedded HTML text.

Version 3.1: July 21, 1999.

• Support ISO-8859-1 (Q or B) encoded attachment filenames.
• Support ISO-8859-1 (Q only) on subject line
• SEE_SAVED_TO_MSG parameter added.
• "+OK" line not written to email message file.
• Added seeExtractLine function.
• Added RegMe example programs.

Version 3.2: January 24, 2000.

• Added QUOTED_8859 processing (QUOTED_8859).
• Can decode printed quotable attachments!
• seeGetEmailLines can use internal memory.
• Added SEE_WRITE_TO_LOG to seeStringParam.
• Added SEE_GET_ATTACH_NAMES to seeDebug to get attachment filename list.
• Ability to reset the SEE_SET_HEADER header string to "nothing".
• Improvements in dynamic memory usage.
• Added GETRAW and CODETEST examples.
• Added support for Lcc-Win32.
• Added seeCommand function.

Version 3.3: October 30, 2000

• seeGetEmailLines can use internal memory.
• Added SEE_COPY_BUFFER [seeDebug] to copy internal buffer.
• Added SEE_WRITE_TO_LOG [seeStringParam] to allow user to write to LOG file.
• Added SEE_GET_ATTACH_NAMES [seeDebug] to get attachment filename list.
• Ability to reset the SEE_SET_HEADER [seeStringParam] to "nothing".
• Added seeCommand function.
• Allow TIC marks (0x27) in VerifyAddressChars().
• Added SEE_GET_LAST_RECIPIENT to seeDebug.
• Added seconds to date string on outgoing email.
• Attachment name is saved when attachment file is closed.
• Added SEE_PATH_DELIMITER to seeIntegerParam().
• Added seeAbort function.
• VerifyFormat rejects "@domain" and "name@" addresses.
• Added "SEE_SET_FROM" so can change "From:" header at runtime.
• Delimiters (CR/LF) sent with command in one network transmission [seeWriteLine].
• Added QUOTED_USER, SEE_SET_CONTENT_TYPE, and SEE_SET_TRANSFER_ENCODING.
• Added SEE_ATTACH_DELIMITER and ability to specify different attachment filename in email.
• Added SEE_ADD_HEADER to seeStringParam.
• Added SEE_WRITE_BUFFER to seeDebug (see seeGetEmailLines)
• Added SEE_ENABLE_IMAGE to send GIF/TIF/BMP/JPG images inside email.

Version 3.4: August, 2001

• Supports "AUTH LOGIN" and "AUTH CRAM-MD5" (SMTP) authentication.
• SmtpResponse accepts response line without message.
• Supports ISO-8859-1 (base-64) encoding on subject line.
• Supports "APOP" authentication (POP3 servers).

Version 3.5: March 20, 2002

• Added support for "AUTH PLAIN".
• Recognize multiple AUTH methods on one line, such as "AUTH PLAIN LOGIN CRAM-MD5".
• Added SEE_FORCE_INLINE -- attachments are inline text rather than base64 encoded.
• Added SEE_SET_ATTACH_CONTENT_TYPE -- user can specify content type for attachments.
• Added SEE_ATTACH_BASE_NUMBER -- attachments named "1.att", "2.att", etc.
• Don't close socket (seeClose) if socket is already closed.
• NBR_CHANS set to 128 for Win32.
• SEE_RAW_MODE reads complete lines rather than buffers.
• Added seeQuoteBuffer() -- used to prepare ISO-8859 headers.
• Will continue with sending DATA (rather than return error) if have at least one recipient.
• Call seeStatistics(Chan, SEE_GET_LAST_RECIPIENT) to get # recipients accepted by server.
• Added SEE_IGNORE_REJECTED to ignore error returned if recipient is rejected.
• Added PB_STAT and CODETEST example programs.

Version 3.6: April 1, 2003

• Added seeSendHTML() function.
• Looks for multipart/related as well as multipart/alternative message parts.
• Added SEE_HTML_CHARSET (CHARSET_US and CHARSET_8859)
• Generic multipart boundary definitions handled (not just alternate, related, ...)
• CR/LFs preserved in multiline "Subjects:" headers.
• Handle case where "MIME-Version: 1.0" statement does not proceed all other MIME statements
• MAX_BUF increased from 2048 to 8192 for WIN32
• Virtual socket # written to log file when created (vsGetSocket) & released (vsCloseSocket).
• Write to email file if "MIME-Version" was not seen.
• vSock released properly in seeClose.
• Terminating ALT boundary not written if HTML file is passed from memory (not a file)
• Alternate text in seeSendHTML can be file (if prefixed with '@')
• Added seeEncodeUTF8 and seeDecodeUTF8 functions.
• Delimiters separating email addresses and pathnames changed to a semicolon.
• Added ISO_8859, WIN_1252, and WIN_1255 character set types.
  
  
  

Version 3.7: February 4, 2005.

• Terminating ALT boundary not written if HTML file is passed from memory (not a file).
• Alternate text in seeSendHTML can be file (if prefixed with '@')
• Added seeEncodeUTF8 and seeDecodeUTF8 functions
• AddrDelimiter and PathDelimiter changed to ';' (semicolon)
• Added QUOTED_WIN_1252 and QUOTED_WIN_1255.
• User headers written even if no subject
• Corrected problem: User Content-Type wasn't being sent if no quoting
• Added SEE_HIDE_HEADERS -- overrides any conflicting flags
• Fixed problem with "Filename=" extraction.
• Replaced OF_READ|OF_SHARE_DENY_WRITE with OF_SHARE_DENY_WRITE in _lopen
• Filename added to SEE_CANNOT_CREATE & SEE_CANNOT_OPEN error messages.
• Multi-line subject headers supported in seeGetEmailFile.
• ReadMsgLine uses Allow8Bits to decide if it should quote or not
• Added SEE_SET_DEFAULT_ZONE
• Increased buffer size for challenge string in authenticated SMTP connections.
• Added WriteToLog(), WriteClientTempToLog(), and WriteToLastLog() to centralize log writing.
• Nulls are replaced by spaces in all incoming data.
• Added support for "=?US-ASCII?B?" encoded filenames
• Fixed problem quoting line starting with '.' and having non-ASCII characters.
• Fixed SMTP problem when attaching large number of files (seeWriteSocket,seeWriteLine, seeWriteString).
• Added IgnoreErrorStatus (default TRUE) that skips socket error check in STATE_CONNECT
• Fixed problem with Content-Type prefix (set by SEE_WRITE_CONTENT_TYPE).
• Scan subjects & filenames for "big5" encoding like iso-8859
• Only one of TO, CC, and BCC must contain a recipient.
• Maximum text line length default increased to 1000.
• Added SEE_REPLACE_WITH_COMMAS to override replacement of delimiters with commas.
• SEE_FILE_PREFIX parameters set base for attachment file prefixes.
• Added seeAttachmentParams function.
• Added ISO8859, GB2312, and MParts example programs.

Version 4.0: June 27, 2006.

• Always an error if "relay", "gateway", or "not local" is in the text of the server's response, regardless of SEE_IGNORE_REJECTED.
• Forwarded header lines written to message/rfc822 (attachment) file.
• Each POP3 message optionally saved to disk in raw (undecoded) format in seeGetEmailFile.
• Added function seeForwardEmail().
• Added function seePop3Source().
• Maximum internal buffer size increased from 8 KB to 16 KB.
• Alternate boundaries w/o enclosing quotes are supported.
• FORWARD and Pop3Rd example programs added.
• Added function seeByteToShort
• Added function seeShortToByte