RFC 10080 Makes the Expires Header a Standard for Email
RFC 10080 lets any sender mark when an email stops being valid, and lets mailbox providers hide or de-emphasize expired mail. Here is what the new standard allows, what it forbids and how to use it.
The IETF has published RFC 10080, "Updated Use of the Expires Message Header Field", a Proposed Standard dated 30 October 2026. It takes a header that existed only for X.400 gateways and opens it to all Internet email: a sender can now state, in a standard way, the moment a message stops being valid, and mailbox providers and mail clients may use that date to de-emphasize or hide the message once it has passed.
The RFC is written by Benjamin Billon of Splio and John Levine of Standcore. Its stated goal is to help mailbox providers and mail user agents reduce inbox clutter. For senders of flash sales, event invitations and other dated mail, it adds a new, optional signal to the message header.
Key facts
- Document: RFC 10080, Proposed Standard (IETF Standards Track), October 2026
- Updates: RFC 4021, which had registered Expires as "not for general use"
- Header:
Expires:followed by an RFC 5322 date-time - Senders: at most one Expires field per message
- Receivers: may hide or de-emphasize expired mail; must not reject or discard a message based solely on this header
From X.400 relic to standard header
The Expires field is not new. RFC 2156 introduced it to carry the expiry date of X.400 messages into Internet mail, but it never said what a receiver should do with it beyond warning that "no automatic handling past that date can be expected". RFC 4021 later listed the field in the IANA header registry, with the label "not for general use".
RFC 10080 extends the field to Internet email in general, whether or not the message passed through an X.400 gateway. IANA has updated the "Expires" entry in the Permanent Message Header Field Names registry: protocol mail, status standard, change controller IETF, reference RFC 10080.
What the RFC says
The syntax
The rule is short: expires = "Expires:" date-time CRLF, where date-time is the same date format used in the Date header under RFC 5322. The RFC gives this example:
Expires: Wed, 3 Dec 2025 17:22:57 +0000
Expiration is defined as the point after which the message "loses its validity". The RFC deliberately stops there: it adds no further required behavior for readers, because there is no consensus on one and existing implementations differ.
Rules for message creators
The field should only be added when the creator knows the message loses its validity at a given time. The RFC cites time-limited newsletter offers, event announcements and periodic announcements as examples. The one hard rule: message creators "MUST NOT include more than one" Expires header field in a message.
Rules for mailbox providers and clients
Readers, a term that covers mail clients, webmail and mailbox providers, may de-emphasize expired messages or stop displaying them, and may let users define their own actions, such as automatic clean-up rules for particular senders. Two limits apply: software "MUST NOT discard or reject a message based solely on the content of this header field", and it should not delete messages that carry an Expires field unless the mailbox owner has deliberately configured it to.
A signal for display, not for trust
The security section is blunt about abuse. A creator can put any date in the field, so receivers cannot assume it is accurate. The RFC lists the obvious tricks: past dates on spam to discourage reporting and to mislead adaptive filters, near-future dates to push the reader to act fast, and distant future dates to keep a message in the inbox. Its conclusion is that the field can help decide how to display mail but is unlikely to help decide whether a message is wanted or fraudulent.
Publication also does not mean adoption. The RFC describes what readers may do; whether a given mailbox provider or client acts on the header is up to each of them.
What it means for senders
What changes
There is now a standard way to tell receivers when a message expires. Expired mail may be hidden or pushed down by clients that support the header, but it may not be rejected or discarded on that basis alone.
Who is affected
Senders of dated content: flash sales, coupons with an end date, webinar and event invitations, recurring announcements. ESPs and sending platforms that let customers set custom headers.
When
The RFC was published on 30 October 2026. Using the header is optional, and support in mail clients will arrive, if at all, on each vendor's own schedule.
Action checklist
- Pick the right messages. Add Expires only to mail with a real end of validity, such as an offer that ends or an event that has taken place.
- Leave it off lasting mail. Receipts, invoices, account notices and legal messages keep their value after any date, and a client may hide expired mail.
- Use the exact RFC 5322 date format and include a time zone offset, so the date reads the same in every client.
- Send one Expires field only. Check that your ESP template and your own code do not both add one.
- Set an honest date. The RFC names fake dates as an abuse pattern; a date that does not match the content undermines the signal for everyone.
- Test before you rely on it. Send to seed accounts on your main mailbox providers and clients and check how each one treats a message once its date has passed.
Sources
- RFC 10080: Updated Use of the Expires Message Header Field (primary source)
- RFC Editor: RFC 10080 information page, 30 October 2026