MachineTradecraft
Global site search

Search guides, labs, glossary, and research

Type two or more characters to search.

Start with a channel, artifact, or defense term

Examples include zero-width, metadata, tokenizer, or prompt injection.
    Messages & Calendars · Representation and automatic-action conflict

    Inert MIME and Calendar Inspector

    The inspector treats authentication fields as claims, disables remote resolution, and never opens an attachment or populates a calendar.

    Browse all labs Open universal Machine View
    Quick answer

    What does the MIME & Calendar Inspector show?

    The inspector treats authentication fields as claims, disables remote resolution, and never opens an attachment or populates a calendar.

    Human visibility
    Nested message structure and calendar actions
    Machine receiver
    Offline structural parser
    Robustness
    Format and gateway dependent

    Research boundary: this page uses bounded, inert data and fixed safe examples. It never executes decoded content, requests secrets, calls third-party services, or performs actions against external systems.

    FIRST RUN / THREE STEPS

    Start with the prepared, bounded workflow.

    Nothing runs automatically
    1. Review the prepared starter input

      A bounded benign input is already present. Change it only when you are ready to test a different authorized artifact.

    2. Run Inspect message or calendar

      Run the normal first-pass analysis for the prepared values above.

    3. Scan before expanding

      Read the summary first, then scan findings and expand only the machine views you need.

    INPUT / CONTROL PLANE

    Prepare the input and choose one action.

    Ready

    The recommended first run is separated from alternate analyses. Inputs and selected files stay on this host.

    Current input state Prepared starter input loaded

    The form is prefilled with a bounded safe starting point. Nothing runs until you choose an action.

    346 / 32,000 bytes

    Maximum 32,000 UTF-8 bytes. Remote URLs, DNS, attachments, and calendar actions are never opened.

    Maximum: 32,000 UTF-8 bytes.

    Switch prepared example5 options

    Loading a sample changes only the form values. Review the result and run an action yourself.

    Prepared benign examples
    ACTION HIERARCHY

    Run the recommended first pass.

    Alternate actions remain available below, but the first pass is the clearest place to start.

    Inputs remain on this host. Text operations are size-limited; uploaded files are processed from PHP’s temporary upload and are not retained by the application.

    OUTPUT / MACHINE VIEWS

    Scan the result from summary to evidence.

    Run Inspect message or calendar to create the first result.

    The prepared starter input is ready. The output will lead with a summary and visible qualifications before the expandable machine views.

    SummaryFindingsMachine views
    Interpretation framework

    The same artifact can produce several valid observations.

    01

    Human view

    What a person naturally reads, sees, or hears.

    02

    Structural view

    What a parser, DOM, container reader, or metadata extractor exposes.

    03

    Decoder view

    What becomes meaningful only with a rule, key, tokenizer, model, or tool.

    04

    Defensive view

    What normalization, rendering, OCR, canonicalization, or policy changes.

    Evidence and decision boundary

    Use the result as bounded evidence, not as a universal verdict.

    The inspector treats authentication fields as claims, disables remote resolution, and never opens an attachment or populates a calendar.

    LOCAL MODEBounded inert message and calendar syntax mapper
    REVIEW DATE2026-08-26
    SOURCE BODYPreserved separately from implementation claims
    Computed locally

    Deterministic output produced by this bounded runtime.

    • Exact source bytes, unfolded selected RFC 5322-style headers, repeated header instances, MIME boundary declarations, HTTP(S) URL strings, and selected iCalendar properties
    • Presence of authentication-related header claims without treating them as verified
    • No mail, RSVP, DNS, URL, attachment, or remote-image action is performed
    Bounded approximation

    Useful subset or model that does not establish full conformance.

    • Header and MIME parsing cover a bounded subset rather than full RFC grammar and recovery behavior
    • The parser does not fully decode every MIME nesting, character set, transfer encoding, address form, recurrence, or timezone rule
    • Client rendering and automatic calendar behavior are not reproduced
    Escalate for

    Claims that require an exact parser, trust system, model, or human review.

    • DKIM, SPF, DMARC, and ARC require message canonicalization, DNS, cryptography, alignment, trust, and policy evaluation
    • Attachment safety requires format-specific inspection
    • Calendar workflows must be tested in the exact client with explicit human-confirmation policy
    Interpretation rule

    Record the receiver and transformation.

    Machine-decodable is receiver-relative. Record the parser, preprocessing, codebook, tokenizer, key, model, and transformation path before generalizing from one result.

    Limitations

    What this page does not prove

    Offline syntax inspection cannot verify DKIM, SPF, DMARC, ARC, sender reputation, DNS policy, attachment safety, or calendar-client behavior.

    Deterministic review material

    Download the exact benign fixtures used for the evidence boundary.

    These local files are supplied for repeatable inspection. The application does not fetch them automatically, execute their content, or treat a fixture result as external verification.

    Multipart message

    Exercises header unfolding, syntax-only authentication claims, multipart/alternative mapping, body comparison, and non-fetching URL inventory.

    Type
    EML fixture
    Bytes
    522
    SHA-256
    a87def6400630b29939c…
    Download fixture
    Calendar request

    Exercises bounded iCalendar property extraction without adding an event, sending an RSVP, resolving a time zone, or executing an alarm.

    Type
    ICS fixture
    Bytes
    478
    SHA-256
    52bf94a62f67084a5621…
    Download fixture

    Download the complete evidence-review fixture pack · SHA-256 sidecar included beside the archive

    Continue the investigation

    Related labs and source reports

    Email, MIME, Calendar, and Collaboration Metadata as Machine-Readable Channels Research report Indirect Prompt Injection, Retrieval Poisoning, and Agent Trust Boundaries Research report
    Continue exploring

    Move from the current explanation to a related guide, evidence source, or controlled workbench.

    Laboratory catalogChoose a focused local experimentBrowse 40 bounded laboratories spanning representation, files, messages, models, provenance, agents, supply chains, and defense.Open this path Field guideDefine Machine Tradecraft preciselyUse the formal model, classification test, taxonomy, and limits before generalizing from one artifact.Open this path Defensive architectureBuild a safer model-ingestion boundaryPreserve evidence, compare representations, canonicalize allowlisted fields, retain provenance, and minimize privilege.Open this path