Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
2to3.html	70.96 KB	-rw-r--r--
__future__.html	20.75 KB	-rw-r--r--
__main__.html	44.87 KB	-rw-r--r--
_thread.html	30.39 KB	-rw-r--r--
abc.html	46.87 KB	-rw-r--r--
aifc.html	35.56 KB	-rw-r--r--
allos.html	34.33 KB	-rw-r--r--
archiving.html	17 KB	-rw-r--r--
argparse.html	300.89 KB	-rw-r--r--
array.html	37.28 KB	-rw-r--r--
ast.html	293.08 KB	-rw-r--r--
asynchat.html	37.41 KB	-rw-r--r--
asyncio-api-index.html	27.68 KB	-rw-r--r--
asyncio-dev.html	36.1 KB	-rw-r--r--
asyncio-eventloop.html	204.43 KB	-rw-r--r--
asyncio-exceptions.html	17.11 KB	-rw-r--r--
asyncio-future.html	38.23 KB	-rw-r--r--
asyncio-llapi-index.html	61.97 KB	-rw-r--r--
asyncio-platforms.html	21.77 KB	-rw-r--r--
asyncio-policy.html	39.56 KB	-rw-r--r--
asyncio-protocol.html	118.33 KB	-rw-r--r--
asyncio-queue.html	31.86 KB	-rw-r--r--
asyncio-stream.html	69.98 KB	-rw-r--r--
asyncio-subprocess.html	49.25 KB	-rw-r--r--
asyncio-sync.html	42.79 KB	-rw-r--r--
asyncio-task.html	109.14 KB	-rw-r--r--
asyncio.html	17.31 KB	-rw-r--r--
asyncore.html	49.36 KB	-rw-r--r--
atexit.html	22.87 KB	-rw-r--r--
audioop.html	46 KB	-rw-r--r--
audit_events.html	72.85 KB	-rw-r--r--
base64.html	48.09 KB	-rw-r--r--
bdb.html	66 KB	-rw-r--r--
binary.html	15.97 KB	-rw-r--r--
binascii.html	36.3 KB	-rw-r--r--
binhex.html	15.97 KB	-rw-r--r--
bisect.html	43.38 KB	-rw-r--r--
builtins.html	14.87 KB	-rw-r--r--
bz2.html	50.68 KB	-rw-r--r--
calendar.html	69.35 KB	-rw-r--r--
cgi.html	59.95 KB	-rw-r--r--
cgitb.html	19.96 KB	-rw-r--r--
chunk.html	22.21 KB	-rw-r--r--
cmath.html	43.89 KB	-rw-r--r--
cmd.html	50.42 KB	-rw-r--r--
code.html	35.38 KB	-rw-r--r--
codecs.html	157.96 KB	-rw-r--r--
codeop.html	18.26 KB	-rw-r--r--
collections.abc.html	79.17 KB	-rw-r--r--
collections.html	189.43 KB	-rw-r--r--
colorsys.html	17.31 KB	-rw-r--r--
compileall.html	50.68 KB	-rw-r--r--
concurrency.html	24.15 KB	-rw-r--r--
concurrent.futures.html	79.03 KB	-rw-r--r--
concurrent.html	11.56 KB	-rw-r--r--
configparser.html	159.4 KB	-rw-r--r--
constants.html	22.41 KB	-rw-r--r--
contextlib.html	117.2 KB	-rw-r--r--
contextvars.html	38.38 KB	-rw-r--r--
copy.html	17.92 KB	-rw-r--r--
copyreg.html	18.63 KB	-rw-r--r--
crypt.html	28.29 KB	-rw-r--r--
crypto.html	13.93 KB	-rw-r--r--
csv.html	82.89 KB	-rw-r--r--
ctypes.html	295.49 KB	-rw-r--r--
curses.ascii.html	32.04 KB	-rw-r--r--
curses.html	221.24 KB	-rw-r--r--
curses.panel.html	22.16 KB	-rw-r--r--
custominterp.html	11.85 KB	-rw-r--r--
dataclasses.html	113.16 KB	-rw-r--r--
datatypes.html	31.82 KB	-rw-r--r--
datetime.html	374.92 KB	-rw-r--r--
dbm.html	51.16 KB	-rw-r--r--
debug.html	17 KB	-rw-r--r--
decimal.html	270.12 KB	-rw-r--r--
development.html	32.34 KB	-rw-r--r--
devmode.html	31.72 KB	-rw-r--r--
dialog.html	43.03 KB	-rw-r--r--
difflib.html	111.99 KB	-rw-r--r--
dis.html	136.07 KB	-rw-r--r--
distribution.html	13.67 KB	-rw-r--r--
distutils.html	14.73 KB	-rw-r--r--
doctest.html	199.32 KB	-rw-r--r--
email.charset.html	31.92 KB	-rw-r--r--
email.compat32-message.html	97.74 KB	-rw-r--r--
email.contentmanager.html	37.02 KB	-rw-r--r--
email.encoders.html	18.47 KB	-rw-r--r--
email.errors.html	24.45 KB	-rw-r--r--
email.examples.html	60.49 KB	-rw-r--r--
email.generator.html	48.79 KB	-rw-r--r--
email.header.html	37.61 KB	-rw-r--r--
email.headerregistry.html	66.26 KB	-rw-r--r--
email.html	30.75 KB	-rw-r--r--
email.iterators.html	18.23 KB	-rw-r--r--
email.message.html	99.75 KB	-rw-r--r--
email.mime.html	44.89 KB	-rw-r--r--
email.parser.html	57.39 KB	-rw-r--r--
email.policy.html	84.24 KB	-rw-r--r--
email.utils.html	42.57 KB	-rw-r--r--
ensurepip.html	23.9 KB	-rw-r--r--
enum.html	151 KB	-rw-r--r--
errno.html	60.17 KB	-rw-r--r--
exceptions.html	108.44 KB	-rw-r--r--
faulthandler.html	31.5 KB	-rw-r--r--
fcntl.html	36.67 KB	-rw-r--r--
filecmp.html	32.08 KB	-rw-r--r--
fileformats.html	13.52 KB	-rw-r--r--
fileinput.html	40.37 KB	-rw-r--r--
filesys.html	16.78 KB	-rw-r--r--
fnmatch.html	21.02 KB	-rw-r--r--
fractions.html	35.29 KB	-rw-r--r--
frameworks.html	16.15 KB	-rw-r--r--
ftplib.html	71.97 KB	-rw-r--r--
functional.html	12.19 KB	-rw-r--r--
functions.html	260.33 KB	-rw-r--r--
functools.html	92.96 KB	-rw-r--r--
gc.html	40.97 KB	-rw-r--r--
getopt.html	29.4 KB	-rw-r--r--
getpass.html	16.01 KB	-rw-r--r--
gettext.html	98.02 KB	-rw-r--r--
glob.html	27.2 KB	-rw-r--r--
graphlib.html	34.82 KB	-rw-r--r--
grp.html	16.03 KB	-rw-r--r--
gzip.html	45.65 KB	-rw-r--r--
hashlib.html	93.19 KB	-rw-r--r--
heapq.html	42.43 KB	-rw-r--r--
hmac.html	24.74 KB	-rw-r--r--
html.entities.html	14.91 KB	-rw-r--r--
html.html	14.81 KB	-rw-r--r--
html.parser.html	47.7 KB	-rw-r--r--
http.client.html	85.63 KB	-rw-r--r--
http.cookiejar.html	113.94 KB	-rw-r--r--
http.cookies.html	47.64 KB	-rw-r--r--
http.html	45.52 KB	-rw-r--r--
http.server.html	73.05 KB	-rw-r--r--
i18n.html	13.44 KB	-rw-r--r--
idle.html	77.18 KB	-rw-r--r--
imaplib.html	87.08 KB	-rw-r--r--
imghdr.html	17.94 KB	-rw-r--r--
imp.html	54.32 KB	-rw-r--r--
importlib.html	239.96 KB	-rw-r--r--
importlib.metadata.html	43.14 KB	-rw-r--r--
index.html	75.06 KB	-rw-r--r--
inspect.html	168.74 KB	-rw-r--r--
internet.html	29.89 KB	-rw-r--r--
intro.html	13.81 KB	-rw-r--r--
io.html	154.15 KB	-rw-r--r--
ipaddress.html	137.75 KB	-rw-r--r--
ipc.html	12.6 KB	-rw-r--r--
itertools.html	153.27 KB	-rw-r--r--
json.html	98.9 KB	-rw-r--r--
keyword.html	14.88 KB	-rw-r--r--
language.html	16.71 KB	-rw-r--r--
linecache.html	18.09 KB	-rw-r--r--
locale.html	77.35 KB	-rw-r--r--
logging.config.html	100.3 KB	-rw-r--r--
logging.handlers.html	146.28 KB	-rw-r--r--
logging.html	169.67 KB	-rw-r--r--
lzma.html	66.89 KB	-rw-r--r--
mailbox.html	176.34 KB	-rw-r--r--
mailcap.html	20.86 KB	-rw-r--r--
markup.html	22.31 KB	-rw-r--r--
marshal.html	24.43 KB	-rw-r--r--
math.html	85.82 KB	-rw-r--r--
mimetypes.html	40.27 KB	-rw-r--r--
mm.html	11.16 KB	-rw-r--r--
mmap.html	55.53 KB	-rw-r--r--
modulefinder.html	23.67 KB	-rw-r--r--
modules.html	15.88 KB	-rw-r--r--
msilib.html	78.38 KB	-rw-r--r--
msvcrt.html	29.22 KB	-rw-r--r--
multiprocessing.html	405.24 KB	-rw-r--r--
multiprocessing.shared_memory....	60 KB	-rw-r--r--
netdata.html	20.24 KB	-rw-r--r--
netrc.html	20.39 KB	-rw-r--r--
nis.html	16.76 KB	-rw-r--r--
nntplib.html	84.93 KB	-rw-r--r--
numbers.html	45.67 KB	-rw-r--r--
numeric.html	19.29 KB	-rw-r--r--
operator.html	107.32 KB	-rw-r--r--
optparse.html	256.96 KB	-rw-r--r--
os.html	594.39 KB	-rw-r--r--
os.path.html	65.54 KB	-rw-r--r--
ossaudiodev.html	56.35 KB	-rw-r--r--
pathlib.html	170.01 KB	-rw-r--r--
pdb.html	68.67 KB	-rw-r--r--
persistence.html	19.13 KB	-rw-r--r--
pickle.html	154.45 KB	-rw-r--r--
pickletools.html	22.92 KB	-rw-r--r--
pipes.html	21.7 KB	-rw-r--r--
pkgutil.html	42.76 KB	-rw-r--r--
platform.html	45.08 KB	-rw-r--r--
plistlib.html	30.06 KB	-rw-r--r--
poplib.html	41.42 KB	-rw-r--r--
posix.html	20.96 KB	-rw-r--r--
pprint.html	55.35 KB	-rw-r--r--
profile.html	84.63 KB	-rw-r--r--
pty.html	23.7 KB	-rw-r--r--
pwd.html	16.84 KB	-rw-r--r--
py_compile.html	29 KB	-rw-r--r--
pyclbr.html	24.06 KB	-rw-r--r--
pydoc.html	19.59 KB	-rw-r--r--
pyexpat.html	104.38 KB	-rw-r--r--
python.html	22.46 KB	-rw-r--r--
queue.html	43.39 KB	-rw-r--r--
quopri.html	18.64 KB	-rw-r--r--
random.html	86.31 KB	-rw-r--r--
re.html	214.24 KB	-rw-r--r--
readline.html	50.19 KB	-rw-r--r--
reprlib.html	30.85 KB	-rw-r--r--
resource.html	48.26 KB	-rw-r--r--
rlcompleter.html	18.06 KB	-rw-r--r--
runpy.html	30.99 KB	-rw-r--r--
sched.html	27.04 KB	-rw-r--r--
secrets.html	30.2 KB	-rw-r--r--
security_warnings.html	16.21 KB	-rw-r--r--
select.html	74.58 KB	-rw-r--r--
selectors.html	41.91 KB	-rw-r--r--
shelve.html	36.54 KB	-rw-r--r--
shlex.html	61.03 KB	-rw-r--r--
shutil.html	100.13 KB	-rw-r--r--
signal.html	95.39 KB	-rw-r--r--
site.html	38.16 KB	-rw-r--r--
smtpd.html	44.09 KB	-rw-r--r--
smtplib.html	81.4 KB	-rw-r--r--
sndhdr.html	16.4 KB	-rw-r--r--
socket.html	256.95 KB	-rw-r--r--
socketserver.html	91.95 KB	-rw-r--r--
spwd.html	16.71 KB	-rw-r--r--
sqlite3.html	225.51 KB	-rw-r--r--
ssl.html	328.83 KB	-rw-r--r--
stat.html	57.79 KB	-rw-r--r--
statistics.html	123.22 KB	-rw-r--r--
stdtypes.html	615.43 KB	-rw-r--r--
string.html	108.03 KB	-rw-r--r--
stringprep.html	24.94 KB	-rw-r--r--
struct.html	70.58 KB	-rw-r--r--
subprocess.html	199.03 KB	-rw-r--r--
sunau.html	39.84 KB	-rw-r--r--
superseded.html	26.21 KB	-rw-r--r--
symtable.html	33.26 KB	-rw-r--r--
sys.html	198.83 KB	-rw-r--r--
sysconfig.html	39.81 KB	-rw-r--r--
syslog.html	27.36 KB	-rw-r--r--
tabnanny.html	16.18 KB	-rw-r--r--
tarfile.html	161.92 KB	-rw-r--r--
telnetlib.html	38.21 KB	-rw-r--r--
tempfile.html	58.39 KB	-rw-r--r--
termios.html	22.86 KB	-rw-r--r--
test.html	222.85 KB	-rw-r--r--
text.html	16.8 KB	-rw-r--r--
textwrap.html	48.83 KB	-rw-r--r--
threading.html	128.33 KB	-rw-r--r--
time.html	107.46 KB	-rw-r--r--
timeit.html	52.63 KB	-rw-r--r--
tk.html	28.08 KB	-rw-r--r--
tkinter.colorchooser.html	14.49 KB	-rw-r--r--
tkinter.dnd.html	17.09 KB	-rw-r--r--
tkinter.font.html	22.21 KB	-rw-r--r--
tkinter.html	106.85 KB	-rw-r--r--
tkinter.messagebox.html	20.09 KB	-rw-r--r--
tkinter.scrolledtext.html	14.52 KB	-rw-r--r--
tkinter.tix.html	59.69 KB	-rw-r--r--
tkinter.ttk.html	138.37 KB	-rw-r--r--
token.html	45.73 KB	-rw-r--r--
tokenize.html	39.86 KB	-rw-r--r--
trace.html	38.85 KB	-rw-r--r--
traceback.html	75.61 KB	-rw-r--r--
tracemalloc.html	122.33 KB	-rw-r--r--
tty.html	14.46 KB	-rw-r--r--
turtle.html	271.71 KB	-rw-r--r--
types.html	64.85 KB	-rw-r--r--
typing.html	315.69 KB	-rw-r--r--
unicodedata.html	27.3 KB	-rw-r--r--
unittest.html	310.01 KB	-rw-r--r--
unittest.mock-examples.html	177.75 KB	-rw-r--r--
unittest.mock.html	363.51 KB	-rw-r--r--
unix.html	13.46 KB	-rw-r--r--
urllib.error.html	18.56 KB	-rw-r--r--
urllib.html	12.92 KB	-rw-r--r--
urllib.parse.html	104.65 KB	-rw-r--r--
urllib.request.html	208.87 KB	-rw-r--r--
urllib.robotparser.html	22.63 KB	-rw-r--r--
uu.html	18.2 KB	-rw-r--r--
uuid.html	42.88 KB	-rw-r--r--
venv.html	90.43 KB	-rw-r--r--
warnings.html	69.13 KB	-rw-r--r--
wave.html	36.12 KB	-rw-r--r--
weakref.html	73.36 KB	-rw-r--r--
webbrowser.html	33.98 KB	-rw-r--r--
windows.html	12.32 KB	-rw-r--r--
winreg.html	89.48 KB	-rw-r--r--
winsound.html	26.3 KB	-rw-r--r--
wsgiref.html	111.52 KB	-rw-r--r--
xdrlib.html	42.07 KB	-rw-r--r--
xml.dom.html	114.66 KB	-rw-r--r--
xml.dom.minidom.html	49.6 KB	-rw-r--r--
xml.dom.pulldom.html	30.06 KB	-rw-r--r--
xml.etree.elementtree.html	186.49 KB	-rw-r--r--
xml.html	22.34 KB	-rw-r--r--
xml.sax.handler.html	55.78 KB	-rw-r--r--
xml.sax.html	31.74 KB	-rw-r--r--
xml.sax.reader.html	56.23 KB	-rw-r--r--
xml.sax.utils.html	22.28 KB	-rw-r--r--
xmlrpc.client.html	79.73 KB	-rw-r--r--
xmlrpc.html	11.9 KB	-rw-r--r--
xmlrpc.server.html	63.56 KB	-rw-r--r--
zipapp.html	52.45 KB	-rw-r--r--
zipfile.html	116.59 KB	-rw-r--r--
zipimport.html	33.76 KB	-rw-r--r--
zlib.html	42.29 KB	-rw-r--r--
zoneinfo.html	57.25 KB	-rw-r--r--

