diplodocus.org Git - nmh/blob - man/mhbuild.man

   1 .TH MHBUILD %manext1% "January 23, 2014" "%nmhversion%"
   2 .\"
   3 .\" %nmhwarning%
   4 .\"
   5 .SH NAME
   6 mhbuild \- translate MIME composition draft
   7 .SH SYNOPSIS
   8 .na
   9 .HP 5
  10 .B mhbuild
  11 .I file
  12 .RB [ \-auto " | " \-noauto ]
  13 .RB [ \-list " | " \-nolist ]
  14 .RB [ \-realsize " | " \-norealsize ]
  15 .RB [ \-headers " | " \-noheaders ]
  16 .RB [ \-directives " | " \-nodirectives ]
  17 .RB [ \-rfc934mode " | " \-norfc934mode ]
  18 .RB [ \-contentid " | " \-nocontentid ]
  19 .RB [ \-verbose " | " \-noverbose ]
  20 .RB [ \-check " | " \-nocheck ]
  21 .RB [ \-headerencoding
  22 .IR encoding\-algorithm
  23 .RB " | " \-autoheaderencoding ]
  24 .RB [ \-dist ]
  25 .RB [ \-version ]
  26 .RB [ \-help ]
  27 .ad
  28 .SH DESCRIPTION
  29 The
  30 .B mhbuild
  31 command will translate a MIME composition draft into
  32 a valid MIME message.
  33 .PP
  34 .B mhbuild
  35 creates multi-media messages as specified in RFC 2045
  36 to RFC 2049.  This includes the encoding of message headers as specified
  37 by RFC 2047.
  38 .PP
  39 If you specify the name of the composition file as \*(lq-\*(rq,
  40 then
  41 .B mhbuild
  42 will accept the composition draft on the standard
  43 input.  If the translation of this input is successful,
  44 .B mhbuild
  45 will output the new MIME message to the standard output.  This argument
  46 must be the last argument on the command line.
  47 .PP
  48 Otherwise if the file argument to
  49 .B mhbuild
  50 is the name of a valid
  51 composition file, and the translation is successful,
  52 .B mhbuild
  53 will replace the original file with the new MIME message.  It will rename
  54 the original file to start with the \*(lq,\*(rq character and end with the
  55 string \*(lq.orig\*(rq, e.g., if you are editing the file \*(lqdraft\*(rq,
  56 it will be renamed to \*(lq,draft.orig\*(rq.  This allows you to easily
  57 recover the
  58 .B mhbuild
  59 input file.
  60 .SS "Listing the Contents"
  61 The
  62 .B \-list
  63 switch tells
  64 .B mhbuild
  65 to list the table of contents associated with the MIME message that is created.
  66 .PP
  67 The
  68 .B \-headers
  69 switch indicates
  70 that a one-line banner should be displayed above the listing.  The
  71 .B \-realsize
  72 switch tells
  73 .B mhbuild
  74 to evaluate the \*(lqnative\*(rq
  75 (decoded) format of each content prior to listing.  This provides an
  76 accurate count at the expense of a small delay.  If the
  77 .B \-verbose
  78 switch
  79 is present, then the listing will show any \*(lqextra\*(rq information
  80 that is present in the message, such as comments in the
  81 \*(lqContent-Type\*(rq header.
  82 .SS "Simplified Attachment Interface"
  83 For users who wish to simply attach files to text content,
  84 .B mhbuild
  85 will scan the composition file for \*(lqAttach\*(rq headers.  An
  86 \*(lqAttach\*(rq header contains a filename that will be appended to the
  87 message using normal MIME encapsulation rules.  One filename is allowed
  88 per \*(lqAttach\*(rq header, but multiple \*(lqAttach\*(rq headers are
  89 allowed ber composition file.
  90 .PP
  91 These files will be appended after any other MIME content, including any
  92 content specified by
  93 .B mhbuild
  94 directives (see below).  See
  95 .IR send (1)
  96 for more details.
  97 .SS "Translating the Composition File"
  98 .B mhbuild
  99 is essentially a filter to aid in the composition of MIME
 100 messages.
 101 .B mhbuild
 102 will convert an
 103 .B mhbuild
 104 \*(lqcomposition file\*(rq
 105 into a valid MIME message.  A
 106 .B mhbuild
 107 \*(lqcomposition file\*(rq
 108 is just a file containing plain text that is interspersed
 109 with various
 110 .B mhbuild
 111 directives.  When this file is processed
 112 by
 113 .BR mhbuild ,
 114 the various directives will be expanded to the
 115 appropriate content, and will be encoded according to the MIME standards.
 116 The resulting MIME message can then be sent by electronic mail.
 117 .PP
 118 The formal syntax for a
 119 .B mhbuild
 120 composition file is defined at the
 121 end of this document, but the ideas behind this format are not complex.
 122 Basically, the body contains one or more contents.  A content consists of
 123 either a directive, indicated with a \*(lq#\*(rq as the first character
 124 of a line; or, plaintext (one or more lines of text).  The continuation
 125 character, \*(lq\\\*(lq, may be used to enter a single directive on more
 126 than one line, e.g.,
 127 .PP
 128 .RS 5
 129 .nf
 130 #image/png \\
 131     /home/foobar/junk/picture.png
 132 .fi
 133 .RE
 134 .PP
 135 There are five kinds of directives: \*(lqtype\*(rq directives, which
 136 name the type and subtype of the content; \*(lqexternal-type\*(rq
 137 directives, which also name the type and subtype of the content; the
 138 \*(lqmessage\*(rq directive (#forw), which is used to forward one or
 139 more messages; the \*(lqbegin\*(rq directive (#begin), which is
 140 used to create a multipart content; and the \*(lqon/off/pop\*(rq
 141 directives (#on, #off, #pop) which control whether any other
 142 directives are honored at all.
 143 .PP
 144 The
 145 .B \-directives
 146 switch allows control over whether mhbuild will honor any of the
 147 \*(lq#\*(rq-directives.  This can also be affected with the #on or
 148 #off directives, and #pop, which restores the state of processing to
 149 that preceding the most recent #on or #off.  (The #on, #off, and #pop
 150 directives are always honored, of course.) This allows inclusion of
 151 plain text which looks like mhbuild directives, without causing
 152 errors:
 153 .PP
 154 .RS 5
 155 .nf
 156 #off
 157 #include <stdio.h>
 158 printf("Hello, World!);
 159 #pop
 160 .fi
 161 .RE
 162 .PP
 163 Currently the stack depth for the #on/off/pop directives is 32.
 164 .PP
 165 The \*(lqtype\*(rq directive is used to directly specify the type and
 166 subtype of a content.  You may only specify discrete types in this manner
 167 (can't specify the types multipart or message with this directive).
 168 You may optionally specify the name of a file containing the contents
 169 in \*(lqnative\*(rq (decoded) format.  If this filename starts with the
 170 \*(lq|\*(rq character, then it represents a command to execute whose
 171 output is captured accordingly.
 172 For example,
 173 .PP
 174 .RS 5
 175 .nf
 176 #audio/basic |raw2audio -F < /usr/lib/sound/giggle.au
 177 .fi
 178 .RE
 179 .PP
 180 If a filename is not given,
 181 .B mhbuild
 182 will look for information in the
 183 user's profile to determine how the different contents should be composed.
 184 This is accomplished by consulting a composition string, and executing
 185 it under
 186 .BR /bin/sh ,
 187 with the standard output set to the content.
 188 If the
 189 .B \-verbose
 190 switch is given,
 191 .B mhbuild
 192 will echo any commands that are used to create contents in this way.
 193 .PP
 194 The composition string may contain the following escapes:
 195 .PP
 196 .RS 5
 197 .nf
 198 .ta \w'%P  'u
 199 %a      Insert parameters from directive
 200 %f      Insert filename containing content
 201 %F      %f, and stdout is not re-directed
 202 %s      Insert content subtype
 203 %%      Insert character %
 204 .fi
 205 .RE
 206 .PP
 207 First,
 208 .B mhbuild
 209 will look for an entry of the form:
 210 .PP
 211 .RS 5
 212 mhbuild-compose-<type>/<subtype>
 213 .RE
 214 .PP
 215 to determine the command to use to compose the content.  If this isn't
 216 found,
 217 .B mhbuild
 218 will look for an entry of the form:
 219 .PP
 220 .RS 5
 221 mhbuild-compose-<type>
 222 .RE
 223 .PP
 224 to determine the composition command. If this isn't found,
 225 .B mhbuild
 226 will complain.
 227 .PP
 228 An example entry might be:
 229 .PP
 230 .RS 5
 231 mhbuild-compose-audio/basic: record | raw2audio -F
 232 .RE
 233 .PP
 234 Because commands like these will vary, depending on the display
 235 environment used for login, composition strings for different
 236 contents should probably be put in the file specified by the
 237 .B $MHBUILD
 238 environment variable, instead of directly in your
 239 user profile.
 240 .PP
 241 The \*(lqexternal-type\*(rq directives are used to provide a MIME
 242 reference to a content, rather than enclosing the contents itself
 243 (for instance, by specifying an ftp site).  Hence, instead of
 244 providing a filename as with the type directives, external-parameters
 245 are supplied.  These look like regular parameters, so they must be
 246 separated accordingly.  For example,
 247 .PP
 248 .RS 5
 249 .nf
 250 #@application/octet-stream; \\
 251     type=tar; \\
 252     conversions=compress \\
 253     [this is the nmh distribution] \\
 254     {attachment; filename="nmh.tar.gz"} \\
 255     name="nmh.tar.gz"; \\
 256     directory="/pub/nmh"; \\
 257     site="ftp.math.gatech.edu"; \\
 258     access-type=anon-ftp; \\
 259     mode="image"
 260 .fi
 261 .RE
 262 .PP
 263 You must give a description string to separate the content parameters
 264 from the external-parameters (although this string may be empty).
 265 This description string is specified by enclosing it within
 266 \*(lq[]\*(rq.  A disposition string, to appear in a
 267 \*(lqContent-Disposition\*(rq header, may appear in the optional
 268 \*(lq{}\*(rq.
 269 .PP
 270 These parameters are of the form:
 271 .PP
 272 .RS 5
 273 .nf
 274 .ta \w'access-type=  'u
 275 access-type=    usually \fIanon-ftp\fR, \fImail-server\fR, or \fIurl\fR
 276 name=   filename
 277 permission=     read-only or read-write
 278 site=   hostname
 279 directory=      directoryname (optional)
 280 mode=   usually \fIascii\fR or \fIimage\fR (optional)
 281 size=   number of octets
 282 server= mailbox
 283 subject=        subject to send
 284 body=   command to send for retrieval
 285 url=    URL of content
 286 .fi
 287 .RE
 288 .PP
 289 A mimimum \*(lqexternal\-type\*(rq directive for the
 290 .B url
 291 .I access\-type
 292 would be as follows:
 293 .PP
 294 .RS 3
 295 .nf
 296 #@application/octet-stream [] access-type=url; \\
 297   url="http://download.savannah.gnu.org/releases/nmh/nmh-1.5.tar.gz"
 298 .fi
 299 .RE
 300 .PP
 301 Any long URLs will be wrapped according to RFC 2017 rules.
 302 .PP
 303 The \*(lqmessage\*(rq directive (#forw) is used to specify a message or
 304 group of messages to include.  You may optionally specify the name of
 305 the folder and which messages are to be forwarded.  If a folder is not
 306 given, it defaults to the current folder.  Similarly, if a message is not
 307 given, it defaults to the current message.  Hence, the message directive
 308 is similar to the
 309 .B forw
 310 command, except that the former uses
 311 the MIME rules for encapsulation rather than those specified in RFC 934.
 312 For example,
 313 .PP
 314 .RS 5
 315 .nf
 316 #forw +inbox 42 43 99
 317 .fi
 318 .RE
 319 .PP
 320 If you include a single message, it will be included directly as a content
 321 of type \*(lqmessage/rfc822\*(rq.  If you include more than one message,
 322 then
 323 .B mhbuild
 324 will add a content of type \*(lqmultipart/digest\*(rq
 325 and include each message as a subpart of this content.
 326 .PP
 327 If you are using this directive to include more than one message, you
 328 may use the
 329 .B \-rfc934mode
 330 switch.  This switch will indicate that
 331 .B mhbuild
 332 should attempt to utilize the MIME encapsulation rules
 333 in such a way that the \*(lqmultipart/digest\*(rq that is created
 334 is (mostly) compatible with the encapsulation specified in RFC 934.
 335 If given, then RFC 934 compliant user-agents should be able to burst the
 336 message on reception\0--\0providing that the messages being encapsulated
 337 do not contain encapsulated messages themselves.  The drawback of this
 338 approach is that the encapsulations are generated by placing an extra
 339 newline at the end of the body of each message.
 340 .PP
 341 The \*(lqbegin\*(rq directive is used to create a multipart content.
 342 When using the \*(lqbegin\*(rq directive, you must specify at least one
 343 content between the begin and end pairs.
 344 .PP
 345 .RS 5
 346 .nf
 347 #begin
 348 This will be a multipart with only one part.
 349 #end
 350 .fi
 351 .RE
 352 .PP
 353 If you use multiple directives in a composition draft,
 354 .B mhbuild
 355 will
 356 automatically encapsulate them inside a multipart content.  Therefore the
 357 \*(lqbegin\*(rq directive is only necessary if you wish to use nested
 358 multiparts, or create a multipart message containing only one part.
 359 .PP
 360 For all of these directives, the user may include a brief description
 361 of the content between the \*(lq[\*(rq character and the \*(lq]\*(rq
 362 character.  This description will be copied into the
 363 \*(lqContent-Description\*(rq header when the directive is processed.
 364 .PP
 365 .RS 5
 366 .nf
 367 #forw [important mail from Bob] +bob 1 2 3 4 5
 368 .fi
 369 .RE
 370 .PP
 371 Similarly, a disposition string may optionally be provided between
 372 \*(lq{\*(rq and \*(lq}\*(rq characters; it will be copied into the
 373 \*(lqContent-Disposition\*(rq header when the directive is processed.
 374 If a disposition string is provided that does not contain a filename
 375 parameter, and a filename is provided in the directive, it will be
 376 added to the \*(lqContent-Disposition\*(rq header.  For example, the
 377 following directive:
 378 .PP
 379 .RS 5
 380 .nf
 381 #text/plain; charset=iso-8859-1 <>{attachment} /tmp/summary.txt
 382 .fi
 383 .RE
 384 .PP
 385 creates these message part headers:
 386 .PP
 387 .RS 5
 388 .nf
 389 Content-Type: text/plain; charset="iso-8859-1"
 390 Content-Disposition: attachment; filename="summary.txt"
 391 .fi
 392 .RE
 393 .PP
 394 By default,
 395 .B mhbuild
 396 will generate a unique \*(lqContent-ID:\*(rq for each directive,
 397 corresponding to each message part; however, the user may override
 398 this by defining the ID using the \*(lq<\*(rq and \*(lq>\*(rq
 399 characters.  The
 400 .B \-nocontentid
 401 switch suppresses creation of all \*(lqContent-ID:\*(rq headers,
 402 even in the top level of the message.
 403 .PP
 404 In addition to the various directives, plaintext can be present.
 405 Plaintext is gathered, until a directive is found or the draft is
 406 exhausted, and this is made to form a text content.  If the plaintext
 407 must contain a \*(lq#\*(rq at the beginning of a line, simply double it,
 408 e.g.,
 409 .PP
 410 .RS 5
 411 ##when sent, this line will start with only one #
 412 .RE
 413 .PP
 414 If you want to end the plaintext prior to a directive, e.g., to have two
 415 plaintext contents adjacent, simply insert a line containing a single
 416 \*(lq#\*(rq character, e.g.,
 417 .PP
 418 .RS 5
 419 .nf
 420 this is the first content
 421 #
 422 and this is the second
 423 .fi
 424 .RE
 425 .PP
 426 Finally, if the plaintext starts with a line of the form:
 427 .PP
 428 .RS 5
 429 Content-Description: text
 430 .RE
 431 .PP
 432 then this will be used to describe the plaintext content.
 433 You MUST follow this line with a blank line before starting
 434 your text.
 435 .PP
 436 By default, plaintext is captured as a text/plain content.  You can
 437 override this by starting the plaintext with \*(lq#<\*(rq followed by
 438 a content-type specification.  For example, e.g.,
 439 .PP
 440 .RS 5
 441 .nf
 442 #<text/enriched
 443 this content will be tagged as text/enriched
 444 #
 445 and this content will be tagged as text/plain
 446 #
 447 #<application/x-patch [this is a patch]
 448 and this content will be tagged as application/x-patch
 449 .fi
 450 .RE
 451 .PP
 452 Note that if you use the \*(lq#<\*(rq plaintext-form, then the
 453 content-description must be on the same line which identifies the content
 454 type of the plaintext.
 455 .PP
 456 When composing a text content, you may indicate the relevant character
 457 set by adding the \*(lqcharset\*(rq parameter to the directive.
 458 .PP
 459 .RS 5
 460 #<text/plain; charset=iso-8859-5
 461 .RE
 462 .PP
 463 If a text content contains any 8\-bit characters (characters with the
 464 high bit set) and the character set is not specified as above, then
 465 .B mhbuild
 466 will assume the character set is of the type given by the
 467 standard
 468 .IR locale (1)
 469 environment variables.  If these environment variables are not
 470 set, then the character set will be labeled as \*(lqx-unknown\*(rq.
 471 .PP
 472 If a text content contains only 7\-bit characters and the character set
 473 is not specified as above, then the character set will be labeled as
 474 \*(lqus-ascii\*(rq.
 475 .PP
 476 The
 477 .B \-headerencoding
 478 switch will indicate which algorithm to use when encoding any message headers
 479 that contain 8\-bit characters.  The valid arguments are
 480 .I base64
 481 for based\-64 encoding and
 482 .I quoted
 483 for quoted\-printable encoding.  The
 484 .B \-autoheaderencoding
 485 switch will instruct
 486 .B mhbuild
 487 to automatically pick the algorithm that results in a shorter encoded string.
 488 .PP
 489 Putting this all together,
 490 here is an example of a more complicated message draft.  The
 491 following draft will expand into a multipart/mixed message
 492 containing five parts:
 493 .PP
 494 .RS 5
 495 .nf
 496 To: nobody@nowhere.org
 497 cc:
 498 Subject: Look and listen to me!
 499 --------
 500 The first part will be text/plain
 501 #<text/enriched
 502 The second part will be text/enriched
 503 #
 504 This third part will be text/plain
 505 #audio/basic [silly giggle]  \\
 506     |raw2audio -F < /usr/lib/sounds/giggle.au
 507 #image/gif   [photo of foobar] \\
 508                     /home/foobar/lib/picture.gif
 509 .fi
 510 .RE
 511 .SS "Integrity Check"
 512 If
 513 .B mhbuild
 514 is given the
 515 .B \-check
 516 switch, then it will also associate an integrity check with each
 517 \*(lqleaf\*(rq content.  This will add a Content-MD5 header field to
 518 the content, along with the md5 sum of the unencoded contents, per RFC
 519 1864.  This may be used by the receiver of the message to verify that
 520 the contents of the message were not changed in transport.
 521 .SS "Transfer Encodings"
 522 After
 523 .B mhbuild
 524 constructs the new MIME message by parsing directives,
 525 including files, etc., it scans the contents of the message to determine
 526 which transfer encoding to use.  It will check for 8bit data, long lines,
 527 spaces at the end of lines, and clashes with multipart boundaries.  It will
 528 then choose a transfer encoding appropriate for each content type.
 529 .PP
 530 If an integrity check is being associated with each content by using
 531 the
 532 .B \-check
 533 switch, then
 534 .B mhbuild
 535 will encode each content with
 536 a transfer encoding, even it the content contains only 7\-bit data.  This
 537 is to increase the likelihood that the content is not changed while in
 538 transport.
 539 .SS "Invoking mhbuild"
 540 Typically,
 541 .B mhbuild
 542 is invoked by the
 543 .B whatnow
 544 program.  This
 545 command will expect the body of the draft to be formatted as an
 546 .B mhbuild
 547 composition file.  Once you have composed this input file
 548 using a command such as
 549 .BR comp ,
 550 .BR repl ,
 551 or
 552 .BR forw ,
 553 you invoke
 554 .B mhbuild
 555 at the \*(lqWhat now\*(rq prompt with
 556 .PP
 557 .RS 5
 558 What now? mime
 559 .RE
 560 .PP
 561 prior to sending the draft.  This will cause
 562 .B whatnow
 563 to execute
 564 .B mhbuild
 565 to translate the composition file into MIME format.
 566 .PP
 567 Normally it is an error to invoke
 568 .B mhbuild
 569 on file that already in MIME format.  The
 570 .B \-auto
 571 switch will cause
 572 .B mhbuild
 573 to exit without error if the input file already has valid MIME headers.
 574 The use of
 575 .B \-auto
 576 also enables the
 577 .B \-nodirectives
 578 switch.
 579 .PP
 580 Finally, you should consider adding this line to your profile:
 581 .PP
 582 .RS 5
 583 lproc: show
 584 .RE
 585 .PP
 586 This way, if you decide to
 587 .B list
 588 after invoking
 589 .BR mime ,
 590 the command
 591 .PP
 592 .RS 5
 593 What now? list
 594 .RE
 595 .PP
 596 will work as you expect.
 597 .PP
 598 The
 599 .B \-dist
 600 switch is intended to be used by
 601 .BR dist .
 602 It will cause mhbuild to not generate any MIME headers in the composition
 603 file (such as \*(lqMIME-Version\*(rq or \*(lqContent-Type\*(rq), but it
 604 will still encode message headers according to RFC 2047.
 605 .SS "User Environment"
 606 Because the environment in which
 607 .B mhbuild
 608 operates may vary for a
 609 user,
 610 .B mhbuild
 611 will look for the environment variable
 612 .BR $MHBUILD .
 613 If present, this specifies the name of an additional user profile which
 614 should be read.  Hence, when a user logs in on a particular machine,
 615 this environment variable should be set to refer to a file containing
 616 definitions useful for that machine.
 617 .PP
 618 Finally,
 619 .B mhbuild
 620 will attempt to consult a global
 621 .B mhbuild
 622 user profile, e.g.,
 623 .PP
 624 .RS 5
 625 %etcdir%/mhn.defaults
 626 .RE
 627 .PP
 628 if it exists.
 629 .SS "Syntax of Composition Files"
 630 The following is the formal syntax of a
 631 .B mhbuild
 632 \*(lqcomposition file\*(rq.
 633 .PP
 634 .RS 5
 635 .nf
 636 body         ::=     1*(content | EOL)
 637
 638 content      ::=     directive | plaintext
 639
 640 directive    ::=     "#" type "/" subtype
 641                          0*(";" attribute "=" value)
 642                          [ "(" comment ")" ]
 643                          [ "<" id ">" ]
 644                          [ "[" description "]" ]
 645                          [ "{" disposition "}" ]
 646                          [ filename ]
 647                          EOL
 648
 649                    | "#@" type "/" subtype
 650                          0*(";" attribute "=" value)
 651                          [ "(" comment ")" ]
 652                          [ "<" id ">" ]
 653                          [ "[" description "]" ]
 654                          [ "{" disposition "}" ]
 655                          external-parameters
 656                          EOL
 657
 658                    | "#forw"
 659                          [ "<" id ">" ]
 660                          [ "[" description "]" ]
 661                          [ "{" disposition "}" ]
 662                          [ "+"folder ] [ 0*msg ]
 663                          EOL
 664
 665                    | "#begin"
 666                            [ "<" id ">" ]
 667                            [ "[" description "]" ]
 668                            [ "{" disposition "}" ]
 669                            [   "alternative"
 670                              | "parallel"
 671                              | something-else    ]
 672                            EOL
 673                          1*body
 674                      "#end" EOL
 675
 676 plaintext    ::=     [ "Content-Description:"
 677                            description EOL EOL ]
 678                          1*line
 679                      [ "#" EOL ]
 680
 681                    | "#<" type "/" subtype
 682                          0*(";" attribute "=" value)
 683                          [ "(" comment ")" ]
 684                          [ "[" description "]" ]
 685                          [ "{" disposition "}" ]
 686                          EOL
 687                          1*line
 688                      [ "#" EOL ]
 689
 690 line         ::=     "##" text EOL
 691                      -- interpreted as "#"text EOL
 692                    | text EOL
 693 .fi
 694 .RE
 695 .SH FILES
 696 .B mhbuild
 697 looks for additional user profile files and mhn.defaults in multiple
 698 locations: absolute pathnames are accessed directly, tilde expansion
 699 is done on usernames, and files are searched for in the user's
 700 .I Mail
 701 directory as specified in their profile.  If not found there, the directory
 702 .RI \*(lq %etcdir% \*(rq
 703 is checked.
 704 .PP
 705 .fc ^ ~
 706 .nf
 707 .ta \w'%etcdir%/ExtraBigFileName  'u
 708 ^$HOME/\&.mh\(ruprofile~^The user profile
 709 ^$MHBUILD~^Additional profile entries
 710 ^%etcdir%/mhn.defaults~^System default MIME profile entries
 711 .fi
 712 .SH "PROFILE COMPONENTS"
 713 .fc ^ ~
 714 .nf
 715 .ta 2.4i
 716 .ta \w'ExtraBigProfileName  'u
 717 ^Path:~^To determine the user's nmh directory
 718 ^Current\-Folder:~^To find the default current folder
 719 ^mhbuild-compose-<type>*~^Template for composing contents
 720 .fi
 721 .SH "SEE ALSO"
 722 .IR mhlist (1),
 723 .IR mhshow (1),
 724 .IR mhstore (1)
 725 .PP
 726 .I "Proposed Standard for Message Encapsulation"
 727 (RFC 934),
 728 .PP
 729 .I "The Content-MD5 Header Field"
 730 (RFC 1864),
 731 .PP
 732 .I "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"
 733 (RFC 2045),
 734 .PP
 735 .I "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"
 736 (RFC 2046),
 737 .PP
 738 .I "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text"
 739 (RFC 2047),
 740 .PP
 741 .I "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"
 742 (RFC 2048),
 743 .PP
 744 .I "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples"
 745 (RFC 2049)
 746 .I "Definition of the URL MIME External-Body Access-Type"
 747 (RFC 2017)
 748 .SH DEFAULTS
 749 .nf
 750 .RB ` \-headers '
 751 .RB ` \-realsize '
 752 .RB ` \-norfc934mode '
 753 .RB ` \-contentid '
 754 .RB ` \-nocheck '
 755 .RB ` \-noverbose '
 756 .RB ` \-autoheaderencoding '
 757 .fi