burst − explode digests into messages
|
burst |
[+folder] [msgs] [−verbose | −noverbose] [−Version] [−help] |
Burst considers the specified messages in the named folder to be Internet digests, and explodes them in that folder.
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.
The −verbose switch directs burst to tell the user the general actions that it is taking to explode the digest.
It turns out that burst works equally well on forwarded messages and blind−carbon−copies as on Internet digests, provided that they use RFC 934 message encapsulation.
To extract messages encapsulated with MIME, use mhstore(1).
$HOME/.mmh/profile The user profile
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
mhstore(1), Proposed Standard for Message Encapsulation (RFC−934)
‘+folder’
defaults to the current folder
‘msgs’ defaults to the current message
‘−noverbose’
If a folder is given, it will become the current folder. The first message extracted from the first digest burst becomes the current message.
The burst program enforces a limit on the number of messages which may be 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 bursting.
Although 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 burst finding an encapsulation boundary prematurely and splitting a single encapsulated message into two or more messages. These erroneous digestifying programs should be fixed.
Any text which appears after the last encapsulated message is not placed in a separate message by burst. In the case of digestified messages, this text is usually an ‘End of digest’ string.