Copyright: Copyright (c) 1994-1996, Andrius Cepaitis


Beemail Installation

Installation

Beemail is distributed as a compressed self-extracting archive file.  The file name is BEExxxx.EXE, where xxxx is the version number.  Extract the file into a temporary directory and run INSTALL.EXE from there (via File | Run in Program Manager,  by double-clicking on the icon in file manager, by double-clicking on the icon in Explorer (Win95), or by using Start | Run (Win95)).  The Installation program will lead you through all steps required to configure Beemail on your system.

Installation sequence

You will be led through the following dialogs:

Welcome

Source Directory Selection

Root Directory Selection

Confirmation of Directories

Copying the Files

File Error

Keep Current Configuration?

Program Group Creation

Success!

See also

Technical Specifications

Trademarks

Beemail™ HQ

Beemail License Agreement

A Short History


Install Welcome
Welcome

The Following Buttons Are Available From the Welcome Dialog:

Ok

Start Beemail installation.

Quit

Cancel Beemail installation and terminate.

Help

Open a help topic for the current dialog.


Source directory
Source Directory Selection

Beemail source directory

Enter the directory name where the Beemail distribution files are located.

Ok

Press Ok if the specified directory is correct.

Back

Return to the previous dialog.

Help

Open a help topic for the current dialog.


Root directory
Root Directory Selection

Beemail root directory

Enter a root directory name for the Beemail program, data and configuration files.  This directory name will be stored in the WIN.INI configuration file for later access by Beemail applications.

'Root' means that there will be a few more directories created, but all of them will be located in the directory entered here.

Ok

Press Ok if the specified directory is correct.

Back

Return to the previous dialog.

Help

Open a help topic for the current dialog.


Confirmation
Confirmation of Directories

This is a confirmation dialog to acknowledge that the Beemail source and root directories entered in the previous dialogs are correct.  Click Install to start copying Beemail files.

Beemail source directory

The directory where the Beemail distribution files are located.

Beemail root directory

The root directory for the Beemail program, data and configuration files.

Install

Start copying files.

Back

Return to the previous dialog.

Help

Open a help topic for the current dialog.


Copying files
Copying The Files

This dialog is displayed while Beemail files are being copied from the source directory to the root directory. There is a short description of each file displayed on the first line of the dialog.  Full source and destination file names are shown in two lines below.

Source file

File name from Beemail source directory.

Destination file

File name in Beemail root directory.

Help

Open a help topic for the current dialog.

Abort

Abort Beemail installation and return to the Welcome dialog.


File Copy Error

An error has occured while copying a Beemail file from source to destination directory!

Error explanation

A short explanation of the reason why the file cannot be copied.

Retry

Correct the problem and try copy the file again. E.g. you may need to close some applications that are using Borland DLL's or an old Beemail program (Hive, Beeline, Philip, etc.) is still running.

Replace

Replace the file even if the file version or file date of an existing file is newer than the file version or file date of the file from the Beemail distribution package.

Skip

Skip this file. CAUTION: if you skip the file, the Beemail installation may be incomplete which may result in unpredictable results.

Abort

Abort Beemail installation and return to the Welcome dialog.

Help

Open a help topic for the current dialog.


Keep current configuration?

Install has found your current Beemail configuration file in the INI directory!  You may want to keep your current Beemail configuration or create new files.

Yes

Keep current configuration.  Your current INI files will be used by a newly installed Beemail version. (Current INI files will also be saved in a separate directory).

No

Create new INI files.  Your current INI files will be saved in a separate directory before creating new INI files.

Help

Open a help topic for the current dialog.


Program group
Program Group Creation

Enter a program group name to hold Beemail program items.  Select a group name from the list or enter any name of your choice.

Program group

Enter a program group name here.

Create group

Create the program group and add Beemail program items.

Skip

Do not create a new Beemail program group.

Help

Open a help topic for the current dialog.


Success!

Beemail files are successfully installed.  To complete the installation process you will have to start Hive. Hive will:

1) Create default configuration files and will ask you to enter your system parameters if this is a first time Beemail installation (fresh installation);

2) Update your current Beemail configuration files if this is an update installation;

