infrastructure-mail-extract

Per-sender-family structured field extraction (regex-based body parsing) over foundation-mail-message::Email

What it is for

# infrastructure-mail-extract

Per-sender-family structured body field extraction over foundation_mail_message::Email — "this message is a PayPal transaction receipt, and here's the amount/fee/transaction id it contains," not generic MIME parsing (that's Email/MessagePart themselves, crate 1) and not header-based classification (that's infrastructure-mail-headers, crate 6).

Refactored, not ported, from rust-gmail-manager/src/parsing/{service, families/paypal}.rs (Gate 4.5 provenance — see CHANGELOG.md). The source's EmailParser trait took a decomposed (sender, subject, body, date) bag of &str/Option<DateTime> params read from Postgres columns; this crate's FamilyParser trait reads an Email directly — same refactor direction as crate 6, applied to body extraction instead of header classification.

Scope: PayPal only, for now

mm's parsing/families/ has three parsers (paypal.rs, uber.rs, cointracker.rs). The sprint doc's crate 7 source line names only families/paypal.rs, so only families::paypal::PayPalParser is lifted here — see families/mod.rs and CHANGELOG.md for the explicit non-goal note on the other two.

Layer note: no cargo dependency on infrastructure-mail-headers

The sprint doc's crate table lists crate 7's "Depends on" column as mail-headers (crate 6). This crate does not actually Cargo.toml-depend on infrastructure-mail-headers: both crates are infrastructure layer, and tools-xtask check-deps's allowed_deps only permits a non-tools library crate to depend on foundation — crate 6 itself only depends on foundation-mail-message for the same reason. Functionally there is no need for the dependency either: PayPalParser::matches_sender reads email.from directly (a substring check, same as the source), never infrastructure_mail_headers::classify's MailClass or from_address::ParsedFrom output. See docs/architecture/layers.toml's entry for this crate for the same note.

Gate 1.5.6 — input limits

Email bodies originate from arbitrary inbound mail (attacker-reachable content). limits::capped_body truncates to limits::MAX_BODY_BYTES before any family parser's regex runs — see that module's doc comment.

Capabilities

Extraction

Run a set of family parsers against one Email and collect the matches.

ExtractionOutcome

Run a set of family parsers against one Email and collect the matches.

PayPalParser

PayPal transaction-email parser.

limits (other)

Gate 1.5.6 input-limit compliance: every family parser in this crate reads

registry (other)

Default family-parser registry.

FamilyParser

Extraction result type and the per-sender-family parser trait.

ParseResult

Extraction result type and the per-sender-family parser trait.

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

infrastructure_mail_extract

• extract
• families
• families::paypal
• limits
• registry
• types

flowchart TD
  n_infrastructure_mail_extract["infrastructure_mail_extract"]
  n_infrastructure_mail_extract --> n_extract["extract"]
  n_infrastructure_mail_extract --> n_families["families"]
  n_families --> n_families__paypal["paypal"]
  n_infrastructure_mail_extract --> n_limits["limits"]
  n_infrastructure_mail_extract --> n_registry["registry"]
  n_infrastructure_mail_extract --> n_types["types"]

Public surface

`extract`

`families::paypal`

`limits`

`registry`

`types`

Re-exports. Exported here, defined elsewhere.

Boundary

Reaches into foundation.

Shares tier infrastructure with 82 other crates: infrastructure-acquire, infrastructure-adapters-google-calendar, infrastructure-adapters-google-gmail, infrastructure-adapters-google-places, infrastructure-adapters-google-trends, infrastructure-adapters-shodan, infrastructure-adapters-yelp, infrastructure-agent, … (82 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier flow. Which tiers this crate's own edges cross.

flowchart LR
  n_infrastructure["infrastructure"] --> n_foundation["foundation"]

Dependencies

Runtime, in this workspace.

Runtime, from outside the workspace.

Development. None.

Build. None.

Depended on by. Nothing in this workspace.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  SELF["infrastructure-mail-extract"]
  SELF -->|runtime| n_foundation_mail_message["foundation-mail-message"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

No environment variable is read with a literal name anywhere in this crate. A variable whose key is computed at run time cannot be listed here, and is not claimed to be absent.

Related capabilities

No workspace crate depends on this one.

Verification

Evidence by module. How often each public module is named by something executable.

What the tests establish, by name:

• empty_registry_yields_no_extractions — src/extract.rs
• extract_is_pure_and_order_matches_registry_order — src/extract.rs
• matching_sender_with_parseable_body_yields_a_parsed_extraction — src/extract.rs
• matching_sender_with_unparseable_body_yields_no_match_not_silence — src/extract.rs
• no_parser_matches_an_unrelated_sender — src/extract.rs
• matches_sender_is_case_insensitive — src/families/paypal.rs
• parse_ignores_bytes_past_the_body_cap — src/families/paypal.rs
• parse_reads_transaction_id_and_fee — src/families/paypal.rs
• parse_returns_none_when_body_has_no_total — src/families/paypal.rs
• parse_threads_the_email_date_into_occurred_at — src/families/paypal.rs
• test_detect_refund — src/families/paypal.rs
• test_matches_paypal — src/families/paypal.rs
• test_parse_paypal_payment — src/families/paypal.rs
• body_over_cap_is_truncated_to_max_bytes — src/limits.rs
• no_text_part_yields_empty_body — src/limits.rs
• short_body_passes_through_unchanged — src/limits.rs
• truncation_does_not_split_a_multibyte_char — src/limits.rs
• default_parsers_has_exactly_one_family_for_now — src/registry.rs
• default_parsers_includes_paypal — src/registry.rs

Documentation coverage

pie showData
    title Public items with rustdoc
    "Documented" : 8
    "No rustdoc detected" : 4

Metrics

pie showData
    title Public API by kind
    "constant" : 1
    "enum" : 1
    "function" : 3
    "method" : 3
    "struct" : 3
    "trait" : 1

pie showData
    title Rust source composition
    "Code" : 390
    "Blank or comment" : 241

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.