mailbourne-core 0.0.1

The vocabulary of mailbourne: addresses, envelopes, messages, events, config
Documentation
  • Coverage
  • 100%
    41 out of 41 items documented1 out of 12 items with examples
  • Size
  • Source code size: 10.2 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 662.02 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 3s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • mailbourne/mailbourne
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • insanalamin

mailbourne-core — the vocabulary

Start here. These are the nouns of email that every other crate shares.

The single most important idea in this crate — and in all of email — is the difference between the envelope and the message:

  • The [envelope::Envelope] is what the servers read: who to bounce to (MAIL FROM) and where to deliver (RCPT TO). Like the outside of a paper envelope, it is thrown away after delivery.
  • The [message::Message] is the letter inside: the headers your mail client shows (From:, Subject:) and the body. The receiving server has no obligation to make it match the envelope — that mismatch is how BCC works, and policing it is what SPF/DKIM/DMARC are for.

Reading order: [address] → [envelope] → [message] → [event] → [config].