Summary

  • John Levine and Benjamin Billon's RFC 10080, published in October 2026, makes the email Expires header available for general Internet mail. The older RFC 4021 had registered it while limiting general use.
  • A sender may put a single expiration date on a message. Mail software may change its display after that date, but the standard forbids rejection or discard solely on the header and reserves automatic deletion for a rule deliberately set by the mailbox owner.

The sale ends. The message survives.

Imagine an event invitation whose date passed last week. A mailbox could move it below current invitations. A retailer's old offer could fade from the top of a search. Those are the practical uses Levine and Billon describe. They ask the sender to supply a date because the sender knows when the event or offer ends. They give the reader's software room to decide what to do with that information.

The distinction matters because a sender can write any date it likes. RFC 10080 names two abuses: a spammer could backdate a message to make it less visible before a complaint; another could set an absurdly distant date to keep it conspicuous. A time stamp from the party seeking attention is evidence about that party's claim, not authority over the recipient's records.

The rule is unusually crisp. A message creator must use at most one Expires field. A receiver can de-emphasize or hide an expired message. It must not reject or discard mail on that field alone. Deleting an expired message should follow a mailbox owner's deliberate configuration. The sender owns the advertised shelf life; the recipient owns the shelf.

A standard with an intentionally open end

The IANA registry now labels the mail Expires field standard and cites RFC 10080. That clears a format obstacle, not the operating choices in each mailbox. The RFC says previous implementations and meanings were too varied for a universal expiration action. It defines when a message loses validity while leaving display and retention behavior to recipients.

Levine's IETF profile records a long run of mail and Internet standards work. In this one, his co-authored line is about control. The message can announce that its offer is stale. It cannot reach across the network and empty the other person's bin. A useful next receipt would be a mailbox provider's documented, user-controlled implementation: how expired mail is surfaced, searched and retained after the sender's clock runs out.

Sources: RFC 10080; RFC 4021; IANA Message Headers; John R. Levine's IETF profile.