3) Build the nodelist index.

Start Hive now

Start Hive right now.  (INSTALL.EXE will terminate before Hive is started).

Quit

Quit INSTALL.EXE.  You will have to start Hive from the Beemail program group to complete the installation process.

Help

Open a help topic for the current dialog.


Technical Specifications

Beemail Technical Specifications

Hardware and software requirements

Windows system files

Beemail program group

Required external DLLs

Beemail directories and files

Beemail directories

Beemail log files

Beemail INI files


Hardware and Software Requirements

Hardware

IBM PC 386 or higher

VGA, PGA, SVGA or compatible display adapter and monitor

Standard serial communications port

Mouse or other Windows-compatible pointing device

Memory

4 MB of RAM (8MB recommended for Windows 3.x / 16MB recommended for Windows 95 or Windows NT)

10 MB of free hard disk space before installation

Software

Microsoft Windows 3.1, Windows 95 or Windows NT

Windows or DOS based BBS system (optional)

Modem

Hayes or Hayes-compatible modem

NOTE: The modem must be capable of recognizing the DTR (Data Terminal Ready) and the CD (Carrier Detect) signals

Telephone line

A regular telephone line or a PBX system


Windows System Files

Changes in the WIN.INI file

The Installation program adds the following section to the WIN.INI file:

[Beemail]

Version = Beemail x.xx

Date = installation date

Root = Beemail root directory

Ini = location of *.INI files

Changes in the AUTOEXEC.BAT file

Make sure the following statement with the location of your WINDOWS directory is included in your AUTOEXEC.BAT file:

SET WINDIR=C:\WINDOWS

Try to include your Windows directory as the first directory in the PATH statement in your AUTOEXEC.BAT file.


Beemail Program Group

A Windows Program Group can be created by the Installation program.  To create a group answer yes when the Program Group selection dialog is displayed.  Choose an existing group name from the list box or enter a new name.  The following program items will be created:

History - changes in the most current Beemail versions

Hive - Beemail setup and controller application.  Must also be active if any communications are to take    	place using Beemail (I.e., if you plan to load Beeline).

Hive Example - a Hive example

Line A - Beemail communications program (Beeline)

Line B - another Beeline example

Philip - The Beemail tosser application

User's Guide - Beemail Users Guide (Windows help file)

First-time install

The first thing to do after installing Beemail is to start Hive - the Beemail setup and controller program. Hive will then create (or update existing) Beemail configuration files.  Answer Yes to all dialogs that will be displayed.  Edit any data in the dialogs according to your system.

Any old INI files present in the Beemail INI files directory are moved to a newly created backup folder, e.g. "c:\beemail\ini\080.old".

Example INI

There are example *.INI files provided with the Beemail distribution.  The example files are located in Beemail folder, e.g. "c:\beemail\ininew".


Required External DLL's

System DLL Files

Available on the Beemail HQ FTP site

The following files are copied by the Installation program to your Windows system directory: bc450rtl.dll, bids45.dll, ctl3dv2.dll, and owl250.dll.  These DLL files must be present in your Windows system folder, e.g. C:\WINDOWS\SYSTEM, in order for Beemail to run.

If you experience any unpredictable crashes on your system, it is possible that one or more of these DLL files is either missing, damaged, or has been replaced by another application.  Please compare the checksums of these DLL files against the values listed in the table below.

Below are the checksums of the DLL files required by Beemail (produced with VALIDATE version 2.00 Copyright (c) McAfee, Inc. 1994) file name, size, file date, file time, check1, check2:

bc450rtl.dll,  219 648, 11-17-1994, 4:50a, 2DC7, 94A2

bids45.dll,     60 758, 11-17-1994, 4:50a, A5BC, 6FE2

ctl3dv2.dll,    21 648, 06-10-1994,  0:00, EE71, 74A4

owl250.dll,    485 184, 02-13-1995, 7:17p, 7188, DA96

Note: the checksum of  the file OWL250.DLL is calculated after applying patch BC45P2.RTP.


Beemail Directories

There are a lot of directories that have to be specified for a mail system to function.  All of these directories will be created as needed.

