Email addresses, display names and non-ASCII headers need proper MIME handling rather than ad-hoc string concatenation.
Why This Matters
Connect the protocol to its actual role. SMTP is for submission, IMAP/POP are for retrieval, while FTP is a separate file-transfer protocol. Authentication and transport encryption are separate concerns.
In this lesson, the focus is Handle Email Addresses and Unicode Headers. The aim is to understand its inputs, observable behavior, and a realistic situation where it is useful, rather than memorize a command name.
How the Example Works
EmailMessage performs header serialization and Unicode encoding when needed. A mailbox address and a friendly display name are different pieces of information.
Step-by-Step Example
from email.message import EmailMessage
from email.utils import formataddr
message = EmailMessage()
message["From"] = formataddr(("Renée", "[email protected]"))
message["To"] = formataddr(("Miyuki", "[email protected]"))
message["Subject"] = "Résumé received"
message.set_content("Thank you.")
print(message["Subject"])
print(message["From"])Understanding the Result
- The program starts by importing email.message, email.utils, making the needed interfaces available.
- Watch these operations in order:
EmailMessage,formataddr,message.set_content. The arguments and return values are the central parts of the demonstration. - Determine whether this sample only builds/parses a message or would actually contact a remote service. A constructed message is not a delivered message.
Observed Output
Résumé received
Renée <[email protected]>This output was produced by the example in the available local Python test environment. Output that depends on the operating system, time, installed packages, or object representations may differ on your computer.
Important Details and Limitations
Do not use user-provided header strings without validating their shape and permissible contents.
Can your test be completed without contacting an account or service? Prefer constructing a message or parsing sample bytes locally before integrating with a mail provider.
Try It Yourself
Add a non-ASCII display name to the To header.
Before running the modified example, write down what you expect to happen. Test one normal case and one boundary, missing-input, or invalid case when the operation accepts them.
Common Beginner Mistakes
- Assuming Handle Email Addresses and Unicode Headers behaves the same way with missing, malformed, or unsupported inputs as it does in the worked example.
- Ignoring this requirement: Do not use user-provided header strings without validating their shape and permissible contents.
- Treating a small illustrative snippet as a production-ready program without testing failures, cleanup, and the target environment.
Key Takeaways
- Email addresses, display names and non-ASCII headers need proper MIME handling rather than ad-hoc string concatenation.
- EmailMessage performs header serialization and Unicode encoding when needed.
- To confirm understanding: Add a non-ASCII display name to the To header.