Lotus cc:Mail Import/Export for MS-DOS and OS/2 Release 5.12


This README.TXT file contains information about Lotus cc:Mail
Import/Export for MS-DOS and OS/2 Release 5.12 that became available
after the Import/Export Release 5.1 Release Notes were printed.

Subsequent to the release of Import/Export 5.11, it became
apparent that some changes were needed; therefore, the release
number was increased to Release 5.12.  

After the release of Export and Export2 5.11, improvements were 
developed; therefore, the release number was increased to Export and 
Export2 Release 5.12.

Please note that all references in this README.TXT to IMPORT.EXE
and EXPORT.EXE, used with the DOS operating system, also apply
to IMPORT2.EXE and EXPORT2.EXE for the OS/2 operating system, except 
when the DOS 3.x operating system is used.

This README.TXT files discusses the following items:

o	Importing binary file attachments

o	Using the new Directory-export sort order (DIRECTORY/PROPADD)

o	Importing with DIRECTORY/PROP

o	Using the DOS 3.x operating system

o	Importing with the optional parameter /PARTIAL

o	Using binary attachments with /PARTIAL, /HILITE, and /ITEMSIZE

o	Using /ITEMSIZE or /FILES/HEX 

o	Using Import with /FILES/SIZE0

o	Using Import for Lotus cc:Mail Mobile for Windows 

o	Forwarding messages with the /ITEMSIZE option

o	Treating CTRL-Z in OS/2 as line feed (LF)

o	Using /ITEMSIZE in third-party vendor applications

o	Importing updates as a user with access rights

o	Using Export from the Lotus cc:Mail Mobile for Windows Outbox 

o	Using the command line to export messages from the Outbox

o	Exporting for bulletin board synchronization


Importing Binary File Attachments
---------------------------------
When a message with binary file attachments is undeliverable, the
binary file attachments are written to the CCMAIL.UND file.


Using the New Directory-Export Sort Order (DIRECTORY/PROPADD)
-------------------------------------------------------------
The Lotus cc:Mail Import/Export for MS-DOS and OS/2 Release 5.1
Release Notes give a different sort order for exporting directories. 
Please replace the information on page 40 relating to the
/DIRECTORY/PROP parameter with the following parameter:

	/DIRECTORY/PROPADD

With the /DIRECTORY/PROPADD command-line parameter, the Export
program exports Directory entries in the following order: 

	P 		Directly connected post offices

	p		Indirectly connected post offices

	L, l, R, r  	Local users, remote local users, local mobile
			users, and remote mobile users are grouped
			together

	A, a 		Local alias users and remote alias users are
			grouped together

Each of these groups of Directory entries is sorted in alphabetical 
order.  /DIRECTORY/PROPADD functions like /DIRECTORY/PROP, except for
sorting Directory entries.  Any data in the address field (Addr:) for
"P", "L", and "R" entries is prepended with the name of the exporting 
post office.   Below is an example of the Export command line using 
/DIRECTORY/PROPADD.

	EXPORT /Npo-name /Ppo-password /Dpo-path /DIRECTORY/PROPADD

This command-line format reflects the name of the exporting post
office and the address of the entry when viewed from the exporting post
office.  This occurs because the address, specifically the post office
name, is only important to the exporting post office.

Example export from Silver-HUB Directory:

	Name: Silver-HQ
	Locn: P
	Addr: Silver-HUB 555-1234
	Cmts:

If the above entry is imported into Silver-HUB, the address will
be the telephone number (555-1234).  If the entry is imported into
another post office, the address will be Silver-HUB.  Actually, the 
address would be "Silver-HUB 555-1234" but the telephone number has no 
function.  Selection of the address component (post office name or
telephone number) is done automatically as a function of the importing
post office's location.  
				 
Lotus cc:Mail recommends that you replace /DIRECTORY and /DIRECTORY/PROP 
with the new /DIRECTORY/PROPADD command-line parameter.  Prior to 
the availability of this parameter, we recommended that you use 
/DIRECTORY/PROP when exporting a Directory to a downstream post office; 
in other cases, /DIRECTORY was recommended.  All three options are still 
available and supported; however, /DIRECTORY/PROPADD covers all scenarios.

Both the /DIRECTORY and the /DIRECTORY/PROP still function like they 
did in Import/Export Release 3.32.  Below is a brief description of 
the operation of each command.

/DIRECTORY

With the /DIRECTORY command-line parameter, the Export program exports 
Directory entries in the order that entries are listed in the exporting 
post office Directory.  This is still the default sort order for 
exporting Directory entries.  If you are exporting Directory entries 
that will then be imported into another post office, do not use this 
command-line parameter.  If you plan to import the exported Directory 
entries to another post office and propagate them, export them using 
either /DIRECTORY/PROP or /DIRECTORY/PROPADD.

Example export from Silver-HUB Directory:

	Name: Silver-HQ
	Locn: P
	Addr: 555-1234
	Cmts:

/DIRECTORY/PROP

