Enum MessageParseError 

#[non_exhaustive]
pub enum MessageParseError {
    InvalidUtf8,
    #[non_exhaustive]
    InvalidHeaderLine {
        line: String,
    },
    #[non_exhaustive]
    MailboxHeaderParse {
        header: &'static str,
    },
    #[non_exhaustive]
    AddressHeaderParse {
        header: &'static str,
    },
    #[non_exhaustive]
    Date {
        source: Parse,
    },
    #[non_exhaustive]
    MessageId {
        source: MessageIdParseError,
    },
    #[non_exhaustive]
    MimeBodyParse {
        details: String,
    },
}

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

InvalidUtf8

#[non_exhaustive]

InvalidHeaderLine

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

line: String

#[non_exhaustive]

MailboxHeaderParse

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

header: &'static str

#[non_exhaustive]

AddressHeaderParse

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

header: &'static str

#[non_exhaustive]

Date

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

source: Parse

#[non_exhaustive]

MessageId

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

source: MessageIdParseError

#[non_exhaustive]

MimeBodyParse

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

details: String

Trait Implementations

impl Debug for MessageParseError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for MessageParseError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for MessageParseError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl PartialEq for MessageParseError

fn eq(&self, other: &Self) -> bool

Pragmatic equality: variants compare by tag, ignoring the boxed source chains on Date and MessageId. Sufficient for tests and avoids forcing Eq on third-party error types.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Eq for MessageParseError