Files
jcoffey-dev d1e48baf90 Import upstream v1.0.0, stripped
Upstream commit: 47df4c0baeb8
Enterprise-only files removed or emptied: 68
Enterprise-only snippets removed: 2080 in 147 files
Dangling module declarations removed: 533
Edits turning enterprise off: 12
Third-party code: 25 files, 14 not in THIRD-PARTY.md
Renamed identifiers: 51 in 11 files
Verification: clean

The last upstream import. 1.0 has a new store layout that can't open a
0.16 store, renumbers the settings schema, ties the store's schema
version to the edition, and moves calcard, smtp-proto, jmap-tools and
sieve in-tree (AGPL-3.0-only OR LicenseRef-SEL; taken under the AGPL).
The tests/ directory is gone upstream; main keeps its own. The build
check is clean, and three files on the known list now compile:
tests/src/directory/issuer.rs, tests/src/directory/mod.rs and
tests/src/smtp/inbound/antispam.rs. The 14 new third-party files are
the in-tree calcard, jmap-tools, smtp-proto and smtp-report code.
2026-10-27 06:09:18 -07:00

74 lines
1.8 KiB
Plaintext

MIME-Version: 1.0
From: Nathaniel Borenstein <[email protected]>
To: Ned Freed <[email protected]>
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT)
Subject: A multipart example
Content-Type: multipart/mixed;
boundary=unique-boundary-1
This is the preamble area of a multipart message.
Mail readers that understand multipart format
should ignore this preamble.
If you are reading this text, you might want to
consider changing to a mail reader that understands
how to properly display multipart messages.
--unique-boundary-1
... Some text appears here ...
[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]
--unique-boundary-1
Content-type: text/plain; charset=US-ASCII
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.
--unique-boundary-1
Content-Type: multipart/parallel; boundary=unique-boundary-2
--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64
... base64-encoded 8000 Hz single-channel
mu-law-format audio data goes here ...
--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
... base64-encoded image data goes here ...
--unique-boundary-2--
--unique-boundary-1
Content-type: text/enriched
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>
Isn't it
<bigger><bigger>cool?</bigger></bigger>
--unique-boundary-1
Content-Type: message/rfc822
From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable
... Additional text in ISO-8859-1 goes here ...
--unique-boundary-1--