Content-type: text/html Man page of capsar


Section: User Commands (1)
Index Return to Main Contents


capsar - prepares documents not in ASCII format for transport in the mail system  


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



Causes capsar to create an encapsulated DOTS bodypart from file. The file must be a DOTS/DDIF type document. Causes capsar to write to the standard output the message type of file. Message type can be either text or DOTS. 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 (for example, LF followed by spaces or tabs). Extracts all the text parts of the mail message in file to the standard output. 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 used.


The capsar utility allows 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(4) and DOTS(4).

The capsar utility prepares a DOTS file or a DDIF document for transport in the mail system by performing the following steps: 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. Each DOTS file is then compressed and encoded using only printing ASCII characters. This is because mail software only supports 7 bit mail. 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$* &amp;UO=&amp;0N9&amp;1I9H0$)%546 "A@"B !@8K

MS@! P$''T1$248M96YC;V1E9"!R979I<V%B;&amp;4@9&amp;]C=6UE;G2@@/__?X"@ 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 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 boundaries. Decoding and uncompressing the data results in the original DOTS file.

The capsar utility is built into the MH message handler to provide DDIF mail support. It can, however, be used with the mailx utility.


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 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.


compress(1), mail(1), mh(1), mhmail(1), uuencode(1), vdoc(1), prompter(1)




This document was created by man2html, using the manual pages.
Time: 02:42:56 GMT, October 02, 2010