Beemail System Directories

The following directories are created during the Beemail installation.  Their location cannot be changed.

Binary files (\beemail\bin)

All Beemail executable files (EXE) and dynamic link libraries (DLL) are located in the Beemail binary files directory.

INI files (\beemail\ini)

All of the Beemail INI files go here.

Old INI files (\beemail\ini\vvv-x.old)

During installation all Beemail INI files are updated.  The old files are moved from the Beemail INI files directory to the Beemail Old INI files directory.

Other Beemail Directories

The following directories are configured as a default during Beemail installation.  The location of these directories can be changed in various Beemail options dialogs.

Log Files (\beemail\log)

Beemail log files.

Text Files (\beemail\text)

A default location to look for all text files.  For example, the greeting files specified in the Handshake options dialog.

Tool Files (\beemail\tools)

A default location to look for all external application files.  For example, program files and PIF files specified in the Handshake options dialog.

All BAT and PIF files should be located there.

Temporary Files (\tmp)

Any kind of temporary files.  Files in this directory are created only for temporary short-term use.  These files are normally removed by Beemail.

Nodelist Files (\beemail\nodelist)

The location for nodelist index file and the default location for nodelist files.

Incoming Files (\beemail\incoming)

All received files are placed here.

Inbound Recovery (\beemail\incoming\restart)

Files being received and aborted files are placed here.

Outgoing Files (\beemail\outgoing)

Beemail looks for files to be sent in the outgoing files directory if the file path is not specified.  This applies to all outgoing files, including netmail file attaches and files manually added in the outbound queue.

Also the location for outgoing compressed echomail packets (Xmail).

Netmail Messages (\beemail\netmail)

Fido *.MSG netmail message directory.  This is also a FrontDoor-style outbound queue.

Incoming PKT Files (\beemail\pktin)

Compressed echomail packets (bundles) are uncompressed in this directory.

Outgoing PKT Files (\beemail\pktout)

Outgoing PKT files are stored in this directory before compressing.

Temporary PKT Files (\beemail\pktque)

Netmail packets created by Beeline during netmail scanning.  Removed after the netmail and accompanying file attach files are sent.

BinkleyTerm  Outbound (\beemail\bink\out)

BinkleyTerm compatible outbound queue directory (OUT, CUT, HUT, FLO, CLO, HLO).


Beemail Log Files

All of the Beemail log files are located in the log files directory.

Beeline Log Files (x-line.log)

There is a separate log file for each Beeline.

Hive Log File (hive.log)

Hive log file.

Philip Log File (philip.log)

Philip log file.


Beemail INI Files

Beemail INI Files

NOTE:  Under normal use, you should never have to hand-modify any of the INI files used by Beemail.  This section is provided both as a reference for the technically inclined user, and in case something does go wrong and hand-editing is necessary.

MSGAREA.INI  (Message Base / Message Area Configuration)


MSGAREA.INI

Message Base List

[b]

A list of all Beemail message bases.  The item key specifies the message base tag (or ID), and  the item value specifies the message base description.

Message Base Items

bF

Message base format:

1 = Pass-through areas

2 = Fido (*.MSG)

3 = JAM

4 = Squish

5 = Hudson

bN

Message base directory name (SDM, JAM, Squish) or message base file name (Hudson).

bO

Origin line for message base areas.

bA

Local system address to use when for outgoing packets.

Message Area List

[a]

A list of all Beemail message areas.  The item key specifies the message area tag (or ID), and the item value specifies the description of the message area.

Message Area Items

aB

Message base ID.  An item in the [b] section above.

aF

Message area file name (SDM, JAM, Squish) or message area board number (Hudson).

aIE

List of import and export systems.


Glossary
Beemail™ Glossary

A

BBS

Bee

C

DTE vs. DCE

EMSI

Excalibur

Front-end

FTS-0001

Function request

GUI

H

INI section

J

K

L

Message base vs. Message area

N

O

PowerBBS

Q

RFC-822

S

T

U

V

W

X

Y

Z


BBS

A Bulletin Board System (BBS) is a program that allows callers to connect to the system using a terminal program and a modem and directly access messages, files and other online services.


