Reader
Access link is not valid
The code does not match any file
Every MaiPDF link ends in a reading code. This message means we looked that code up and found nothing behind it.
Three things cause it. The link was cut short when it travelled through a chat app or an email client that wraps long URLs. The sender used Replace to point that link at a different file. Or the file has passed its retention window — historical files are removed roughly once every five months.
What to do: copy the link again from the original message rather than retyping it, and check nothing is missing from the end. If it still fails, ask the sender to confirm the link or re-upload.
Reader
You are not authorised to view
The allowance ran out
The link is alive, but it has nothing left to give. A MaiPDF link carries a view count that drops by one every time the document is opened, and it can also carry an expiry date. When either runs out, the reader stops serving the file.
Refreshing will not help, and neither will a different browser — the count is held with the file, not in your browser.
What to do: ask the sender to raise the view count or extend the date. They can do it on the existing link with their modification code, so you do not need a new link.
Reader
Verification code never arrives
Your address may not be on the list
A sender can restrict a document to a list of named addresses. Only those addresses are sent a code — anyone else is simply never mailed, with no message explaining why.
Verification mail is automated and lands in spam more often than it should, so rule that out first.
What to do: check spam and promotions folders. If it is not there, ask the sender which address they authorised — it may be a work address rather than the one you are trying.
Reader
Page loads but stays empty
Usually the network, occasionally us
The reading page loads the document separately from the page itself, so a slow or filtered connection can leave you with a page frame and no document.
Corporate networks and VPNs are the usual culprits — some block the requests the reader needs.
What to do: try a different network, ideally mobile data, and a different browser. If it is empty on both, that is worth reporting — see the last section.