74 Trevino Lane
Conroe, Texas 77302
Business (409) 321-3220
BBS (409) 273-3112
NHUB: [email protected]
Welcome to Einstein Electronic Mail!
Einstein Electronic Mail (EEMail) is a fast, powerful email and
groupware system designed specifically for Novell Networks. It
has features found in systems costing thousands of dollars and
some features found nowhere else in the market. We hope you
enjoy using our product! It has been on the market for a year,
and has gone through many changes and updates. To date, we have
spent over 20 months in development and refinement. We have sold
systems to major corporations, school systems, law firms and
many companies of all sizes all around the world.
With the addition of the MHS compatible release in December 1991,
EEMail is positioned to become a major player in the electronic
mail marketplace. Once you have experimented with our package,
you'll wonder why the other guys charge so much!
This version of the program does not include complete documentation
for the users or the systems administrator. Experienced Novell
Systems Administrators should have no problems setting up the system
for EEMAIL use. If you should require more assistance than this brief
documentation provides, please call Devont Software's BBS at (409)
273-3112 (300-2400 bps, 24 hours a day). We would be happy to provide
you with assistance in setting up the program for your use. If you
are an NHUB user you can reach us by sending mail to [email protected]
CompuServe users can reach us with email at [70421,1506].
EEMAIL requires an IBM PC/XT, AT, PS/2 or compatible computer with 512K
RAM or more. Although EEMAIL will run on an XT-class system, a 286 or better
is recommended. Monochrome, Hercules, CGA, EGA, VGA and Super VGA video
modes have been tested and supported. Networking software is also required.
Novell Netware 286 and 386 has been tested and supported. ELS versions
have been tested and are supported. You'll need 470K RAM or more to use
all of EEMail's feature.
If running EEMail in TSR mode, you should be using a 286 or better workstation
with 2M RAM and an XMS or EMS memory manager.
Each workstation's CONFIG.SYS file should contain at least the following
After loading the network shells, you should have at least 470K RAM free in
order to run the program. Networks with a lot of objects in the bindery
(users, groups, printers, etc) may require a bit more free RAM.
On the average, a 100 user network requires 470K RAM Free or more to run
all modules of the program. If you are using a menu system that takes
up low memory, be aware of the memory requirements of your menu system!
Examples of menu systems that use up low DOS memory are Novell's menu
and WP Office menu. Saber menu users should use the "BATCH" option from
the program option line.
If you are going to communicate with other email systems, you'll need
Novell's Message Handling Service (MHS) program and an MHS server on
your network. MHS is available from your Authorized Novell Dealer.
Call 1-800-RED-WORD for details on acquiring MHS.
EEMail is not free software. A lot of time and effort (along with many
late nights and weekend work) has gone into the development of this
package. To date, we have spent over 20 months in the process, and
would sure like to have our efforts rewarded! To see how dedicated we\
are to this program, take a few minutes to review the Revision History
included at the end of this document. Most of the requests for program
changes have come from our user base.
You are granted a limited license to preview the software for 30 days.
If you continue using the program after the preview time period, send a
check or money order for $249.00 (per server license) plus $5.00 shipping
With your order, you will receive the latest version of the program (with the
closing banner removed) with a user's and system administrator's guide,
access to Devont Software's technical support BBS, free ugrades, tech
support and a commitment to making your E-Mail system a success!
If you have any comments, suggestions, improvement ideas or customization
requests, please call Devont Software's BBS at: (409) 273-3112. We
support 300-2400bps 24 hours a day, 7 days a week. We would really like
to hear from you!
Thank you for your time and effort in looking at this software. IF IT IS
NOT FOR YOU, PLEASE PASS ALONG THIS PROGRAM AND DOCUMENTATION TO SOMEONE
ELSE WHO MAY BE INTERESTED. We thank you all (you know who you are) for
your ideas and support!
Jim, Deb and Devon Tyson
Sold To: ____________________________________________________________________
City: ____________________________ State: __________ Zip Code: __________
Phone: ___________________________________ Data: __________________________
Netware Version: _______________________ Number of Users: __________________
Current EEMail Version: ________________ Obtained From: __________________
[ ] Copies Einstein E-Mail Unlimited Users @ $449.00 Each __________
[ ] Copies Einstein E-Mail 20 User License @ $249.00 Each __________
[ ] Copies Einstein E-Mail 10 User License @ $199.00 Each __________
Residents of Texas add Sales Tax (7.25%) _________
Shipping and Handling $5.00
Outside of US (except Canada) $5.00
Total Price _________
Please send remittance in form of Check or Money Order to:
74 Trevino Lane
Conroe, Texas 77302
>> Please allow two weeks for delivery <<
We welcome your comments! In the space provided below, please tell us what
you like about EEMail, what you don't like, what you'd like to see added,
and/or what features convinced you that EEMail was the product for you:
Novell Installation Instructions
To install EEMail on your network, follow the steps below:
1. Create a directory for the mailboxes. EEMail is flexible, in that you
may choose any volume in which to store the data. For example, if you
want to install the data files on SYS1:, type the following:
Note: You can install EEMail in the existing SYS:MAIL directory if
you desire. Note that you still have to grant trustee rights (Minimum
rights = RWOSCM) to this directory in order to run the program. If you
install in SYS:MAIL, Netware's SECURITY command may tell you that
you have excessive rights to this directory. No biggie, but just
make sure you are aware of this! We recommend that you install EEMail
somewhere else on your network, though. SYS:MAIL\user contains other
files pertaining to login scripts and printer defaults. It would be
wise to separate EEMail from these other data files if you ever want
to uninstall EEMail.
2. FLAG the files appropriately. You should mark the program files as SRO
(Shareable Read-Only) so the users cannot remove any of these files.
For example: FLAG *.* SRO The HELP files (HELP.*) need to be flagged
as SRW (Shareable Read-Write). For example: FLAG HELP.* SRW
3. Run the ADMIN.EXE program.
4. ATTACH to all servers on your network as SUPERVISOR or equivalent.
5. From ADMIN's main menu, select "Maintain User/Group List" then
"Import From Bindery." A listing of all attached servers displays.
If you are running MHS, name each server whatever you called it
in MHS' routing table. Otherwise, accept the default physical
server name. Press on the last field to complete. The
procedure will begin to build the user/group database.
6. Again from the ADMIN main menu, select "Maintain User/Group List"
then select "Edit User List." The user database displays. Users
that do not need to have a mailbox can be "Excluded" from the
list by pressing +
. For example, you should exclude
GUEST, print server accounts, batch server accounts, or other user
or group accounts that you do not want to show up in the user
listing. Return to the Main menu by pressing when you
have excluded all you need.
7. Select "Create Mailboxes." This program will create necessary data files
for each user account on the network. Note: You must be a SUPERVISOR or
equivalent to execute this program. Data files created with this procedure
are automatically flagged as SRW (Shareable-Read/Write) upon creation of
these files. All user's data files will be created, and they will be
ready to use the mail program. Excluded users will not have a mailbox
on the system. Note: A new mailbox will occupy approximately 7K of
disk space. A mailbox which contains a lot of mail will occupy more
space, of course.
8. Create a .BAT file for the users to access the program. You can be as
creative as you like, but keep in mind that the user MUST be placed in
the directory created in the first step in order to access his mailbox.
For example, if you elected to store your mail data in SYS1:, create a
.BAT file similar to the following:
echo Loading Einstein E-Mail...Please wait...
map m:=sys1:eemail >>nul
...return to home dir and menu..
The .BAT file you create should be placed in a common directory, such
as SYS:PUBLIC (usually defined as Z:) so all users can run it.
9. Assign Trustee assignments to the directory in which the mail data files
are to exist. The users must have ALL RIGHTS, except Supervisor and
Access Control (Or Parental, for NW 2.x). For example, if you placed
the EEMAIL data files in SYS1:EEMAIL, run SYSCON, create a group called
EEMAIL, and assign Trustee Directory Assignments for that directory. Add
ALL EEMAIL USERS to this new group. If you need more information about
running the SYSCON utility, refer to the Netware Systems Adminstration
manual. You could if you prefer, assign the group EVERYONE trustee
directory assignments to this directory without having to create a
Using EEMail's MHS Features
EEMail is an MHS-compliant mail system, meaning you can use the package
to commicate with email systems across the country, or connect to
message hubs such as Compuserve or Novell's NHUB message clearinghouse.
EEMail requires no special setup to accomplish this, only the following
environment variables be defined for each workstation:
MHSPATH The drive and colon for locating the MHS directories.
MHSNAME The name of your MHS hub.
A good place to set these variables is in the System Login Script (SYSCON).
For example, add the following lines to yours:
SET MHSNAME="MHS_NAME" (Replace "MHS_NAME" above with your MHS Hub name)
Before running EEMail, you need a pre-existing drive mapping to whatever
drive you specified in the MHSPATH environment variable above. For example,
add the following to your System Login Script:
If the MHS server is connected to a server that is not your default server,
you'll need to attach to that server before creating the drive mapping. If
all users do not have an account on the server in which the MHS server
is located, you must create one for each user on the server, and use that
connection to facilitate the drive mapping. The MHS installation will
create proper trustee assignments for each of the users automatically.
Assign no password to the account so the Login Script can perform the
connection without prompting the user for a password. For example:
Finally, you need to install MHS per the instructions found in the
MHS manual. If you require assistance, please call our technical support,
your dealer, or Novell for specific MHS installation instructions.
ADMIN allows you to set up remote Routing Tables to ease in sending mail
to remote users or groups. For instance, if you have several users on
a remote system that you would like to be able to refer to as "Sales"
while creating a message, you can use ADMIN's "Routing Table Manager" to
specify the complete route name of each of the members, and this group
will appear in the User List of all network users. Assume the remote
MHS connected server hub is called "DENVER." You could set up a route to
the remote group like:
Dist. List: [email protected],[email protected],[email protected],[email protected],[email protected] ...
Keep in mind that MHS is limited to having 64 addresses in the Send To:
field. If communicating with a large network through MHS, you should
consider breaking down the remote lists into managable groups so this
limit is not exceeded. EEMail will truncate an address list if the 64
user limit is exceeded.
If you just want to preview the program, and do not want to create a
mailbox for each and every user on your network, ADMIN will allow you
to create one mailbox at a time. Here's what you do:
Enter the EEMAIL data/program directory. Type "ADMIN /c USERID" (without
the quotes). Do this for a couple of users, including yourself, and
then run the MAIL program. Of course, you will only be able to send and
receive mail to/from those user accounts that you created from the command
Upgrading Older Versions
If you are upgrading from version 1.60 or below, you should use the UPGRADE.EXE
program (found on our BBS) to convert your user's data files.
If you choose not to use the UPGRADE.EXE program, then you should remove all
user data files, then reinstall the program from scratch. Follow these steps
in order to remove the older EEMail program files:
1. Enter the EEMail Directory (e.g. cd SYS1:EEMAIL)
2. Type "FILER" (without the quotes, of course)
3. Select the option that totally removes all the user subdirectories
(F5=Mark User Directories, press
, then select Remove Entire
4. Erase all the program files from the current directory.
5. Follow the directions above for installing EEMail
Flagging Mail Directories
For Netware 386 users, the mailbox directories created during the installation
procedure should be flagged PURGE. This will decrease the amount to server
resources required to track all of the deleted files (which in any mail system,
is a lot of files!). To flag all the user mailbox directories, perform the
following (you must be a SUPERVISOR or equivelent!)
FLAGDIR *.* PURGE (you could also add HIDDEN here if you desire)
If running MHS, you should also flag the MHS user directories as well as the
SND directory as purge. For instance:
flagdir snd P
flagdir *.* p
Einstein E-Mail Administration
EEMail is very easy to administer. After you have created all the mailboxes
for the user accounts, there is very little that needs to be done on a
regular basis. If you add users to your system, you will need to run
the "Create Mailboxes" function in the ADMIN.EXE program to create a
new mailbox for the user. If users already exist on your system, they will
not be affected by this procedure. Only new user accounts will be added
to the system. Note again, that you must be in the EEMail data directory
to perform any of the administration duties. Running the program anywhere
else will create new mailboxes in whatever directory you are currently
When users delete messages from their system, EEMail removes the message
record, but leaves the message text in the data files. This is done
purely for performance reasons. System Administrators need to "pack" the
user mailboxes at regular intervals. We recommend that this procedure be
be run at least once a month. To pack the user mailboxes:
1. Change to the Mail Data directory. If you elected to store the data
files in SYS1:\EEMAIL, type:
2. Select "Pack Mailboxes." An informative message displays, then you
are prompted with a "yes/no" box. After you have read the message,
select "yes" to perform the procedure.
3. Next, you are prompted if you would like to remove old messages. Old
messages are those that have already been read (OutBox messages are
always considered "old" messages). If you would like to remove
messages that are older than 90 (or whatever you specify) days, select
"Yes". If not, select "No."
If you choose "Yes," you are prompted to enter a number. This number is
used to scan the InBox and OutBox, and all messages which are older than
this number of days are removed from the system. Note that WasteBasket
messages are automatically removed after 10 days, so this procedure
does not affect those messages.
If you choose "No," the packing procedure will continue, and all messages
will be retained.
The packing procedure should be run when no users are accessing their
mailboxes. If a user has a mailbox open at the time this procedure is
run, that mailbox will be skipped. Not a mojor event, but it is recommended
that this procedure is run during off peak hours mainly because of the
increased traffic that occurs during the packing procedure.
For this reason, ADMIN allows you to specify parameters at start up to
allow you to run the packing procedure at a specified time. For instance,
you could let ADMIN pack all the mailboxes at 2am, when it's likely that
no one will be using the mail system. To do so, enter the following while
in the EEMAIL data directory:
ADMIN /p 02:00
The program will then go into "AutoPack" mode, waiting until 2am to perform
the procedure. The TIME parameter is in 24 Hour military time.
You can also "pack" one user's mailbox at a time from the command line. This
is to assist the administrator in recovering corrupted index/data files. To
use this feature, type the following while in the EEMAIL data directory:
ADMIN /p UserID
Where UserID is a valid user of the network. If the user does not have
any data files, nothing will be performed. The ACTIVITY.LOG file is
updated to show packing activity messages. You can view this file or
print it out to view any error messages.
EEMAIL allows the system administrator to exclude certain users or groups
from the mailing lists. You may have set up groups that you do not want
users to send mail to, such as print server accounts, remote groups, etc.
By default, EEMAIL Excludes the user account GUEST from all mailing lists,
and will not allow a user to send mail to that account. To exclude additional
users or groups from the mailing lists, perform the following:
1. Enter the drive/directory where the EEMAIL data files exist.
2. Run the ADMIN program by typing ADMIN at the command line.
3. From the ADMIN main menu, select "Exclude Users." A pick-list of
user accounts will display. Currently excluded users and groups
will have an asterisk (*) in the left-most portion of their name.
4. Using the cursor keys, move the highlight bar to a user/group account
that you would like excluded. Press the
key. A pop-up menu
box displays, confirming your selection.
Repeat the above steps for each user you would like excluded from the mailing
If you would like to re-include a user that you have previously excluded,
perform the following steps:
1. Enter the drive/directory in which the EEMAIL data files are stored.
2. Run the ADMIN program by typing ADMIN at the command line.
3. Select Exclude Users/Groups.
4. Using the cursor keys, move the highlight bar to a user/group account
that you would like included in the mailing lists. Press the