# US 2012/0259936 A1 · Document object model api for mime

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0259936 A1
- Document ID: US20120259936A1
- Status: Published application
- Kind: A1
- Application number: 13/526,790
- Filed: 2012-06-19
- Published: 2012-10-11
- Earliest claimed: 2005-12-06
- Assignees: Microsoft Corporation
- Inventors: Roy Williams; Yuri Inglikov; Oleg V. Ouliankine; Nelly Porter; Loren Curtis
- Web page: https://patentgrep.com/patent/US20120259936A1

## CPC

- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- H04L 51/066: Format adaptation, e.g. format conversion or compression
- H04L 51/23: Reliability checks, e.g. acknowledgments or fault reporting
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 69/22: Parsing or analysis of headers
- H04L 51/212: using filtering or selective blocking
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The claimed subject matter provides systems and/or methods that facilitate interpreting Multipurpose Internet Mail Extensions (MIME) data. An interface can obtain MIME data. For instance, a stream of MIME data can be obtained, MIME data can be loaded from a static file, etc. Moreover, any disparate type of RFC 822 data can additionally or alternatively be received by the interface. Also, a MIME reader can analyze the MIME data (and/or normalized RFC 822 data) to interpret encoded structural information and generate at least one primitive based on the encoded structural information. Further, a hierarchical model can be built utilizing the at least one primitive.

## Claims

### Claim 1

A system that facilitates interpreting Multipurpose Internet Mail Extensions (MIME) data, comprising:
an interface that obtains MIME data; and
a MIME reader that analyzes the MIME data to interpret encoded structural information and generates at least one primitive based on the encoded structural information.

### Claim 2 (depends on 1)

The system of claim 1, the MIME reader further comprises a streaming data component that analyzes the MIME data as the MIME data is streamed to the MIME reader via the interface.

### Claim 3 (depends on 1)

The system of claim 1, the MIME reader further comprises a static data component that obtains a static file that comprises the MIME data and subsequently analyzes the MIME data.

### Claim 4 (depends on 1)

The system of claim 1, the MIME reader concurrently yields primitives associated with multiple documents.

### Claim 5 (depends on 1)

The system of claim 1, further comprising a hierarchical model generator that utilizes the at least one primitive generated via the MIME reader to build a hierarchical model of the MIME data.

### Claim 6 (depends on 5)

The system of claim 5, the hierarchical model generator utilizes a library written in managed code.

### Claim 7 (depends on 5)

The system of claim 5, the hierarchical model of the MIME data includes extensible objects.

### Claim 8 (depends on 1)

The system of claim 1, further comprising a normalization component that interprets and converts RFC 822 data obtained via the interface with a differing format into a normalized MIME form.

### Claim 9 (depends on 1)

The system of claim 1, further comprising a MIME writer that generates MIME data from the at least one primitive.

### Claim 10 (depends on 1)

The system of claim 1, further comprising a conversion component that converts the obtained MIME data into Unicode.

### Claim 11 (depends on 1)

The system of claim 1, further comprising a data correction component that offers a logical interpretation of malformed MIME data.

### Claim 12 (depends on 1)

The system of claim 1, the data correction component further refrains from altering the malformed MIME data upon identify the MIME data as being digitally signed content.

### Claim 13 (depends on 1)

The system of claim 1, further comprising a streaming evaluation component that controls at least one of a strictness/completeness of the MIME data; a maximum number of nested parts allowed; a maximum size of the MIME data; a maximum number of bytes allowed in a header; a maximum number of distinct parts; a maximum number of headers; a maximum number of addressing headers; a maximum number of bytes in one header; and a maximum number of parameter fields on any supported structured header.

### Claim 14 (depends on 1)

The system of claim 1, further comprising a state accumulation component that detects at least one of a missing multipart MIME boundary; an invalid boundary value; an invalid line wrapping; an incorrect line termination; an invalid header; a missing separator after a group of headers; a missing boundary parameter; an undefined transfer encoding; and an invalid external link.

### Claim 15

A method that facilitates interpreting Multipurpose Internet Mail Extensions (MIME) data, comprising:
receiving MIME data;
identifying structural information encoded in the MIME data; and
generating primitive(s) based on the encoded structural information as the MIME data is analyzed.

### Claim 16 (depends on 15)

The method of claim 15, further comprising producing a hierarchical model of the MIME data based on the encoded structural information.

### Claim 17 (depends on 16)

The method of claim 16, further comprising at least one of accessing and manipulating the hierarchical model based at least in part upon a document object model.

### Claim 18 (depends on 15)

The method of claim 15, further comprising identifying structural information by at least one of analyzing a stream of the MIME data and loading a static file comprising the MIME data.

### Claim 19 (depends on 15)

The method of claim 15, further comprising:
obtaining RFC 822 data;
converting the RFC 822 data into a normalized MIME form; and
analyzing structural information encoded in the normalized data.

### Claim 20

A system that facilitates interpreting Multipurpose Internet Mail Extensions (MIME) data, comprising:
means for obtaining data;
means for identifying structural information encoded in the MIME data;
means for generating object(s) based on the encoded structural information as the MIME data is analyzed; and
means for building a hierarchical model based upon the object(s).
