Source code:
———
The following exception classes are defined in the email.errors module:
exceptionemail.errors.MessageError
This is the base class for all exceptions that the
package can raise. It is derived from the standard
class and defines no additional methods.
exceptionemail.errors.MessageParseError
This is the base class for exceptions raised by the
class. It is derived from
. This class is also used internally by the parser used by
.
Raised under some error conditions when parsing the
headers of a message, this class is derived from
. The
method will raise this error if the content type is unknown when the method is called.
may raise this error for certain base64 decoding errors, and when an attempt is made to create a header that appears to contain an embedded header (that is, there is what is supposed to be a continuation line that has no leading whitespace and looks like a header).
exceptionemail.errors.BoundaryError
Deprecated and no longer used.
exceptionemail.errors.MultipartConversionError
Raised if the
method is called on an instance of a class derived from
(e.g.
). MultipartConversionError multiply inherits from
and the built-in
.
Raised when an error occurs when the
outputs headers.
exceptionemail.errors.MessageDefect
This is the base class for all defects found when parsing email messages. It is derived from
.
This is the base class for all defects found when parsing email headers. It is derived from
.
Here is the list of the defects that the
can find while parsing messages. Note that the defects are added to the message where the problem was found, so for example, if a message nested inside a multipart/alternative had a malformed header, that nested message object would have a defect, but the containing messages would not.
All defect classes are subclassed from
.
exceptionemail.errors.NoBoundaryInMultipartDefect
A message claimed to be a multipart, but had no boundary parameter.
exceptionemail.errors.StartBoundaryNotFoundDefect
The start boundary claimed in the header was never found.
exceptionemail.errors.CloseBoundaryNotFoundDefect
A start boundary was found, but no corresponding close boundary was ever found.
Added in version 3.3.
The message had a continuation line as its first header line.
A “Unix From” header was found in the middle of a header block.
exceptionemail.errors.MissingHeaderBodySeparatorDefect
A line was found while parsing headers that had no leading white space but contained no ‘:’. Parsing continues assuming that the line represents the first line of the body.
Added in version 3.3.
A header was found that was missing a colon, or was otherwise malformed.
Deprecated since version 3.3: This defect has not been used for several Python versions.
exceptionemail.errors.MultipartInvariantViolationDefect
A message claimed to be a multipart, but no subparts were found. Note that when a message has this defect, its
method may return False even though its content type claims to be multipart.
exceptionemail.errors.InvalidBase64PaddingDefect
When decoding a block of base64 encoded bytes, the padding was not correct. Enough padding is added to perform the decode, but the resulting decoded bytes may be invalid.
exceptionemail.errors.InvalidBase64CharactersDefect
When decoding a block of base64 encoded bytes, characters outside the base64 alphabet were encountered. The characters are ignored, but the resulting decoded bytes may be invalid.
exceptionemail.errors.InvalidBase64LengthDefect
When decoding a block of base64 encoded bytes, the number of non-padding base64 characters was invalid (1 more than a multiple of 4). The encoded block was kept as-is.
exceptionemail.errors.InvalidDateDefect
When decoding an invalid or unparsable date field. The original value is kept as-is.