Proton Message Expiration Removes Hosted Contents but Not the External Notification Email

Separate the message content from the email that announces it

A person can still see an email containing a link even when the protected message behind that link has expired. When reviewing Proton Mail expiration, identify which object remains visible before describing the feature as failed. The notification and the hosted contents have different lifecycles.

This distinction matters for a support handoff. A screenshot of an old link email establishes that the notification exists. It does not, by itself, establish that the protected contents are still accessible. Equally, a visible expiration setting is not a record of what a particular recipient observed.

The boundary described by Proton

Proton’s official message-expiration guide covers expiring end-to-end encrypted messages, including password-protected messages sent to people outside Proton Mail. The expiration timer starts when the email is sent, rather than when it is read, and the maximum interval is four weeks, or 28 days. Messages do not expire by default.

For an external recipient of a password-protected message, the recipient receives a link to the contents. Proton states that expiration deletes the encrypted message and its attachments, but cannot delete the link email stored outside Proton’s infrastructure. The sender’s message is also removed from the sent folder after expiration.

Map the objects in a fictional handoff

Imagine a team sending a short project note to a recipient who does not use Proton Mail. There are at least two things to describe in the recipient’s experience: the notification in the recipient’s ordinary mailbox and the protected contents opened through its link. The team should not use the same word, email, for both when diagnosing access.

This is a conceptual checklist, not a live delivery test. Do not infer from it that a recipient has or has not made another copy. A claim about access to hosted contents and a claim that no copies exist anywhere require different evidence.

Plan the window around the send time

If a fictional handoff needs two working days for review, account for when the recipient is expected to begin. An interval that begins when a message is sent should not be described as an interval beginning at the recipient’s first reading. Include the intended expiration date in the working notes rather than relying on an informal phrase such as available for a few days.

Before choosing expiration, confirm that the recipient should receive the material at all and that the chosen channel suits the task. Keep any necessary password exchange in an appropriate private process. Do not put passwords or message links into a public troubleshooting post to demonstrate the issue.

Check setup without overstating the result

Proton documents the outgoing setting in the web composer’s ellipsis menu under Expiration time. Choose the date and time, identify a non-Proton recipient when required, and set the choice. Follow the current official instructions for the particular message type rather than assuming every ordinary external email supports the same behavior.

For an observed problem, record the sender’s application, message type, send time, intended expiration and the exact access result. These fields help distinguish a timing misunderstanding from a different access problem. Avoid repeatedly resending sensitive material while those details remain unclear.

Keep the support route and the service distinct

The EmailSupport Proton Mail guide provides broader setup checks and official resources. EmailSupport is operated by Scott Jeppesen and provides independent third-party guidance. Proton’s own documentation and support remain the authority for its feature behavior and account-specific decisions.

Prepared with AI assistance and checked against Proton documentation on October 27, 2026. The scenario is fictional. No encrypted message was sent, no expiration was configured and no recipient mailbox was accessed for this article.