class Mail::StructuredField

Overview

Provides access to a structured header field

===Per RFC 2822: 2.2.2. Structured Header Field Bodies

Some field bodies in this standard have specific syntactical
structure more restrictive than the unstructured field bodies
described above. These are referred to as "structured" field bodies.
Structured field bodies are sequences of specific lexical tokens as
described in sections 3 and 4 of this standard.  Many of these tokens
are allowed (according to their syntax) to be introduced or end with
comments (as described in section 3.2.3) as well as the space (SP,
ASCII value 32) and horizontal tab (HTAB, ASCII value 9) characters
(together known as the white space characters, WSP), and those WSP
characters are subject to header "folding" and "unfolding" as
described in section 2.2.3.  Semantic analysis of structured field
bodies is given along with their syntax.

Direct Known Subclasses

Defined in:

mail/fields/structured_field.cr

Instance methods inherited from class Mail::CommonField

charset : String | Nil charset, charset=(charset : String | Nil) charset=, decoded decoded, default default, do_decode do_decode, do_encode do_encode, element element, element=(element) element=, encoded encoded, errors : Array(Array(Mail::Field::ParseError | String)) errors, errors=(errors : Array(Array(String | Field::ParseError))) errors=, main_type main_type, mime_type mime_type, name : String | Nil name, name=(name : String | Nil) name=, parameters parameters, parse parse, responsible_for?(field_name) responsible_for?, singular? singular?, to_s to_s, value : String | Nil value, value=(value) value=

Constructor methods inherited from class Mail::CommonField

new(value = nil, charset = nil) new

Class methods inherited from class Mail::CommonField

parse(*args) parse, singular? singular?