With the /DIRECTORY/PROP command-line parameter, the Export program 
exports Directory entries with all post offices ("P" and "p" Directory 
entries) listed first in the Export output file, followed by all 
other Directory entries.  Each group of Directory entries is sorted in
alphabetical order.  Any data in the address field for "P" local post 
office Directory entries is replaced with the name of the exporting 
post office.  This command-line option operates like it did in 
Import/Export Release 3.32.

Example export from Silver-HUB Directory:

	Name: Silver-HQ
	Locn: P
	Addr: Silver-HUB
	Cmts:

	NOTE:	If you are exporting Directory entries which will be 
		imported to other post offices, export the entries with 
		the DIRECTORY/PROP or /DIRECTORY/PROPADD command-line 
		parameters.  Do not export Directory entries using the 
		/DIRECTORY command-line parameter.  

Using the /DIRECTORY/PROP or /DIRECTORY/PROPADD command-line parameters 
with Export properly prepares the Directory-entry address field.  Also,
using these parameters imports Directory entries much faster than the
default /DIRECTORY parameter.  


Importing with /DIRECTORY/PROP
------------------------------
Importing a directory file using /DIRECTORY/PROP will post the
entries from the import file to the ##DIRECTORY UPDATES bulletin
board for propagation to other post offices (as though they were
added with the ADMIN program).

In Release 3.32, Import posted the entire import file to the
##DIRECTORY UPDATES bulletin board when the import was completed, 
even if only a few changes were made to the Directory.  Import 
Release 5.11 (and above), now posts for propagation only those 
Directory imports that resulted in changes to the Directory.


Using the DOS 3.x Operating System 
----------------------------------
If you run Import or Export on a computer operating on any version of
the 3.x DOS operating system, include the following command line in your 
CONFIG.SYS file:

	FILES=20

While the number of files can be larger, 20 is the minimum number 
recommended.  Please refer to your 3.x DOS documentation for more 
information about the FILES line in the CONFIG.SYS file.


Importing with the Optional Parameter /PARTIAL
----------------------------------------------
In previous releases of Import, a header buffer larger than 4K caused 
looping after a bad message.  Import 5.12 correctly handles a 
header larger than 4K.


Using Binary Attachments with /PARTIAL, /HILITE, and /ITEMSIZE
--------------------------------------------------------------
In previous releases of Import, binary attachments were not
written to the CCMAIL.UND file when the /PARTIAL, /HILITE, and
/ITEMSIZE command-line options were set.  That problem was corrected 
with this release.


Using /ITEMSIZE or /FILES/HEX
-----------------------------
In previous releases of Import, the use of /ITEMSIZE or FILES/HEX
could cause file attachment corruption.  That problem was 
corrected with this release.


Using Import with /FILES/SIZE0 
------------------------------
Import with /FILES/SIZE0 and any combination of /FILES/MACBIN1, 
/FILES/MACBIN2, /FILES/APPSNGL1, or /FILES/APPSNGL2 caused the 
error "Binary file not found" instead of creating a zero-length file
item.  Import 5.12 now creates a zero-length file item.


Using Import for Lotus cc:Mail Mobile for Windows
-------------------------------------------------
Improvements have been made to Import Release 5.12.  Import 5.12 now
allows users to import messages into the Inbox from any sender;
however, if the Outbox folder is selected---either by the command-line
option /OUTBOX (the default) or by "To Folder: Outbox"---the local
user must send the message.

Example of Import command line:

	IMPORT /NLOCALPO /Pusers-password /Dpo-path @file /INBOX


Forwarding Messages with the /ITEMSIZE Option 
---------------------------------------------
In previous releases of Import, if a forwarded message was imported
with the /ITEMSIZE option, the forwarded header of the message would
include extra Itemsize information.  That problem was corrected 
with this release.


Treating CTRL-Z in OS/2 as Line Feed (LF) 
-----------------------------------------
In Release 5.12, CTRL-Z in OS/2 is now treated as LF and ignored
by the program.  


Using /ITEMSIZE in Third-Party Vendor Applications
--------------------------------------------------
	Note:  Third-party vendors should use /ITEMSIZE in their
	       applications.  

In order to insure that messages are read as intended, all third-party 
vendors should use the /ITEMSIZE parameter.  Using /ITEMSIZE insures 
the integrity of the entire message by making other programs aware of 
the actual message size.  It was possible for Import/Export to read 
reserve words, like "Message:", within the message text and then
truncate the actual message.  Note that if the reserve word "Include:"
begins in Column 1 of any part of the text field, truncation may still
occur.

For further information on /ITEMSIZE parameter usage, read the 
/ITEMSIZE Technote included at the end of this README.TXT file. 


Importing Updates as a User with Access Rights
----------------------------------------------
When a user doesn't have the appropriate access rights to make
updates, the following error messages are inserted in the CCMDIR.UND 
file:

   *** User without rights may not import directory updates ***
   *** User without rights cannot update public mailing lists ***
   *** User without rights cannot update bulletin board propagation lists ***
   *** User without rights may not change password ***


