djc on main
Test that RFC2971 parser can de… (compare)
djc on main
Remove unused lifetime (compare)
djc on imap-proto-0.16.1
djc on main
Revert "Simplify configuration … (compare)
djc on main
Simplify configuration for carg… (compare)
djc on main
Bump version to 0.16.1 (compare)
djc on main
Add support for RFC 4314/2086 A… (compare)
assert_matches!(
super::capability_data(b"CAPABILITY IMAP4rev1\r\n"),
Ok((_, capabilities)) => {
assert_eq!(capabilities, vec![Capability::Imap4rev1])
}
);
Message
has all the completely shared fields, and consist of one or more Entity
s, which have the mostly-shared fields. An Entity
has an enum Body
, which can be one of Body::Basic
, Body::Message
, and Body::Multipart
. The text
type is a special case of Body::Basic
.
content_
prefixes on fields? these don't seem to add much
BodyStructureBasic
et al into BodyStructure
as struct variants
sub_type
just subtype
type
i'll have to escape them like r#type
body_structure.rs
see the macros in parser::macros
, anybody have any clues?