.\"
.\" THIS FILE HAS BEEN AUTOMATICALLY GENERATED.  DO NOT EDIT.
.\"
.TH BURST 1mh "2019-01-06" MH.6.8 [mmh-0.4]
.SH NAME
burst \- explode digests into messages
.SH SYNOPSIS
.HP 5
.na
.B burst
.RI [ +folder ]
.RI [ msgs ]
.RB [ \-verbose " | " \-noverbose ]
.RB [ \-Version ]
.RB [ \-help ]
.ad
.SH DESCRIPTION
.B Burst
considers the specified messages in the named folder to be
Internet digests, and explodes them in that folder.
.PP
The messages contained within the digest are placed at the end of the folder.
The digest is preserved.
No other messages are tampered with in any way.
.PP
The
.B \-verbose
switch directs
.B burst
to tell the user the general
actions that it is taking to explode the digest.
.PP
It turns out that
.B burst
works equally well on forwarded messages
and blind\-carbon\-copies as on Internet digests, provided that they
use RFC 934 message encapsulation.
.PP
To extract messages encapsulated with MIME, use
.BR mhstore (1).

.SH FILES
.fc ^ ~
.nf
.ta \w'/etc/mmh/ExtraBigFileName  'u
^$HOME/.mmh/profile~^The user profile
.fi

.SH "PROFILE COMPONENTS"
.fc ^ ~
.nf
.ta 2.4i
.ta \w'ExtraBigProfileName  'u
^Path:~^To determine the user's mail storage
^Current\-Folder:~^To find the default current folder
^Msg\-Protect:~^To set mode when creating a new message
.fi

.SH "SEE ALSO"
mhstore(1),
.I "Proposed Standard for Message Encapsulation"
(RFC\-934)

.SH DEFAULTS
.nf
.RB ` +folder "' defaults to the current folder"
.RB ` msgs "' defaults to the current message"
.RB ` \-noverbose '
.fi

.SH CONTEXT
If a folder is given, it will become the current folder.
The first message extracted from the
first digest burst becomes the current message.

.SH BUGS
The
.B burst
program enforces a limit on the number of messages which
may be
.B burst
from a single message.  This number is on the order
of 1000 messages.  There is usually no limit on the number of messages
which may reside in the folder after the
.BR burst ing.
.PP
Although
.B burst
uses a sophisticated algorithm to determine where
one encapsulated message ends and another begins, not all digestifying
programs use an encapsulation algorithm.  In degenerate cases, this
usually results in
.B burst
finding an encapsulation boundary
prematurely and splitting a single encapsulated message into two or
more messages.  These erroneous digestifying programs should be fixed.
.PP
Any text which appears after the last encapsulated message
is not placed in a separate message by
.BR burst .
In the case of
digestified messages, this text is usually an `End of digest'
string.