exceptions.EpistoleError
An EpistoleError reports an error reply from a mail service, or a network failure.
Usage
exceptions.EpistoleError(
message,
/,
*,
backend=None,
)Epistole raises TypeError or ValueError instead for a mistake it finds before any network call. A retry loop catches the transient set (ThrottledError, TransportError, ProviderError) by name. See ADR-0004.
Attributes
backend: Backend | None-
The backend the error came from. Connection.send and Backend.connect set it, so it is
Noneonly on an error inspected before it propagates.
Methods
| Name | Description |
|---|---|
| __reduce__() |
Pickle through _rebuild, so unpickling skips __init__.
|
__reduce__()
Pickle through _rebuild, so unpickling skips __init__.
Usage
__reduce__()With the default reduction, unpickling calls cls(message), which raises TypeError for RecipientsRefusedError because refused is required. A process pool would then raise BrokenProcessPool instead of the refusal. As with any exception, pickling drops __cause__, __context__ and __traceback__.