Bee

Any of several winged, often stinging insects that gather pollen and nectar from flowers.  Some bees, such as the honeybee, live together in colonies.

A gathering where people work together or compete against one another: a quilting bee; a spelling bee.

Idiom.  A bee in (one's) bonnet - an idea that fills most of one's thoughts.

These sound alike: bee, be.

Beeline - the fastest and most direct course, as one that might be taken by a bee going to its hive.


Excalibur

A GUI BBS system for MS Windows.  In medieval legend, the sword of King Arthur.


Front-end

A communication program that answers inbound calls and starts other processes depending on what type of user (or other system) the caller is.  The caller can be an ASCII human caller, a mailer program, a GUI Client program for a Windows BBS, an incoming FAX or other communication program.


FTS-0001

A Basic FidoNet ® Technical Standard by Randy Bush, Pacific Systems Group, 30 August 1990.

This document specifies a standard for the FidoNet community.  FidoNet nodes are expected to adopt and implement this standard.

This document defines the data structures and communication protocols which a FidoNet implementation must provide.  The implementor of FidoNet compatible systems is the intended audience of this document.


Function request

Function requests execute a function program upon receiving a specific file request.


GUI

Graphical User Interface, such as that presented by Microsoft Windows, or the X-Window system under UNIX.


PowerBBS

A GUI BBS system for MS Windows.  Author Russell E. Frey


RFC-822

Standard for the format of ARPA Internet text messages.  This standard specifies a syntax for text messages that are sent among computer users, within the framework of electronic mail.

Some message systems may store messages in formats that differ from the one specified in this standard. This specification is intended strictly as a definition of what message content format is to be passed BETWEEN hosts.


EMSI

Electronic Mail Standard Identification.  The standard protocol used by most FidoNet compatible mail systems in use today.


DTE vs. DCE

There is much confusion in the online world about the difference between DCE (Data Communication Equipment) speed and DTE (Data Terminal Equipment) speed.  The DTE speed is the speed that your computer is talking to your modem at.  This speed is typically locked, or fixed, at one speed, usually 38400 or 57600bps.  The speed stays the same no matter what speed the modems are actually connected at.  The DCE speed is the speed that the modems are talking to each other at.  This varies from connection to connection based on the type of modems involved, telephone line conditions, and so on.  The DTE speed is almost always higher than the DCE speed due to the fact that via data compression, modems can transmit data at a rate which apparently exceeds the actual connect rate.  Unless the computer is feeding the modem data faster than it is going out over the line, this is not possible.


INI section

A section in an .INI file is simply a group of lines which begins with a name enclosed in square brackets ([ & ]) and ends when the next section name is encountered, or at the end of the file in the case of the last section.

Each line in an INI file (except comment lines and section header lines) consists of a key and a value, separated  by an equals sign (=).  The key is the name of a parameter which the program that uses the INI file is looking for.  The value is the value you want that parameter to have.  An example would be:  bN=C:\BEEMAIL\JAM.


Message base vs. Message area

A message base in Beemail is defined as a group of message areas all having the same message base format and directory (or Hudson file) on the disk.  For example, all your JAM format areas would normally be stored in C:\BEEMAIL\JAM.  A message area is simply one of the areas in a message base, and would normally correspond to your individual echoes (or conferences).


Beemail License Agreement
Beemail™ License Agreement

Preface

Beemail (tm) is a Computer Program which functions as a mail transport system and Bulletin Board System front-end.  It is copyrighted by Andrius Cepaitis.

This is a legal contract between you, an end user of the Beemail (tm) Software ("Beemail"), and Bokera Ay, a Finnish company whose postal address is:

Bokera Ay

PL 15

00301 Helsinki

FINLAND

Telephone: +358-0-87893022

In order to protect its interests in Beemail (tm), Bokera Ay does not sell any rights to Beemail (tm).  Rather, a Beemail License Key is sold which allows Beemail (tm) to operate for the number of lines purchased.

BY INSTALLING AND USING YOUR BEEMAIL (tm) LICENSE KEY, YOU AGREE TO ALL THE TERMS OF THIS LICENSE AGREEMENT.  IF AT ANY TIME YOU ARE FOUND TO BE IN VIOLATION OF ANY OF THE TERMS CONTAINED HEREIN, BOKERA AY WILL REVOKE YOUR LICENSE TO OPERATE BEEMAIL (tm) AND YOU MAY THEN BE SUBJECT TO LEGAL PENALTIES.

Software License

You are hereby granted a nonexclusive license to use Beemail (tm) on as many telephone lines as allowed by the version you have purchased, as detailed by the following table:

"/SL" Versions:  One (1) Telephone Line Only

"/M2" Versions:  Two (2) Telephone Lines Only

"/ML" Versions:  As many telephone lines as you deem necessary, up to the limits imposed by the software itself, which is currently twenty-six (26), and/or your hardware configuration

Use of Beemail (tm) on multiple lines is subject to the following restriction:

All lines in a multi-line Beemail (tm) installation MUST BE part of  the same Bulletin Board  System or Network Node.  This means, for example, that you may not purchase an /ML version of Beemail (tm) and run 10 lines on your BBS and another 16 lines on your friend's BBS.

If you are running multiple lines on multiple networked computers (as with a LAN), the license key MUST BE LOCATED ON ONLY ONE OF THE COMPUTERS.  This would, of course, usually be the file server computer.

This is a license only, and does not confer any ownership privileges on you.  All ownership in Beemail (tm) is retained by Bokera Ay, and the Copyright holder, Andrius Cepaitis.  This ownership includes the Beemail License Key as well - you are not the owner of the key, only a licensee.

You must not give anyone any copy, regardless of what form it is in, of Beemail (tm) or the Beemail License Key.  This includes modem transfers, diskettes, hard copy listings, as well as any other method.  The only copy you are permitted to make is a copy  for yourself, kept at your location, solely for backup purposes.  You are allowed to move the software from one of your computers to another one of your computers, as long as such a move does not violate any other part of this license.  For example, if you have purchased a "/SL" Beemail (tm) License Key, you may copy Beemail (tm) between your own computers, BUT IT MUST ONLY BE RUNNING ON *ONE* OF THOSE COMPUTERS.  Another example is where you are running multiple lines, with each line on a different computer, with all the computers networked together.  In this case, the Beemail License Key must be located on ONLY ONE COMPUTER, normally the file server machine.

You are also prohibited from making any attempt to disable the copy protection features of Beemail (tm).  This includes modifying the executables so as to disable the Beemail License Key check or make it erroneously report a "good" key, reverse engineering the key algorithm to produce a key generator, or any other such methods.  You are also prohibited from making *ANY* modifications, for whatever reason, to Beemail (tm) or any of its components.

This license is granted only to YOU, and may not be transferred to anyone else without prior authorization from Bokera Ay.  This license is in effect until it is terminated.  Termination of this agreement will occur WITHOUT NOTICE if you are found to be in violation of any part of this License agreement.

Limited Warranty

Beemail (tm) and its documentation and help files are provided "as is", without any warranty of any kind.  Neither  Bokera Ay nor any Beemail (tm) dealer or support site make any warranty, guarantee, or any representation regarding the use or results of use of Beemail (tm) or its documentation and help files.  Neither Bokera Ay nor any Beemail (tm) may be held liable for any damage, regardless of type, which may occur from the use or misuse of Beemail (tm).  All risks are assumed by You.

THE ABOVE ARE THE ONLY WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED (INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE), THAT ARE MADE ON BEEMAIL (tm).  NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY BOKERA AY, ANY BEEMAIL (tm) DEALER, DISTRIBUTOR, AGENT, EMPLOYEE, OR SUPPORT SITE SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR ADVICE.

NEITHER BOKERA AY NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTION OR DELIVERY OF BEEMAIL (tm) SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE EVEN IF BOKERA AY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Acknowledgement

YOU ACKNOWLEDGE THAT YOU HAVE READ THIS ENTIRE DOCUMENT, UNDERSTAND IT, AND AGREE TO BE BOUND BY ALL OF ITS TERMS.  FURTHERMORE, YOU AGREE THAT THIS DOCUMENT COMPRISES THE SOLE AND COMPLETE AGREEMENT BETWEEN YOURSELF AND BOKERA AY AND THAT THIS DOCUMENT SUPERCEDES ANY OTHER AGREEMENT, BE IT WRITTEN OR ORAL, REGARDING YOUR LICENSE OF BEEMAIL (tm).

Licensor:

Bokera Ay

PL 15

00301 Helsinki

FINLAND

Telephone: +358-0-87893022


Trademarks

Trademarks

ALLFIX - Copyright © 1993 Harald Harms. All rights reserved.

ARC, ARCmail - Thom Henderson, System Enhancement Associates

ARJ - Copyright © 1990-93 Robert K Jung.

BGFAX - Copyright © 1993-1995 B.J. Guillot.  All Rights Reserved.

"BinkleyTerm" and "Freely Available" are trademarks of Bit Bucket Software, Co.

Blue Wave Offline Mail Reader - Copyright © 1992 by Cutting Edge Computing. All Rights Reserved.

Borland C++ - Copyright © 1994 Borland International, Inc. All Rights Reserved.

DBridge - Copyright © 1987-1995, Chris Irwin. All Rights Reserved.

Excalibur BBS - Copyright © 1994-95, Excalibur Communications, Inc. All Rights Reserved.

FastEcho -  Copyright © 1991-93 by Software Technik Burchhardt

FrontDoor - Copyright © 1986-1994 Joaquim Homrighausen All Rights Reserved.

Fido and FidoNet are registered marks of Tom Jennings and Fido Software

GEcho - Copyright ©1991-1994 Gerard J. van der Land. All rights reserved.

The GoldED Message Editor - Copyright © 1990 - 1993 By Odinn Sorensen

IBM, IBM OS/2 - International Business Machines Corporation

InterMail - Copyright © 1992-1994 InterMail Software Inc. All rights reserved.

ITRACK - © by Frank Prade 1992, Munich

JAM(mbp) - Copyright © 1993 Joaquim Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. All Rights Reserved.

LHA - Copyright © Haruyasu Yoshizaki, 1988-91

MS DOS, MS Windows, Windows NT and Windows 95 are registered trademarks of the Microsoft Corporation.

Pak - Copyright © 1988-90 NoGate Consulting

PGP - Copyright © 1990-1995 Philip Zimmermann, Phil's Pretty Good Software.

PKZIP, PKUNZIP - Copyright © 1989-1993 PKWARE Inc. All Rights Reserved.

PowerBBS for Windows - Copyright © 1989-1995 by Russell E. Frey. All rights reserved.

QuickBBS - Pegasus Software

RemoteAccess - Copyright © 1989-1993 Wantree Development & Andrew Milner. All Rights Reserved.

SemPoint - Copyright © 1992-95 Andrea Matta

SQLBase, SQLWindows - Copyright © 1994 Gupta Corporation. All rights reserved.

Squish - Copyright © 1990, 1991 by Scott J. Dudley.  All rights reserved.

UUENCODE/UUDECODE - Copyright © 1983 Regents of the  University of California

X.00 - Copyright © 1993 by Raymond L. Gwinn

WWIV - Copyright © 1989 White Star Software

ZMODEM was documented by Chuck Forsberg, Omen Technologies Inc.

Any other product names mentioned in this documentation may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.


Beemail™ HQ

Beemail HQ BBS

Beemail HQ is the main Beemail Support Site, located in Helsinki Finland.  Beemail HQ BBS is open 24 hours a day, running Beemail as the FidoNet mailer and several Windows and DOS BBSes.  You can log into Beemail HQ using appropriate Windows BBS clients or with ANSI terminal.

Location: 	Helsinki Finland

Fidonet: 	2:220/777

BeemNet: 	700:700/1, 700:700/2

Voice: 	+358-0-87893022

BBS phone: 	+358-0-8785-338, +358-0-8793103

FAX: 	+358-0-8793-103

E-mail: 	hq@beemail.com

Sales/orders: 	sales@beemail.com

FTP site: 	ftp://beemail.com

WWW site: 	http://beemail.com

WWW & FTP sites, Listservers

All public Beemail release files are placed on Beemail FTP site.  WWW site is to provide general information to the public about Beemail products.

Beemail WWW Site:http://beemail.com

Beemail FTP Site: ftp://beemail.com

List servers & info

Send an empty message to help@beemail.com for instructions how to use Beemail list services on the Internet.  Send an empty message to info@beemail.com to get the latest Beemail product information.  To subscribe to the public FREE Beemail listserver send a message to bee-list@beemail.com with the following text in the message body:

SUBSCRIBE bee-list

Webmaster

If you have any special questions or suggestions about Beemail software, please send a message to webmaster@beemail.com.

Beemail HQ Postal Address

Bokera Ay

PL 15

00301 Helsinki

FINLAND

Beemail HQ Bank Account & VAT

Banker: Merita Bank, FINLAND

Merita Bank SWIFT Code: MRIT SI HH

Account Holder: Bokera Ay

Account Number (USD): 200162-75234

Account Number (FIM): 200118-182613

Bokera Ay's EU VAT registration number: FI10413992

Value added tax (VAT) is 22%

Beemail HQ Product Ordering Information

Payments are accepted by Check, Bank Transfer or Cash.  No Credit Cards accepted.  Checks and Cash must be sent to Beemail HQ Postal Address.  Cash should only be sent by registered or recorded post.  Make Checks payable to Bokera Ay.  Send Bank transfers to Bokera Ay Bank Account.

Residents of EU (European Union) add 22% VAT (Value Added Tax) to the Total sum of contract when transfering money to Beemail HQ.  Include your EU VAT Registration Number (if you have registered for VAT) in your check and add 0% (zero %) VAT.

Copyright © 1994-96 Andrius Cepaitis. All rights reserved.


Short history

Note for beta testers: do not mix files from different Beemail vertions together - it wouldn't work. E.g. do not try to run Hive from version 0.90 and Beeline from version 0.92.

Files

BEE092.ZIP - Beemail 0.92, "Wild Bee" release, full install.

BEE0212.ZIP - Beemail 0.93.0212, updated EXE & DLL.

BEE0212 (1996.02.12)

Blank Mail directories after install.

Beeline state (in info window) is changed if node is 'Forced immediate' in the outbound queue.

Correct message date in imported messages.

Set tear and origin lines during scan if none are found in the message.

Set origin line for messages exported from Grail database.

BEE092 (1996.02.08)

INI files structure has been changed. Click Hive | Other | Refresh INI files to update INI files from version 0.90 to 0.92.

Separate origin AKA and origin line for each message base can be specified.

Address lists changed from LISTBOX style to EDIT style in option dialogs.

New EVENT LENGTH options in mail and external events time dialog.

On-line files are removed from outbound queue after mail session.

Forced polls start immediately and are removed from the outbound queue after successful mail session.

Beeline is reopened after external event with Reopen line checked.

BEE0201 (1996.02.01)

JAM message base SCANNER! Export local messages from JAM message base, import to Grail database and pack in packets for nodes in 'connections' list.

Bug corrected: origination and destination addresses in echomail messages are now correct.

Grail echomail export: all messages are addressed to 'All'.

BEE091 (1996.01.31)

Old command line switches (Line, RunMin, Toss, etc.) are not supported anymore.

Removed space in AREA:XXX kludge line.

Removed INTL kludge from echomail messages.

Beemail will dial immediately after an inbound call. That is, there is no dial delay after inbound calls - Beemail only waits between two outbound calls.

New 'Export real names' option in Grail database options dialog (Hive | Other | Grail options).

New 'max no connect tries' option in Dial limits dialog (Beeline | Options | Dial limits).

Support for multiple file attaches in one netmail message (two file names on one subject line).

End dynamic event immediately if there is no mail to send during the event.

Bugs corrected: Type 2+, type 2.2 packets; file requests are sent and processed.

BEE090 (1996.01.20) "Wild Bee"

All command line parameters for Hive, Beeline, Philip and for external handshake programs described in Beemail Help.

Type 2, type 2+ and 2.2 packet support (FTS-001, FSC-039, FSC-045).

'Force immediate' item in outbound queue also resets dial counters.

Primary a.k.a. in Behaviour window.

BEE0116 (1996.01.16)

Grail: "could not get index for:" error message (and following GPF) should be corrected.

Mail only event: BBS callers are not allowed (all handshakes except EMSI are disabled during mail only events).

External event buttons in Beeline: show event comment as a 'hint text' on the status bar.

BEE0114 (1996.01.14)

Help: Service requests.

A bug in Beeline when reloading after PowerBBS should be fixed.

Minimum 'Wait' time in Beeline is 0, i.e. Beeline windows are opened immediately after startup.

Command line parameters are displayed in Beeline and Philip log windows on startup.

TOM089 (1996.01.13)

"Service request" feature. Service request options dialog (Hive | Files | Service requests).

Service request program is triggered by receiving a file with the specific name. The service request program is started with the following parameters: 1) received file, 2) file name with list of files to send back, and 3) D'Bridge compatible caller info file name. All file names include disk letter and full path.

