The package page a recipient opens from email

/p/{token} is the first thing a stranger sees. It is a page, not an app — no script, every field encoded, an expired link looks the same as one that never existed. Replying to the email still works after the page does not.

2 min read

Every cold send, and most warm ones, put a link in the notification. That link is /p/ plus a token. It is the first page a stranger sees, and it has to work as a letter, not as an app.

What is on the page

A briefing. Who it is from — a name, an address, a date. The note, the ask, the rest of the structured fields, each encoded so someone else's words cannot become markup.

Nothing sits between the message and the reply box. The assistant pitch is a muted line below the actions, with unsubscribe and a sign-in fact, in that order. Sign-in stays last. It is not the product for a person who opened a letter.

Every result — reply sent, marked as read, could not send — has a way back to the message. The unsubscribe confirmation offers "keep receiving them."

No script, on purpose

This is the one surface that still has none. It is unauthenticated, prefetched by mail scanners, and it renders a stranger's words. Encoding every field is the first layer; refusing to run any script is the second.

The marketing site and the account portal each load one file. This page loads zero. If a feature would need JavaScript here, it does not belong here.

Expired looks like never existed

A token that has aged out and a token that was never issued are the same 404: titled "This link has expired," saying that a reply to the email still works and that the address can sign in. A reply posted to a dead link gets the same page.

"Expired" is the honest word for almost every real arrival. Distinguishing the two would make the page an oracle.

A fetch is not a read

Mail security scanners and link previewers request the URL before any human sees the message. That request is recorded. It is never shown to the sender as "they opened it." Acknowledging is still the deliberate act. Opening this page is not.

After the page dies

Thirty days, typically, then the token no longer renders. Reply to the email for another sixty days past that. Or sign in and use the thread, if you have an account.

The only links in that mail that are meant to be clicked are RelayLink's own. Everything the sender wrote that looked like a link arrived defused.

Tags features email security recipients

Frequently asked questions

Do I need a RelayLink account to open the link?
No. The token is the capability. Sign-in is offered at the bottom as a fact, not as a requirement.
Why does a dead link say "expired" even if I made the URL up?
The service does not distinguish an expired token from one that never existed, and the page does not either. Saying "not found" on one and "expired" on the other would be a way to test tokens.
Does opening the page tell the sender I read it?
No. Mail scanners fetch the URL before anyone sees the message. A fetch is recorded and never shown as evidence of reading. Acknowledging is the act that means that.

Related articles