Using Export from the Lotus cc:Mail Mobile for Windows Outbox 
-------------------------------------------------------------
When a message is exported from the Outbox folder, recipients of
the message are exported into "To:" fields instead of "*To:" fields, 
which rendered the message undeliverable.  That problem was 
corrected with this release.

If a message is addressed to a bulletin board, the bulletin board 
name is now converted to a "To: bboard-name" field.

The author of a message exported from the Outbox is no longer
added to the "To:" field.

Messages exported from the Outbox are now deleted from the
Outbox after the export.

Export with Return Receipt (RRQ) corrections:  When a message is
exported from the Inbox with RRQ, the Return Receipt message goes
to the Outbox.  When a Return Receipt message is created, the sender
of the original message doesn't have to be in the Lotus cc:Mail Mobile
for Windows Directory.


Using the Command Line to Export Messages from the Outbox 
---------------------------------------------------------
To export messages from the Outbox, use the following command
line:

	EXPORT /NLOCALPO /Puser-password /Dpo-path @file /OUTBOX /MSGS/ALL

If /MSGS/ALL isn't used in the command line, no messages will be
exported.


Exporting for Bulletin Board Synchronization
--------------------------------------------
When exporting for bulletin board synchronization, use the following
command line:

	EXPORT /Nsilver-NY /Pny-pass /Dz:\path\to\silver-NY\ccdata 
	/bboard/"#name"

All the messages from the bboard called "#name" on the post office
Silver-NY will be exported, and addressed as follows:

	To: #name

This simplifies the task of using Export to synchronize bulletin board 
messages to another post office.  Previous releases of Export required 
an unconventional command line, which still works if used with Export 
Release 5.12.  


/ITEMSIZE Technote:      
								     
This technote informs third-party vendors that when they use the Lotus 
cc:Mail Import/Export utility in their applications they must incorporate
the /ITEMSIZE command-line parameter into these applications.  The
/ITEMSIZE command-line parameter ensures that messages are imported 
as intended.  Most third-party vendors have already incorporated this
parameter.  However, some third-party vendors are not using /ITEMSIZE.  

The Lotus cc:Mail Import/Export utility contains four .EXE executable 
programs: 

	o	IMPORT.EXE
	o	EXPORT.EXE
	o	IMPORT2.EXE
	o	EXPORT2.EXE

IMPORT.EXE and EXPORT.EXE are used with the DOS operating system, 
and IMPORT2.EXE and EXPORT2.EXE are used with the OS/2 operating system.  
The information in this technote is equally applicable to both the DOS 
and OS/2 programs.  All four .EXE programs are collectively referred to  
below as Import(2) and Export(2).

Using the /ITEMSIZE parameter allows Import(2) to accurately identify 
the beginning and ending of each message to be imported.  Without this
parameter, a text item containing a reserved word (for example, "Message:") 
at the start of a line within the item causes Import to incorrectly
think that the item is complete.  This can cause a message import to be
ended before the actual end of the message.

The /ITEMSIZE parameter is used to make Import(2) aware of the exact size
of each message which it tries to import.  When this parameter is used 
with Import(2), the program expects a byte count for each part of the 
message; namely, for the "Message:", "Contents:", "Text item:", 
"File item:", and "Fax item:" portion of each message.  The byte count
is a decimal number followed first by a carriage return/line feed (CR/LF),
then by that part of the message.  

When the /ITEMSIZE parameter is used with Export(2), the program writes a 
byte count for each part of the message; namely, for each "Message:", 
"Contents:", "Text item:", "File item:", and "Fax item:" portion of each 
message.  The byte count is a decimal number followed first by a CR/LF, 
then by the actual bytes of that part of the message.  In each case, 
the byte count is written on the line following the Import/Export 
reserved word beginning in the first column.

For text, file, or fax items, the item byte count is the size of the
item itself.  However, the byte count for "Contents:" includes all items 
included as part of the message's contents.  The byte count for 
"Message:" includes the number of bytes in the message header as well 
as the number of bytes for all items in the contents.

Using the /ITEMSIZE parameter, which gives an accurate byte count,
will prevent the problems mentioned above.  This parameter is recommended 
for any application using Import(2)/Export(2).

Below is an example of a message exported using the /ITEMSIZE 
command-line parameter.  If the /ITEMSIZE parameter is used when the 
example below is imported, Import(2) will properly recognize the byte
count for each section of the message and will know when the end of the
message has been reached.

	M:\CCADMIN\export /NCindy Martin /Ppassword /Dm:\ccdata /ITEMSIZE

	Message:
	4644
	From: Cindy Martin
	Date: 4/12/94 9:15AM
	To: Teresa Rizzo
	Subject: Accounts Audit
	Contents:
	4504
	Text item:
	44
	Distribution of financial audit statement.
	File item: AUDIT93.FIL 7/12/93 4:00pm
	4400

In the example, the actual AUDIT93.FIL file isn't shown.  If the
AUDIT93.FIL file were shown, the number of bytes would begin on the
line after the number 4400.  

To prevent incorrect message delivery, be sure to use the /ITEMSIZE 
command-line parameter in applications that use Import(2) and Export(2).