Code Editor : email.compat32-message.html

<!DOCTYPE html>

<title>email.message.Message: Representing an email message using the compat32 API &#8212; Python 3.10.12 documentation</title><meta name="viewport" content="width=device-width, initial-scale=1.0">
 
 <link rel="stylesheet" type="text/css" href="../_static/pygments.css" />
 <link rel="stylesheet" type="text/css" href="../_static/pydoctheme.css?2022.1" />
 
 <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
 <script src="../_static/jquery.js"></script>
 <script src="../_static/underscore.js"></script>
 <script src="../_static/doctools.js"></script>
 
 <script src="../_static/sidebar.js"></script>
 
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 3.10.12 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="email.mime: Creating email and MIME objects from scratch" href="email.mime.html" />
 <link rel="prev" title="email: Examples" href="email.examples.html" />
 <link rel="canonical" href="file:///usr/share/doc/python3.10/html/library/email.compat32-message.html" />

</head>
<body>
<div class="mobile-nav">
 <input type="checkbox" id="menuToggler" class="toggler__input" aria-controls="navigation"
 aria-pressed="false" aria-expanded="false" role="button" aria-label="Menu" />
 <label for="menuToggler" class="toggler__label">
 
 </label>
 <nav class="nav-content" role="navigation">
 <a href="https://www.python.org/" class="nav-logo">
 <img src="../_static/py.svg" alt="Logo"/>
 </a>
 <div class="version_switcher_placeholder"></div>
 <form role="search" class="search" action="../search.html" method="get">
 <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" class="search-icon">
 <path fill-rule="nonzero"
 d="M15.5 14h-.79l-.28-.27a6.5 6.5 0 001.48-5.34c-.47-2.78-2.79-5-5.59-5.34a6.505 6.505 0 00-7.27 7.27c.34 2.8 2.56 5.12 5.34 5.59a6.5 6.5 0 005.34-1.48l.27.28v.79l4.25 4.25c.41.41 1.08.41 1.49 0 .41-.41.41-1.08 0-1.49L15.5 14zm-6 0C7.01 14 5 11.99 5 9.5S7.01 5 9.5 5 14 7.01 14 9.5 11.99 14 9.5 14z" fill="#444"></path>
 </svg>
 <input type="text" name="q" aria-label="Quick search"/>
 <input type="submit" value="Go"/>
 </form>
 </nav>
 <div class="menu-wrapper">
 <nav class="menu" role="navigation" aria-label="main navigation">
 <div class="language_switcher_placeholder"></div>
 <h4>Previous topic</h4>
 <a href="email.examples.html"
 title="previous chapter"><code class="xref py py-mod docutils literal notranslate">email</code>: Examples</a>
 <h4>Next topic</h4>
 <a href="email.mime.html"
 title="next chapter"><code class="xref py py-mod docutils literal notranslate">email.mime</code>: Creating email and MIME objects from scratch</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li>
 <a href="https://github.com/python/cpython/blob/3.10/Doc/library/email.compat32-message.rst"
 rel="nofollow">Show Source
 </a>
 </li>
 </ul>
 </div>
 </nav>
 </div>