NOTE: a temporary directory C:\TMP must exist on C: disk when using service requests.

Beemail will wait for all service request programs to complete before completing the mail session.

BEE088 (1996.01.11)

Help topic: Excalibur BBS.

E-mail and conference message import and export from Grail database. E-mail messages are exported to the netmail folder. Conference messages are packed to outgoing packets and optionally stored in JAM message base.

Exporting user handles instead of real user names from Grail.

Pause between separate messages during import and export from Grail.

Non standard ^a kludge lines (e.g. ^aBBS: Maximus) from imported echomail messages are stored in JAM message base header file (JHR), not in the message text.

Expires on Feb 1, 1996.

BEE0110 (1996.01.10)

Help topics: Excalibur, Beeline;

Grail user handle names (required by Beemail) must be 'Fido' and 'Grail';

Grail database conferences are imported in one pass during toss;

New Grail database conferences are automatically created;

Grail database E-mail and message scan is disabled;

Correct CRC values in JAM;

Line tag in Beeline frame window caption.

BEE086 (1996.01.05)

Beeline options menu BUG corrected.

Message area tag length can be 80 chars long.

External event options: 1) add to control bar, 2) bitmap file name. If (1) is checked, a button is added on Beeline control bar. By pressing the button one can start external event from Beeline.

