Tool guideEmail Tools

MIME Report Inspector – Guide to Email Structure, Attachments and Report Formats

How MIME messages are built, how to read multipart/report structures from ARF, AFRF, APRF and DMARC reports, and how the NetTools.tech MIME Report Inspector decodes them in your browser.

By NetTools.tech · · 4 min read

Every email report — a spam complaint, a DMARC failure report, an APRF performance report, a bounce — is a MIME message: parts inside parts, each with its own type, encoding and headers. When a report does not parse, or you need the attachment inside it, you have to see that structure.

The MIME Report Inspector shows the complete MIME tree of any email in your browser, decodes each part on request, and detects known report formats with the evidence behind each detection.

What is MIME?

In simple terms

MIME is how one email carries several things at once: a text part, an HTML version, attachments, even other emails. Each part has a type (text/plain, application/json, message/rfc822) and is encoded so it survives transport.

Technical background

RFC 2045 defines Content-Type, Content-Transfer-Encoding (7bit, 8bit, binary, base64, quoted-printable) and parameters; RFC 2046 defines multipart types separated by boundary lines and message/rfc822 for embedded messages; RFC 2047 and RFC 2231 encode non-ASCII header values and file names. Email reports use multipart/report (RFC 6522) with a report-type parameter such as feedback-report or delivery-status.

Why use a MIME report inspector?

Mail clients hide the structure. The inspector shows where a report's machine-readable part is, whether boundaries close, which encoding a part uses and whether it decodes, so you can find out why a report processor fails — or simply get at the attachment. Because it reports defects instead of quietly repairing them, it also shows what a stricter parser on the receiving side would stumble over.

Who should use it?

Postmasters and abuse desks handling reports, developers writing report parsers, security analysts examining suspicious messages, and anyone who needs to extract an attachment from a raw .eml.

How the MIME report inspector works

Your browser parses the message into a tree: header blocks are unfolded, multipart bodies split at their boundaries, embedded messages expanded. Problems — a missing closing boundary, an unknown encoding, invalid base64, 8-bit data in a 7bit part — are reported rather than silently fixed. Parts are decoded on request; gzip attachments are decompressed locally with a size cap. Detection looks for feedback report parts, APRF JSON and DMARC XML, and hands detected reports to the ARF Report Analyzer, AFRF Analyzer or APRF Analyzer.

How to use the NetTools.tech MIME Report Inspector

  1. Save the email as .eml or copy its full source.
  2. Open the MIME Report Inspector, paste or drop it, or load the example.
  3. Click Inspect MIME Message.
  4. Review the detected format, then click parts in the tree to see headers, decoding status and content.
  5. Download decoded attachments, open the report in its analyzer, or export the structure.

Understanding the results

The detection box names the format with high, medium or low confidence and the evidence used. The tree shows each part's number, type, encoding, file name and size; a warning marker flags parts with problems. The detail panel lists Content-Type parameters, disposition, encoding, charset, Content-ID, encoded and decoded size, and whether decoding succeeded, followed by a preview for text, JSON and XML.

Example: an APRF report inside a multipart/report

The example message is a multipart/report with report-type=aprf: a multipart/alternative with text and HTML parts, and a base64 application/gzip attachment. The inspector detects an APRF report with high confidence because the decompressed attachment is JSON with header, body and dkim_domain. The HTML part is shown as source — its script and onclick handler are never run.

Common use cases

  • Finding out why a report parser rejects a message.
  • Extracting and decompressing report attachments.
  • Checking boundaries and encodings of generated reports.
  • Identifying an unknown report email.
  • Examining suspicious messages without opening attachments.

Troubleshooting

"Boundary never occurs in the body"

The boundary parameter does not match the delimiter lines, often after copying through a client that rewrapped lines.

"Closing boundary is missing"

The message was truncated; the last part runs to the end.

Base64 "not valid"

The attachment is corrupt or was altered. The decoded bytes may be incomplete.

ZIP attachment not previewed

ZIP archives are not unpacked; download and open them locally.

Common mistakes

  • Copying the visible message instead of the raw source.
  • Assuming every multipart/report is a spam complaint.
  • Opening unknown attachments directly instead of inspecting them.
  • Rendering HTML from untrusted mail in a normal browser tab.
  • Ignoring decoding warnings when a parser fails.

Limitations

Inputs are limited to 10 MB, nesting to 16 levels and 500 parts. ZIP archives are not unpacked. TNEF (winmail.dat) and S/MIME or PGP-encrypted content are shown as binary parts. Detection covers the listed report formats only.

Security & privacy

Messages are processed in your browser and never uploaded or stored. Attachments are decoded but never executed; HTML previews run sandboxed without scripts and with all remote content blocked. Exports contain the structure only, not part contents.

Summary

Every email report is a MIME tree. The NetTools.tech MIME Report Inspector shows that tree exactly as it is, decodes parts safely in your browser, and tells you which report you are looking at — and why.

Frequently asked questions

Is my email uploaded?

No. Parsing, decoding and decompression all run in your browser. Nothing is sent to NetTools or stored.

Is it safe to inspect a suspicious email?

Attachments are decoded but never opened or executed, and HTML is shown as source. The optional HTML preview runs in a sandboxed frame without scripts, forms or remote images.

How does it decide which report format a message is?

From real evidence: MIME types, the report-type parameter, feedback report fields and the content of JSON or XML attachments. Every detection lists its evidence and confidence.

Why is my multipart/report not called ARF?

ARF needs a message/feedback-report part. Bounces (delivery-status) and read receipts are also multipart/report, and are named as such.

Can it open ZIP attachments?

No. ZIP files, common for DMARC aggregate reports, are recognised by name but not unpacked. Gzip attachments are decompressed locally.

What limits apply?

10 MB input, 16 nesting levels, 500 parts and 20 MB after gzip decompression, so malformed or hostile messages cannot freeze your browser.