capsar(1)

NAME

capsar − prepares documents not in ASCII format for transport in the Mail system

SYNTAX

capsar [-c] [-t] [-x[hTD]] [filename]

DESCRIPTION

The capsar utility allows ULTRIX mail to support documents containing non-ASCII data, such as DDIF. Only the DDIF and DOTS data types are currently supported. DDIF is Digital’s standard format for document interchange. DOTS is an encapsulation of the encoded interchange form of a number of related data objects into a single composite object. For more information, see DDIF(5) and DOTS(5).

The capsar utility prepares a DOTS file or a DDIF document for transport in the mail system by performing the following steps:

1) The DDIF document is converted to DOTS format. As a DDIF document may contain more than one file, all files within the DDIF document are incorporated into one DOTS file which can be sent as one mail message. 2) Each DOTS file is then compressed and encoded using only printing ASCII characters. This is because ULTRIX only supports 7 bit mail. 3) The capsar routine encapsulates coded documents by adding leading and trailing lines, each surrounded by a <CR>. The lines should begin with 2 or more dashes (−) and some text that indicates the nature of the encapsulated message. The following is a typical encapsulated mail message:

To: anybody@anynode
Cc:
Subject: Another DDIF document

-----------motd.ddif : DOTS.ctod.compress.uuencode message
begin 0 motd.ddif
M__]@*" ,(" !BO.#P$# 8$* &UO=&0N9&1I9H0$)%546 "A@"B !@8K
MS@! P$”T1$248M96YC;V1E9"!R979I<V%B;&4@9&]C=6UE;G2@@/__?X"@
M@( ! 8$! ((/1$1)1B1?4D5!1%]415A4HX#)% !$1$E&(%1E>’0@1G)O;G0@

end
-----------End of motd.ddif : DOTS.ctod.compress.uuencode message

The capsar command can also extract different parts of a mail message, namely, the header information, the text part of the message, and the DOTS file that was encapsulated as described above.

Extracting the DOTS file is done by parsing the mail message and detecting the leading and trailing encapsulation bounderies. Decoding and uncompressing the data results in the original DOTS file.

The capsar utility is built into Rand MH to provide DDIF mail support. It can, however, be used with ucb mail.

SWITCHES

−c This causes capsar to create an encapsaulated DOTS bodypart from "file". "file" must be a DOTS/DDIF type document.

−t This switch writes to the standard output the message type of "file". Message type can be either text or DOTS.

−xh This switch extracts the mail header lines from "file". The header line must be at the beginning of the file and separated from the remaining text by a <CR> or <CRLF>. Each header line is a string containing a header field name (eg Subject), a colon (:), one or more spaces, and a field value. Each header line may have embedded continuation sequences it it (for example, LF followed by spaces or tabs).

−xT This switch extracts all the text parts of the mail message in "file" to the standard output.

−xD This switch extracts any DOTS bodyparts in "file". The DOTS document is sent to the standard output. This is the reverse of the −c switch above.

"file" must be specified for the −c option. If "file" is not specified with the −x or −t option then the standard input is used.

EXAMPLES

The following are examples of how to use the capsar command:

Encapsulates a DDIF document

capsar −c file.ddif | more

Lists the header line from the mail message

capsar −xh file.mail

Extracts the encapsulated DOTS file from the file

capsar −xD file > file.dots
or
capsar −xD file | dtoc

In order to mail a DDIF/DOTS dcoument you can use one of the following:

capsar −c file.ddif | mail -s "subject" address
capsar −c file.ddif | mhmail −subject "subject" address

Use the second command if you are using RAND mh.

A DOTS file is extracted from dxmail first extracting the message into a file. The dxmail utility has an extract feature built in so capsar −xD isn’t needed.

Museum