capsar(1)capsar(1)Namecapsar - prepares documents not in ASCII format for transport in the
Syntaxcapsar [-c] [-t] [-x[hTD]] [file]
The utility allows ULTRIX mail to support documents containing non-
ASCII data, such as DDIF. Only the DDIF and DOTS data types are cur‐
rently 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 and
The 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 docu‐
ment 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 mail software only
supports 7 bit mail.
3) The 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:
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
M@( ! 8$! ((/1$1)1B1?4D5!1%]415A4HX#)% !$1$E&(%1E>'0@1G)O;G0@
-----------End of motd.ddif : DOTS.ctod.compress.uuencode message
The 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 boundaries. Decoding
and uncompressing the data results in the original DOTS file.
The utility is built into Rand MH to provide DDIF mail support. It
can, however, be used with mail.
Options-c Causes to create an encapsulated DOTS bodypart from file. The file
must be a DOTS/DDIF type document.
-t Causes to write to the standard output the message type of file.
Message type can be either text or DOTS.
-xh 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 (for example, 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
-xT Extracts all the text parts of the mail message in file to the
-xD Extracts any DOTS bodyparts in file. The DOTS document is sent to
the standard output. This is the reverse of the -c option above.
The file must be specified for the -c option. If file is not
specified with the -x or -t option then the standard input is
The following are examples of how to use the command:
Encapsulates a DDIF document
capsar-c file.ddif | more
Lists the header line from the mail message
Extracts the encapsulated DOTS file from the file
capsar-xD file > file.dots
capsar-xD file | dtoc
In order to mail a DDIF/DOTS document 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 isn't
See Alsocompress(1), ctod(1), dtoc(1), mail(1), mh(1mh), mhmail(1mh), uuen‐
code(1), vdoc(1), prompter(1mh), DDIF(5), DOTS(5)capsar(1)