Install sets default a.k.a. address in System options dialog.

AA button is set to on (pushed) by install program.

If external event is active, it cannot be started again. The event must end before is can be started again.

BEE0104 (1996.01.04)

A bug (that caused Beeline to crash) in Z-send module corrected.

A few problems while skipping files during Z-modem mail session.

A short pause before sending next file during Z-send.

Pretty tile in Beeline brings Mail events window in the middle of the frame window.

Open/close item in Beeline system menu to close and open line while Beeline is iconic. Short cut F4 can be used.

Confirmation message is displayed on attempt to close line during mail session.

A new button on Beeline control bar.

BEE0103 (1996.01.03)

Some changes in Z-send module (hangs at 0 bytes bug should be corrected).

File I/O error bug when sending zero length files correcter (zero length files are not sent anymore).

Date and time lines in EXTRA!.BEE file.

Number of files matching wildcard in netmail attach (and Beemail send files) is limited to 50.

'File requests removed' message line in log file.

'Total bytes sent' message removed.

Active event, next event and next mail only event info lines in Beeline information window.

Mail events are not started if Beeline re-opens after event end time.

External events are not started if Hive restarts after event end time.

999 minutes until next event bug corrected.

BEE0102 (1996.01.02)

Netmail messages and attached files can be deleted from outbound queue in Beeline.

Fixed nodelist update problem (LF instead of CR/LF at the end of line).

'Cannot open nodelist file xxx' message will be displayed only once.

End of history


Authors

Zygimantas Cepaitis

Project management

Fidonet: 2:220/777

BeemNet: 700:700/1

Internet: hq@beemail.com

Andrius Cepaitis

C++ programming and documentation

BeemNet: 700:3700/77

Internet: andrius@beemail.com

Linas Siniauskas

Excellent testing

Fidonet: 2:470/1

BeemNet: 700:3700/1

Internet: linas@beemail.com