Resending temp files

When the user edits message contents before doing a resend, the new message is saved to a temp file. This is used in the resend command.

If multiple messages are being resent, then the metadata temp file consists of many lists.

If necessary, then you can edit metadata and message content before doing a resend.

The edited metadata is stored in a separate temporary file. This file’s format is based on the index file format, with two differences:

  • It has no requirement to be of fixed length. SEPCHARS, DRIVERCTL, and USERDATA contains the actual variable-length contents of those fields from the .msg file instead of length values.
  • Many fields that are stored in SMAT are not required in the temp file and are omitted. They include the fields for context, type, and priority. These are specified as arguments to the resend command and many fields that are rewritten by the engine.

See Using resend and Using resend_errordb and hcidbdump.