</div>

<div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="email.mime.html" title="email.mime: Creating email and MIME objects from scratch"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="email.examples.html" title="email: Examples"
 accesskey="P">previous</a> |</li>

<li><img src="../_static/py.svg" alt="python logo" style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li class="switchers">
 <div class="language_switcher_placeholder"></div>
 <div class="version_switcher_placeholder"></div>
 </li>
 <li>
 
 </li>
 <li id="cpython-language-and-version">
 <a href="../index.html">3.10.12 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="netdata.html" >Internet Data Handling</a> &#187;</li>
 <li class="nav-item nav-item-3"><a href="email.html" accesskey="U"><code class="xref py py-mod docutils literal notranslate">email</code> — An email and MIME handling package</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">email.message.Message</code>: Representing an email message using the <code class="xref py py-data docutils literal notranslate">compat32</code> API</a></li>
 <li class="right">

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="email-message-message-representing-an-email-message-using-the-compat32-api">
<h1><a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-mod docutils literal notranslate">email.message.Message</code></a>: Representing an email message using the <a class="reference internal" href="email.policy.html#email.policy.compat32" title="email.policy.compat32"><code class="xref py py-data docutils literal notranslate">compat32</code></a> API<a class="headerlink" href="#email-message-message-representing-an-email-message-using-the-compat32-api" title="Permalink to this headline">¶</a></h1>
The <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> class is very similar to the
<a class="reference internal" href="email.message.html#email.message.EmailMessage" title="email.message.EmailMessage"><code class="xref py py-class docutils literal notranslate">EmailMessage</code></a> class, without the methods added by that
class, and with the default behavior of certain other methods being slightly
different. We also document here some methods that, while supported by the
<a class="reference internal" href="email.message.html#email.message.EmailMessage" title="email.message.EmailMessage"><code class="xref py py-class docutils literal notranslate">EmailMessage</code></a> class, are not recommended unless you are
dealing with legacy code.
The philosophy and structure of the two classes is otherwise the same.
This document describes the behavior under the default (for <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a>)
policy <a class="reference internal" href="email.policy.html#email.policy.Compat32" title="email.policy.Compat32"><code class="xref py py-attr docutils literal notranslate">Compat32</code></a>. If you are going to use another policy,
you should be using the <a class="reference internal" href="email.message.html#email.message.EmailMessage" title="email.message.EmailMessage"><code class="xref py py-class docutils literal notranslate">EmailMessage</code></a> class instead.
An email message consists of headers and a payload. Headers must be
<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc5322.html">RFC 5322</a> style names and values, where the field name and value are
separated by a colon. The colon is not part of either the field name or the
field value. The payload may be a simple text message, or a binary object, or
a structured sequence of sub-messages each with their own set of headers and
their own payload. The latter type of payload is indicated by the message
having a MIME type such as multipart/* or
message/rfc822.
The conceptual model provided by a <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> object is that of an
ordered dictionary of headers with additional methods for accessing both
specialized information from the headers, for accessing the payload, for
generating a serialized version of the message, and for recursively walking
over the object tree. Note that duplicate headers are supported but special
methods must be used to access them.
The <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> pseudo-dictionary is indexed by the header names, which
must be ASCII values. The values of the dictionary are strings that are
supposed to contain only ASCII characters; there is some special handling for
non-ASCII input, but it doesn’t always produce the correct results. Headers
are stored and returned in case-preserving form, but field names are matched
case-insensitively. There may also be a single envelope header, also known as
the Unix-From header or the <code class="docutils literal notranslate">From_</code> header. The payload is either a
string or bytes, in the case of simple message objects, or a list of
<a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects, for MIME container documents (e.g.
multipart/* and message/rfc822).
Here are the methods of the <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> class:
<dl class="py class">
<dt class="sig sig-object py" id="email.message.Message">
class email.message.Message(policy=compat32)<a class="headerlink" href="#email.message.Message" title="Permalink to this definition">¶</a></dt>
<dd>If policy is specified (it must be an instance of a <a class="reference internal" href="email.policy.html#module-email.policy" title="email.policy: Controlling the parsing and generating of messages"><code class="xref py py-mod docutils literal notranslate">policy</code></a>
class) use the rules it specifies to update and serialize the representation
of the message. If policy is not set, use the <a class="reference internal" href="email.policy.html#email.policy.Compat32" title="email.policy.Compat32"><code class="xref py py-class docutils literal notranslate">compat32</code></a> policy, which maintains backward compatibility with
the Python 3.2 version of the email package. For more information see the
<a class="reference internal" href="email.policy.html#module-email.policy" title="email.policy: Controlling the parsing and generating of messages"><code class="xref py py-mod docutils literal notranslate">policy</code></a> documentation.
<div class="versionchanged">
Changed in version 3.3: The policy keyword argument was added.
</div>
<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.as_string">
as_string(unixfrom=False, maxheaderlen=0, policy=None)<a class="headerlink" href="#email.message.Message.as_string" title="Permalink to this definition">¶</a></dt>
<dd>Return the entire message flattened as a string. When optional unixfrom
is true, the envelope header is included in the returned string.
unixfrom defaults to <code class="docutils literal notranslate">False</code>. For backward compatibility reasons,
maxheaderlen defaults to <code class="docutils literal notranslate">0</code>, so if you want a different value you
must override it explicitly (the value specified for max_line_length in
the policy will be ignored by this method). The policy argument may be
used to override the default policy obtained from the message instance.
This can be used to control some of the formatting produced by the
method, since the specified policy will be passed to the <code class="docutils literal notranslate">Generator</code>.
Flattening the message may trigger changes to the <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> if
defaults need to be filled in to complete the transformation to a string
(for example, MIME boundaries may be generated or modified).
Note that this method is provided as a convenience and may not always
format the message the way you want. For example, by default it does
not do the mangling of lines that begin with <code class="docutils literal notranslate">From</code> that is
required by the Unix mbox format. For more flexibility, instantiate a
<a class="reference internal" href="email.generator.html#email.generator.Generator" title="email.generator.Generator"><code class="xref py py-class docutils literal notranslate">Generator</code></a> instance and use its
<a class="reference internal" href="email.generator.html#email.generator.Generator.flatten" title="email.generator.Generator.flatten"><code class="xref py py-meth docutils literal notranslate">flatten()</code></a> method directly. For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>from io import StringIO
from email.generator import Generator
fp = StringIO()
g = Generator(fp, mangle_from_=True, maxheaderlen=60)
g.flatten(msg)
text = fp.getvalue()
</pre></div>
</div>
If the message object contains binary data that is not encoded according
to RFC standards, the non-compliant data will be replaced by unicode
“unknown character” code points. (See also <a class="reference internal" href="#email.message.Message.as_bytes" title="email.message.Message.as_bytes"><code class="xref py py-meth docutils literal notranslate">as_bytes()</code></a> and
<a class="reference internal" href="email.generator.html#email.generator.BytesGenerator" title="email.generator.BytesGenerator"><code class="xref py py-class docutils literal notranslate">BytesGenerator</code></a>.)
<div class="versionchanged">
Changed in version 3.4: the policy keyword argument was added.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__str__">
__str__()<a class="headerlink" href="#email.message.Message.__str__" title="Permalink to this definition">¶</a></dt>
<dd>Equivalent to <a class="reference internal" href="#email.message.Message.as_string" title="email.message.Message.as_string"><code class="xref py py-meth docutils literal notranslate">as_string()</code></a>. Allows <code class="docutils literal notranslate">str(msg)</code> to produce a
string containing the formatted message.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.as_bytes">
as_bytes(unixfrom=False, policy=None)<a class="headerlink" href="#email.message.Message.as_bytes" title="Permalink to this definition">¶</a></dt>
<dd>Return the entire message flattened as a bytes object. When optional
unixfrom is true, the envelope header is included in the returned
string. unixfrom defaults to <code class="docutils literal notranslate">False</code>. The policy argument may be
used to override the default policy obtained from the message instance.
This can be used to control some of the formatting produced by the
method, since the specified policy will be passed to the
<code class="docutils literal notranslate">BytesGenerator</code>.
Flattening the message may trigger changes to the <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> if
defaults need to be filled in to complete the transformation to a string
(for example, MIME boundaries may be generated or modified).
Note that this method is provided as a convenience and may not always
format the message the way you want. For example, by default it does
not do the mangling of lines that begin with <code class="docutils literal notranslate">From</code> that is
required by the Unix mbox format. For more flexibility, instantiate a
<a class="reference internal" href="email.generator.html#email.generator.BytesGenerator" title="email.generator.BytesGenerator"><code class="xref py py-class docutils literal notranslate">BytesGenerator</code></a> instance and use its
<a class="reference internal" href="email.generator.html#email.generator.BytesGenerator.flatten" title="email.generator.BytesGenerator.flatten"><code class="xref py py-meth docutils literal notranslate">flatten()</code></a> method directly.
For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>from io import BytesIO
from email.generator import BytesGenerator
fp = BytesIO()
g = BytesGenerator(fp, mangle_from_=True, maxheaderlen=60)
g.flatten(msg)
text = fp.getvalue()
</pre></div>
</div>
<div class="versionadded">
New in version 3.4.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__bytes__">
__bytes__()<a class="headerlink" href="#email.message.Message.__bytes__" title="Permalink to this definition">¶</a></dt>
<dd>Equivalent to <a class="reference internal" href="#email.message.Message.as_bytes" title="email.message.Message.as_bytes"><code class="xref py py-meth docutils literal notranslate">as_bytes()</code></a>. Allows <code class="docutils literal notranslate">bytes(msg)</code> to produce a
bytes object containing the formatted message.
<div class="versionadded">
New in version 3.4.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.is_multipart">
is_multipart()<a class="headerlink" href="#email.message.Message.is_multipart" title="Permalink to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the message’s payload is a list of
sub-<a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects, otherwise return <code class="docutils literal notranslate">False</code>. When
<a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> returns <code class="docutils literal notranslate">False</code>, the payload should be a string
object (which might be a CTE encoded binary payload). (Note that
<a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> returning <code class="docutils literal notranslate">True</code> does not necessarily mean that
“msg.get_content_maintype() == ‘multipart’” will return the <code class="docutils literal notranslate">True</code>.
For example, <code class="docutils literal notranslate">is_multipart</code> will return <code class="docutils literal notranslate">True</code> when the
<a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> is of type <code class="docutils literal notranslate">message/rfc822</code>.)
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_unixfrom">
set_unixfrom(unixfrom)<a class="headerlink" href="#email.message.Message.set_unixfrom" title="Permalink to this definition">¶</a></dt>
<dd>Set the message’s envelope header to unixfrom, which should be a string.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_unixfrom">
get_unixfrom()<a class="headerlink" href="#email.message.Message.get_unixfrom" title="Permalink to this definition">¶</a></dt>
<dd>Return the message’s envelope header. Defaults to <code class="docutils literal notranslate">None</code> if the
envelope header was never set.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.attach">
attach(payload)<a class="headerlink" href="#email.message.Message.attach" title="Permalink to this definition">¶</a></dt>
<dd>Add the given payload to the current payload, which must be <code class="docutils literal notranslate">None</code> or
a list of <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects before the call. After the call, the
payload will always be a list of <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects. If you want to
set the payload to a scalar object (e.g. a string), use
<a class="reference internal" href="#email.message.Message.set_payload" title="email.message.Message.set_payload"><code class="xref py py-meth docutils literal notranslate">set_payload()</code></a> instead.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by <a class="reference internal" href="email.message.html#email.message.EmailMessage.set_content" title="email.message.EmailMessage.set_content"><code class="xref py py-meth docutils literal notranslate">set_content()</code></a> and the
related <code class="docutils literal notranslate">make</code> and <code class="docutils literal notranslate">add</code> methods.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_payload">
get_payload(i=None, decode=False)<a class="headerlink" href="#email.message.Message.get_payload" title="Permalink to this definition">¶</a></dt>
<dd>Return the current payload, which will be a list of
<a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects when <a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> is <code class="docutils literal notranslate">True</code>, or a
string when <a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> is <code class="docutils literal notranslate">False</code>. If the payload is a list
and you mutate the list object, you modify the message’s payload in place.
With optional argument i, <a class="reference internal" href="#email.message.Message.get_payload" title="email.message.Message.get_payload"><code class="xref py py-meth docutils literal notranslate">get_payload()</code></a> will return the i-th
element of the payload, counting from zero, if <a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> is
<code class="docutils literal notranslate">True</code>. An <a class="reference internal" href="exceptions.html#IndexError" title="IndexError"><code class="xref py py-exc docutils literal notranslate">IndexError</code></a> will be raised if i is less than 0 or
greater than or equal to the number of items in the payload. If the
payload is a string (i.e. <a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> is <code class="docutils literal notranslate">False</code>) and i is
given, a <a class="reference internal" href="exceptions.html#TypeError" title="TypeError"><code class="xref py py-exc docutils literal notranslate">TypeError</code></a> is raised.
Optional decode is a flag indicating whether the payload should be
decoded or not, according to the Content-Transfer-Encoding
header. When <code class="docutils literal notranslate">True</code> and the message is not a multipart, the payload will
be decoded if this header’s value is <code class="docutils literal notranslate">quoted-printable</code> or <code class="docutils literal notranslate">base64</code>.
If some other encoding is used, or Content-Transfer-Encoding
header is missing, the payload is
returned as-is (undecoded). In all cases the returned value is binary
data. If the message is a multipart and the decode flag is <code class="docutils literal notranslate">True</code>,
then <code class="docutils literal notranslate">None</code> is returned. If the payload is base64 and it was not
perfectly formed (missing padding, characters outside the base64
alphabet), then an appropriate defect will be added to the message’s
defect property (<code class="xref py py-class docutils literal notranslate">InvalidBase64PaddingDefect</code> or
<code class="xref py py-class docutils literal notranslate">InvalidBase64CharactersDefect</code>, respectively).
When decode is <code class="docutils literal notranslate">False</code> (the default) the body is returned as a string
without decoding the Content-Transfer-Encoding. However,
for a Content-Transfer-Encoding of 8bit, an attempt is made
to decode the original bytes using the <code class="docutils literal notranslate">charset</code> specified by the
Content-Type header, using the <code class="docutils literal notranslate">replace</code> error handler.
If no <code class="docutils literal notranslate">charset</code> is specified, or if the <code class="docutils literal notranslate">charset</code> given is not
recognized by the email package, the body is decoded using the default
ASCII charset.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by <a class="reference internal" href="email.message.html#email.message.EmailMessage.get_content" title="email.message.EmailMessage.get_content"><code class="xref py py-meth docutils literal notranslate">get_content()</code></a> and
<a class="reference internal" href="email.message.html#email.message.EmailMessage.iter_parts" title="email.message.EmailMessage.iter_parts"><code class="xref py py-meth docutils literal notranslate">iter_parts()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_payload">
set_payload(payload, charset=None)<a class="headerlink" href="#email.message.Message.set_payload" title="Permalink to this definition">¶</a></dt>
<dd>Set the entire message object’s payload to payload. It is the client’s
responsibility to ensure the payload invariants. Optional charset sets
the message’s default character set; see <a class="reference internal" href="#email.message.Message.set_charset" title="email.message.Message.set_charset"><code class="xref py py-meth docutils literal notranslate">set_charset()</code></a> for details.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by <a class="reference internal" href="email.message.html#email.message.EmailMessage.set_content" title="email.message.EmailMessage.set_content"><code class="xref py py-meth docutils literal notranslate">set_content()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_charset">
set_charset(charset)<a class="headerlink" href="#email.message.Message.set_charset" title="Permalink to this definition">¶</a></dt>
<dd>Set the character set of the payload to charset, which can either be a
<a class="reference internal" href="email.charset.html#email.charset.Charset" title="email.charset.Charset"><code class="xref py py-class docutils literal notranslate">Charset</code></a> instance (see <a class="reference internal" href="email.charset.html#module-email.charset" title="email.charset: Character Sets"><code class="xref py py-mod docutils literal notranslate">email.charset</code></a>), a
string naming a character set, or <code class="docutils literal notranslate">None</code>. If it is a string, it will
be converted to a <a class="reference internal" href="email.charset.html#email.charset.Charset" title="email.charset.Charset"><code class="xref py py-class docutils literal notranslate">Charset</code></a> instance. If charset
is <code class="docutils literal notranslate">None</code>, the <code class="docutils literal notranslate">charset</code> parameter will be removed from the
Content-Type header (the message will not be otherwise
modified). Anything else will generate a <a class="reference internal" href="exceptions.html#TypeError" title="TypeError"><code class="xref py py-exc docutils literal notranslate">TypeError</code></a>.
If there is no existing MIME-Version header one will be
added. If there is no existing Content-Type header, one
will be added with a value of text/plain. Whether the
Content-Type header already exists or not, its <code class="docutils literal notranslate">charset</code>
parameter will be set to charset.output_charset. If
charset.input_charset and charset.output_charset differ, the payload
will be re-encoded to the output_charset. If there is no existing
Content-Transfer-Encoding header, then the payload will be
transfer-encoded, if needed, using the specified
<a class="reference internal" href="email.charset.html#email.charset.Charset" title="email.charset.Charset"><code class="xref py py-class docutils literal notranslate">Charset</code></a>, and a header with the appropriate value
will be added. If a Content-Transfer-Encoding header
already exists, the payload is assumed to already be correctly encoded
using that Content-Transfer-Encoding and is not modified.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by the charset parameter of the
<code class="xref py py-meth docutils literal notranslate">email.emailmessage.EmailMessage.set_content()</code> method.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_charset">
get_charset()<a class="headerlink" href="#email.message.Message.get_charset" title="Permalink to this definition">¶</a></dt>
<dd>Return the <a class="reference internal" href="email.charset.html#email.charset.Charset" title="email.charset.Charset"><code class="xref py py-class docutils literal notranslate">Charset</code></a> instance associated with the
message’s payload.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class it always returns
<code class="docutils literal notranslate">None</code>.
</dd></dl>

The following methods implement a mapping-like interface for accessing the
message’s <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2822.html">RFC 2822</a> headers. Note that there are some semantic differences
between these methods and a normal mapping (i.e. dictionary) interface. For
example, in a dictionary there are no duplicate keys, but here there may be
duplicate message headers. Also, in dictionaries there is no guaranteed
order to the keys returned by <a class="reference internal" href="#email.message.Message.keys" title="email.message.Message.keys"><code class="xref py py-meth docutils literal notranslate">keys()</code></a>, but in a <a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> object,
headers are always returned in the order they appeared in the original
message, or were added to the message later. Any header deleted and then
re-added are always appended to the end of the header list.
These semantic differences are intentional and are biased toward maximal
convenience.
Note that in all cases, any envelope header present in the message is not
included in the mapping interface.
In a model generated from bytes, any header values that (in contravention of
the RFCs) contain non-ASCII bytes will, when retrieved through this
interface, be represented as <a class="reference internal" href="email.header.html#email.header.Header" title="email.header.Header"><code class="xref py py-class docutils literal notranslate">Header</code></a> objects with
a charset of <code class="docutils literal notranslate">unknown-8bit</code>.
<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__len__">
__len__()<a class="headerlink" href="#email.message.Message.__len__" title="Permalink to this definition">¶</a></dt>
<dd>Return the total number of headers, including duplicates.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__contains__">
__contains__(name)<a class="headerlink" href="#email.message.Message.__contains__" title="Permalink to this definition">¶</a></dt>
<dd>Return <code class="docutils literal notranslate">True</code> if the message object has a field named name. Matching is
done case-insensitively and name should not include the trailing colon.
Used for the <code class="docutils literal notranslate">in</code> operator, e.g.:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>if &#39;message-id&#39; in myMessage:
 print(&#39;Message-ID:&#39;, myMessage[&#39;message-id&#39;])
</pre></div>
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__getitem__">
__getitem__(name)<a class="headerlink" href="#email.message.Message.__getitem__" title="Permalink to this definition">¶</a></dt>
<dd>Return the value of the named header field. name should not include the
colon field separator. If the header is missing, <code class="docutils literal notranslate">None</code> is returned; a
<a class="reference internal" href="exceptions.html#KeyError" title="KeyError"><code class="xref py py-exc docutils literal notranslate">KeyError</code></a> is never raised.
Note that if the named field appears more than once in the message’s
headers, exactly which of those field values will be returned is
undefined. Use the <a class="reference internal" href="#email.message.Message.get_all" title="email.message.Message.get_all"><code class="xref py py-meth docutils literal notranslate">get_all()</code></a> method to get the values of all the
extant named headers.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__setitem__">
__setitem__(name, val)<a class="headerlink" href="#email.message.Message.__setitem__" title="Permalink to this definition">¶</a></dt>
<dd>Add a header to the message with field name name and value val. The
field is appended to the end of the message’s existing fields.
Note that this does not overwrite or delete any existing header with the same
name. If you want to ensure that the new header is the only one present in the
message with field name name, delete the field first, e.g.:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>del msg[&#39;subject&#39;]
msg[&#39;subject&#39;] = &#39;Python roolz!&#39;
</pre></div>
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.__delitem__">
__delitem__(name)<a class="headerlink" href="#email.message.Message.__delitem__" title="Permalink to this definition">¶</a></dt>
<dd>Delete all occurrences of the field with name name from the message’s
headers. No exception is raised if the named field isn’t present in the
headers.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.keys">
keys()<a class="headerlink" href="#email.message.Message.keys" title="Permalink to this definition">¶</a></dt>
<dd>Return a list of all the message’s header field names.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.values">
values()<a class="headerlink" href="#email.message.Message.values" title="Permalink to this definition">¶</a></dt>
<dd>Return a list of all the message’s field values.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.items">
items()<a class="headerlink" href="#email.message.Message.items" title="Permalink to this definition">¶</a></dt>
<dd>Return a list of 2-tuples containing all the message’s field headers and
values.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get">
get(name, failobj=None)<a class="headerlink" href="#email.message.Message.get" title="Permalink to this definition">¶</a></dt>
<dd>Return the value of the named header field. This is identical to
<a class="reference internal" href="#email.message.Message.__getitem__" title="email.message.Message.__getitem__"><code class="xref py py-meth docutils literal notranslate">__getitem__()</code></a> except that optional failobj is returned if the
named header is missing (defaults to <code class="docutils literal notranslate">None</code>).
</dd></dl>

Here are some additional useful methods:
<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_all">
get_all(name, failobj=None)<a class="headerlink" href="#email.message.Message.get_all" title="Permalink to this definition">¶</a></dt>
<dd>Return a list of all the values for the field named name. If there are
no such named headers in the message, failobj is returned (defaults to
<code class="docutils literal notranslate">None</code>).
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.add_header">
add_header(_name, _value, **_params)<a class="headerlink" href="#email.message.Message.add_header" title="Permalink to this definition">¶</a></dt>
<dd>Extended header setting. This method is similar to <a class="reference internal" href="#email.message.Message.__setitem__" title="email.message.Message.__setitem__"><code class="xref py py-meth docutils literal notranslate">__setitem__()</code></a>
except that additional header parameters can be provided as keyword
arguments. _name is the header field to add and _value is the
primary value for the header.
For each item in the keyword argument dictionary _params, the key is
taken as the parameter name, with underscores converted to dashes (since
dashes are illegal in Python identifiers). Normally, the parameter will
be added as <code class="docutils literal notranslate">key=&quot;value&quot;</code> unless the value is <code class="docutils literal notranslate">None</code>, in which case
only the key will be added. If the value contains non-ASCII characters,
it can be specified as a three tuple in the format
<code class="docutils literal notranslate">(CHARSET, LANGUAGE, VALUE)</code>, where <code class="docutils literal notranslate">CHARSET</code> is a string naming the
charset to be used to encode the value, <code class="docutils literal notranslate">LANGUAGE</code> can usually be set
to <code class="docutils literal notranslate">None</code> or the empty string (see <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2231.html">RFC 2231</a> for other possibilities),
and <code class="docutils literal notranslate">VALUE</code> is the string value containing non-ASCII code points. If
a three tuple is not passed and the value contains non-ASCII characters,
it is automatically encoded in <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2231.html">RFC 2231</a> format using a <code class="docutils literal notranslate">CHARSET</code>
of <code class="docutils literal notranslate">utf-8</code> and a <code class="docutils literal notranslate">LANGUAGE</code> of <code class="docutils literal notranslate">None</code>.
Here’s an example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>msg.add_header(&#39;Content-Disposition&#39;, &#39;attachment&#39;, filename=&#39;bud.gif&#39;)
</pre></div>
</div>
This will add a header that looks like
<div class="highlight-python3 notranslate"><div class="highlight"><pre>Content-Disposition: attachment; filename=&quot;bud.gif&quot;
</pre></div>
</div>
An example with non-ASCII characters:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>msg.add_header(&#39;Content-Disposition&#39;, &#39;attachment&#39;,
 filename=(&#39;iso-8859-1&#39;, &#39;&#39;, &#39;Fußballer.ppt&#39;))
</pre></div>
</div>
Which produces
<div class="highlight-python3 notranslate"><div class="highlight"><pre>Content-Disposition: attachment; filename*=&quot;iso-8859-1&#39;&#39;Fu%DFballer.ppt&quot;
</pre></div>
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.replace_header">
replace_header(_name, _value)<a class="headerlink" href="#email.message.Message.replace_header" title="Permalink to this definition">¶</a></dt>
<dd>Replace a header. Replace the first header found in the message that
matches _name, retaining header order and field name case. If no
matching header was found, a <a class="reference internal" href="exceptions.html#KeyError" title="KeyError"><code class="xref py py-exc docutils literal notranslate">KeyError</code></a> is raised.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_content_type">
get_content_type()<a class="headerlink" href="#email.message.Message.get_content_type" title="Permalink to this definition">¶</a></dt>
<dd>Return the message’s content type. The returned string is coerced to
lower case of the form maintype/subtype. If there was no
Content-Type header in the message the default type as given
by <a class="reference internal" href="#email.message.Message.get_default_type" title="email.message.Message.get_default_type"><code class="xref py py-meth docutils literal notranslate">get_default_type()</code></a> will be returned. Since according to
<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2045.html">RFC 2045</a>, messages always have a default type, <a class="reference internal" href="#email.message.Message.get_content_type" title="email.message.Message.get_content_type"><code class="xref py py-meth docutils literal notranslate">get_content_type()</code></a>
will always return a value.
<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2045.html">RFC 2045</a> defines a message’s default type to be text/plain
unless it appears inside a multipart/digest container, in
which case it would be message/rfc822. If the
Content-Type header has an invalid type specification,
<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2045.html">RFC 2045</a> mandates that the default type be text/plain.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_content_maintype">
get_content_maintype()<a class="headerlink" href="#email.message.Message.get_content_maintype" title="Permalink to this definition">¶</a></dt>
<dd>Return the message’s main content type. This is the maintype
part of the string returned by <a class="reference internal" href="#email.message.Message.get_content_type" title="email.message.Message.get_content_type"><code class="xref py py-meth docutils literal notranslate">get_content_type()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_content_subtype">
get_content_subtype()<a class="headerlink" href="#email.message.Message.get_content_subtype" title="Permalink to this definition">¶</a></dt>
<dd>Return the message’s sub-content type. This is the subtype
part of the string returned by <a class="reference internal" href="#email.message.Message.get_content_type" title="email.message.Message.get_content_type"><code class="xref py py-meth docutils literal notranslate">get_content_type()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_default_type">
get_default_type()<a class="headerlink" href="#email.message.Message.get_default_type" title="Permalink to this definition">¶</a></dt>
<dd>Return the default content type. Most messages have a default content
type of text/plain, except for messages that are subparts of
multipart/digest containers. Such subparts have a default
content type of message/rfc822.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_default_type">
set_default_type(ctype)<a class="headerlink" href="#email.message.Message.set_default_type" title="Permalink to this definition">¶</a></dt>
<dd>Set the default content type. ctype should either be
text/plain or message/rfc822, although this is not
enforced. The default content type is not stored in the
Content-Type header.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_params">
get_params(failobj=None, header='content-type', unquote=True)<a class="headerlink" href="#email.message.Message.get_params" title="Permalink to this definition">¶</a></dt>
<dd>Return the message’s Content-Type parameters, as a list.
The elements of the returned list are 2-tuples of key/value pairs, as
split on the <code class="docutils literal notranslate">'='</code> sign. The left hand side of the <code class="docutils literal notranslate">'='</code> is the key,
while the right hand side is the value. If there is no <code class="docutils literal notranslate">'='</code> sign in
the parameter the value is the empty string, otherwise the value is as
described in <a class="reference internal" href="#email.message.Message.get_param" title="email.message.Message.get_param"><code class="xref py py-meth docutils literal notranslate">get_param()</code></a> and is unquoted if optional unquote is
<code class="docutils literal notranslate">True</code> (the default).
Optional failobj is the object to return if there is no
Content-Type header. Optional header is the header to
search instead of Content-Type.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by the params property of the individual header objects
returned by the header access methods.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_param">
get_param(param, failobj=None, header='content-type', unquote=True)<a class="headerlink" href="#email.message.Message.get_param" title="Permalink to this definition">¶</a></dt>
<dd>Return the value of the Content-Type header’s parameter
param as a string. If the message has no Content-Type
header or if there is no such parameter, then failobj is returned
(defaults to <code class="docutils literal notranslate">None</code>).
Optional header if given, specifies the message header to use instead of
Content-Type.
Parameter keys are always compared case insensitively. The return value
can either be a string, or a 3-tuple if the parameter was <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2231.html">RFC 2231</a>
encoded. When it’s a 3-tuple, the elements of the value are of the form
<code class="docutils literal notranslate">(CHARSET, LANGUAGE, VALUE)</code>. Note that both <code class="docutils literal notranslate">CHARSET</code> and
<code class="docutils literal notranslate">LANGUAGE</code> can be <code class="docutils literal notranslate">None</code>, in which case you should consider <code class="docutils literal notranslate">VALUE</code>
to be encoded in the <code class="docutils literal notranslate">us-ascii</code> charset. You can usually ignore
<code class="docutils literal notranslate">LANGUAGE</code>.
If your application doesn’t care whether the parameter was encoded as in
<a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2231.html">RFC 2231</a>, you can collapse the parameter value by calling
<a class="reference internal" href="email.utils.html#email.utils.collapse_rfc2231_value" title="email.utils.collapse_rfc2231_value"><code class="xref py py-func docutils literal notranslate">email.utils.collapse_rfc2231_value()</code></a>, passing in the return value
from <a class="reference internal" href="#email.message.Message.get_param" title="email.message.Message.get_param"><code class="xref py py-meth docutils literal notranslate">get_param()</code></a>. This will return a suitably decoded Unicode
string when the value is a tuple, or the original string unquoted if it
isn’t. For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>rawparam = msg.get_param(&#39;foo&#39;)
param = email.utils.collapse_rfc2231_value(rawparam)
</pre></div>
</div>
In any case, the parameter value (either the returned string, or the
<code class="docutils literal notranslate">VALUE</code> item in the 3-tuple) is always unquoted, unless unquote is set
to <code class="docutils literal notranslate">False</code>.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by the params property of the individual header objects
returned by the header access methods.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_param">
set_param(param, value, header='Content-Type', requote=True, charset=None, language='', replace=False)<a class="headerlink" href="#email.message.Message.set_param" title="Permalink to this definition">¶</a></dt>
<dd>Set a parameter in the Content-Type header. If the
parameter already exists in the header, its value will be replaced with
value. If the Content-Type header as not yet been defined
for this message, it will be set to text/plain and the new
parameter value will be appended as per <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2045.html">RFC 2045</a>.
Optional header specifies an alternative header to
Content-Type, and all parameters will be quoted as necessary
unless optional requote is <code class="docutils literal notranslate">False</code> (the default is <code class="docutils literal notranslate">True</code>).
If optional charset is specified, the parameter will be encoded
according to <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2231.html">RFC 2231</a>. Optional language specifies the RFC 2231
language, defaulting to the empty string. Both charset and language
should be strings.
If replace is <code class="docutils literal notranslate">False</code> (the default) the header is moved to the
end of the list of headers. If replace is <code class="docutils literal notranslate">True</code>, the header
will be updated in place.
<div class="versionchanged">
Changed in version 3.4: <code class="docutils literal notranslate">replace</code> keyword was added.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.del_param">
del_param(param, header='content-type', requote=True)<a class="headerlink" href="#email.message.Message.del_param" title="Permalink to this definition">¶</a></dt>
<dd>Remove the given parameter completely from the Content-Type
header. The header will be re-written in place without the parameter or
its value. All values will be quoted as necessary unless requote is
<code class="docutils literal notranslate">False</code> (the default is <code class="docutils literal notranslate">True</code>). Optional header specifies an
alternative to Content-Type.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_type">
set_type(type, header='Content-Type', requote=True)<a class="headerlink" href="#email.message.Message.set_type" title="Permalink to this definition">¶</a></dt>
<dd>Set the main type and subtype for the Content-Type
header. type must be a string in the form maintype/subtype,
otherwise a <a class="reference internal" href="exceptions.html#ValueError" title="ValueError"><code class="xref py py-exc docutils literal notranslate">ValueError</code></a> is raised.
This method replaces the Content-Type header, keeping all
the parameters in place. If requote is <code class="docutils literal notranslate">False</code>, this leaves the
existing header’s quoting as is, otherwise the parameters will be quoted
(the default).
An alternative header can be specified in the header argument. When the
Content-Type header is set a MIME-Version
header is also added.
This is a legacy method. On the
<code class="xref py py-class docutils literal notranslate">EmailMessage</code> class its functionality is
replaced by the <code class="docutils literal notranslate">make_</code> and <code class="docutils literal notranslate">add_</code> methods.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_filename">
get_filename(failobj=None)<a class="headerlink" href="#email.message.Message.get_filename" title="Permalink to this definition">¶</a></dt>
<dd>Return the value of the <code class="docutils literal notranslate">filename</code> parameter of the
Content-Disposition header of the message. If the header
does not have a <code class="docutils literal notranslate">filename</code> parameter, this method falls back to looking
for the <code class="docutils literal notranslate">name</code> parameter on the Content-Type header. If
neither is found, or the header is missing, then failobj is returned.
The returned string will always be unquoted as per
<a class="reference internal" href="email.utils.html#email.utils.unquote" title="email.utils.unquote"><code class="xref py py-func docutils literal notranslate">email.utils.unquote()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_boundary">
get_boundary(failobj=None)<a class="headerlink" href="#email.message.Message.get_boundary" title="Permalink to this definition">¶</a></dt>
<dd>Return the value of the <code class="docutils literal notranslate">boundary</code> parameter of the
Content-Type header of the message, or failobj if either
the header is missing, or has no <code class="docutils literal notranslate">boundary</code> parameter. The returned
string will always be unquoted as per <a class="reference internal" href="email.utils.html#email.utils.unquote" title="email.utils.unquote"><code class="xref py py-func docutils literal notranslate">email.utils.unquote()</code></a>.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.set_boundary">
set_boundary(boundary)<a class="headerlink" href="#email.message.Message.set_boundary" title="Permalink to this definition">¶</a></dt>
<dd>Set the <code class="docutils literal notranslate">boundary</code> parameter of the Content-Type header to
boundary. <a class="reference internal" href="#email.message.Message.set_boundary" title="email.message.Message.set_boundary"><code class="xref py py-meth docutils literal notranslate">set_boundary()</code></a> will always quote boundary if
necessary. A <a class="reference internal" href="email.errors.html#email.errors.HeaderParseError" title="email.errors.HeaderParseError"><code class="xref py py-exc docutils literal notranslate">HeaderParseError</code></a> is raised if the
message object has no Content-Type header.
Note that using this method is subtly different than deleting the old
Content-Type header and adding a new one with the new
boundary via <a class="reference internal" href="#email.message.Message.add_header" title="email.message.Message.add_header"><code class="xref py py-meth docutils literal notranslate">add_header()</code></a>, because <a class="reference internal" href="#email.message.Message.set_boundary" title="email.message.Message.set_boundary"><code class="xref py py-meth docutils literal notranslate">set_boundary()</code></a> preserves
the order of the Content-Type header in the list of
headers. However, it does not preserve any continuation lines which may
have been present in the original Content-Type header.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_content_charset">
get_content_charset(failobj=None)<a class="headerlink" href="#email.message.Message.get_content_charset" title="Permalink to this definition">¶</a></dt>
<dd>Return the <code class="docutils literal notranslate">charset</code> parameter of the Content-Type header,
coerced to lower case. If there is no Content-Type header, or if
that header has no <code class="docutils literal notranslate">charset</code> parameter, failobj is returned.
Note that this method differs from <a class="reference internal" href="#email.message.Message.get_charset" title="email.message.Message.get_charset"><code class="xref py py-meth docutils literal notranslate">get_charset()</code></a> which returns the
<a class="reference internal" href="email.charset.html#email.charset.Charset" title="email.charset.Charset"><code class="xref py py-class docutils literal notranslate">Charset</code></a> instance for the default encoding of the message body.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_charsets">
get_charsets(failobj=None)<a class="headerlink" href="#email.message.Message.get_charsets" title="Permalink to this definition">¶</a></dt>
<dd>Return a list containing the character set names in the message. If the
message is a multipart, then the list will contain one element
for each subpart in the payload, otherwise, it will be a list of length 1.
Each item in the list will be a string which is the value of the
<code class="docutils literal notranslate">charset</code> parameter in the Content-Type header for the
represented subpart. However, if the subpart has no
Content-Type header, no <code class="docutils literal notranslate">charset</code> parameter, or is not of
the text main MIME type, then that item in the returned list
will be failobj.
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.get_content_disposition">
get_content_disposition()<a class="headerlink" href="#email.message.Message.get_content_disposition" title="Permalink to this definition">¶</a></dt>
<dd>Return the lowercased value (without parameters) of the message’s
Content-Disposition header if it has one, or <code class="docutils literal notranslate">None</code>. The
possible values for this method are inline, attachment or <code class="docutils literal notranslate">None</code>
if the message follows <a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc2183.html">RFC 2183</a>.
<div class="versionadded">
New in version 3.5.
</div>
</dd></dl>

<dl class="py method">
<dt class="sig sig-object py" id="email.message.Message.walk">
walk()<a class="headerlink" href="#email.message.Message.walk" title="Permalink to this definition">¶</a></dt>
<dd>The <a class="reference internal" href="#email.message.Message.walk" title="email.message.Message.walk"><code class="xref py py-meth docutils literal notranslate">walk()</code></a> method is an all-purpose generator which can be used to
iterate over all the parts and subparts of a message object tree, in
depth-first traversal order. You will typically use <a class="reference internal" href="#email.message.Message.walk" title="email.message.Message.walk"><code class="xref py py-meth docutils literal notranslate">walk()</code></a> as the
iterator in a <code class="docutils literal notranslate">for</code> loop; each iteration returns the next subpart.
Here’s an example that prints the MIME type of every part of a multipart
message structure:
<div class="highlight-pycon3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; for part in msg.walk():
... print(part.get_content_type())
multipart/report
text/plain
message/delivery-status
text/plain
text/plain
message/rfc822
text/plain
</pre></div>
</div>
<code class="docutils literal notranslate">walk</code> iterates over the subparts of any part where
<a class="reference internal" href="#email.message.Message.is_multipart" title="email.message.Message.is_multipart"><code class="xref py py-meth docutils literal notranslate">is_multipart()</code></a> returns <code class="docutils literal notranslate">True</code>, even though
<code class="docutils literal notranslate">msg.get_content_maintype() == 'multipart'</code> may return <code class="docutils literal notranslate">False</code>. We
can see this in our example by making use of the <code class="docutils literal notranslate">_structure</code> debug
helper function:
<div class="highlight-pycon3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; for part in msg.walk():
... print(part.get_content_maintype() == &#39;multipart&#39;,
... part.is_multipart())
True True
False False
False True
False False
False False
False True
False False
&gt;&gt;&gt; _structure(msg)
multipart/report
 text/plain
 message/delivery-status
 text/plain
 text/plain
 message/rfc822
 text/plain
</pre></div>
</div>
Here the <code class="docutils literal notranslate">message</code> parts are not <code class="docutils literal notranslate">multiparts</code>, but they do contain
subparts. <code class="docutils literal notranslate">is_multipart()</code> returns <code class="docutils literal notranslate">True</code> and <code class="docutils literal notranslate">walk</code> descends
into the subparts.
</dd></dl>

<a class="reference internal" href="#email.message.Message" title="email.message.Message"><code class="xref py py-class docutils literal notranslate">Message</code></a> objects can also optionally contain two instance attributes,
which can be used when generating the plain text of a MIME message.
<dl class="py attribute">
<dt class="sig sig-object py" id="email.message.Message.preamble">
preamble<a class="headerlink" href="#email.message.Message.preamble" title="Permalink to this definition">¶</a></dt>
<dd>The format of a MIME document allows for some text between the blank line
following the headers, and the first multipart boundary string. Normally,
this text is never visible in a MIME-aware mail reader because it falls
outside the standard MIME armor. However, when viewing the raw text of
the message, or when viewing the message in a non-MIME aware reader, this
text can become visible.
The preamble attribute contains this leading extra-armor text for MIME
documents. When the <a class="reference internal" href="email.parser.html#email.parser.Parser" title="email.parser.Parser"><code class="xref py py-class docutils literal notranslate">Parser</code></a> discovers some text
after the headers but before the first boundary string, it assigns this
text to the message’s preamble attribute. When the
<a class="reference internal" href="email.generator.html#email.generator.Generator" title="email.generator.Generator"><code class="xref py py-class docutils literal notranslate">Generator</code></a> is writing out the plain text
representation of a MIME message, and it finds the
message has a preamble attribute, it will write this text in the area
between the headers and the first boundary. See <a class="reference internal" href="email.parser.html#module-email.parser" title="email.parser: Parse flat text email messages to produce a message object structure."><code class="xref py py-mod docutils literal notranslate">email.parser</code></a> and
<a class="reference internal" href="email.generator.html#module-email.generator" title="email.generator: Generate flat text email messages from a message structure."><code class="xref py py-mod docutils literal notranslate">email.generator</code></a> for details.
Note that if the message object has no preamble, the preamble attribute
will be <code class="docutils literal notranslate">None</code>.
</dd></dl>

<dl class="py attribute">
<dt class="sig sig-object py" id="email.message.Message.epilogue">
epilogue<a class="headerlink" href="#email.message.Message.epilogue" title="Permalink to this definition">¶</a></dt>
<dd>The epilogue attribute acts the same way as the preamble attribute,
except that it contains text that appears between the last boundary and
the end of the message.
You do not need to set the epilogue to the empty string in order for the
<a class="reference internal" href="email.generator.html#email.generator.Generator" title="email.generator.Generator"><code class="xref py py-class docutils literal notranslate">Generator</code></a> to print a newline at the end of the
file.
</dd></dl>

<dl class="py attribute">
<dt class="sig sig-object py" id="email.message.Message.defects">
defects<a class="headerlink" href="#email.message.Message.defects" title="Permalink to this definition">¶</a></dt>
<dd>The defects attribute contains a list of all the problems found when
parsing this message. See <a class="reference internal" href="email.errors.html#module-email.errors" title="email.errors: The exception classes used by the email package."><code class="xref py py-mod docutils literal notranslate">email.errors</code></a> for a detailed description
of the possible parsing defects.
</dd></dl>

</dd></dl>

</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <h4>Previous topic</h4>
 <a href="email.examples.html"
 title="previous chapter"><code class="xref py py-mod docutils literal notranslate">email</code>: Examples</a>
 <h4>Next topic</h4>
 <a href="email.mime.html"
 title="next chapter"><code class="xref py py-mod docutils literal notranslate">email.mime</code>: Creating email and MIME objects from scratch</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li>
 <a href="https://github.com/python/cpython/blob/3.10/Doc/library/email.compat32-message.rst"
 rel="nofollow">Show Source
 </a>
 </li>
 </ul>
 </div>
 </div>
 </div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="email.mime.html" title="email.mime: Creating email and MIME objects from scratch"
 >next</a> |</li>
 <li class="right" >
 <a href="email.examples.html" title="email: Examples"
 >previous</a> |</li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Standard Library</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="netdata.html" >Internet Data Handling</a> &#187;</li>
 <li class="nav-item nav-item-3"><a href="email.html" ><code class="xref py py-mod docutils literal notranslate">email</code> — An email and MIME handling package</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href=""><code class="xref py py-mod docutils literal notranslate">email.message.Message</code>: Representing an email message using the <code class="xref py py-data docutils literal notranslate">compat32</code> API</a></li>
 <li class="right">

<div class="inline-search" role="search">
 <form class="inline-search" action="../search.html" method="get">
 <input placeholder="Quick search" aria-label="Quick search" type="text" name="q" />
 <input type="submit" value="Go" />
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>
 </div>
 |
 </li>
 
 </ul>
 </div> 
 <div class="footer">
 &copy; <a href="../copyright.html">Copyright</a> 2001-2026, Python Software Foundation.
 
 This page is licensed under the Python Software Foundation License Version 2.
 
 Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License.
 
 See <a href="/license.html">History and License</a> for more information.

The Python Software Foundation is a non-profit corporation.
<a href="https://www.python.org/psf/donations/">Please donate.</a>

Last updated on January 26, 2026.
 <a href="/bugs.html">Found a bug</a>?

Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 4.3.2.
 </div>

</body>
</html>

${this.title}

Code Editor : email.compat32-message.html