- Source
- smails
- Access model
- Mailbox token
- Upstream retention
- 7 days of inactivity upstream
- Removal here
- Request source deletion
A token accompanies the generated address
Creating a smails mailbox returns an address and a mailbox-specific token. GetaTempMail keeps that token on the server and uses it when retrieving messages. You copy only the email address into the form you are testing; there is no reason to paste the token into another website.
This differs from a provider whose public address alone identifies the inbox for reading. A token is an access mechanism, however, not a promise about every aspect of a provider’s privacy or storage practices. Keep lasting account recovery in an inbox you control.
Read through the shared inbox interface
The smails integration normalizes sender, subject, timestamp, and body into the same message view as the other sources. Search and unread filtering work on the messages available in your current session. The preview removes active markup and remote images.
The provider documents cleanup after seven days of inactivity, but GetaTempMail access still ends after one hour. Reloading the browser reconnects an active session; it does not renew it. For repeatable automated testing, use infrastructure whose lifecycle you control rather than relying on this browser session.
A few common questions
Do I need to manage the smails token?+
No. GetaTempMail stores and uses the mailbox token server-side. It is not included in the public page or copied email address.
Does choosing this source extend my GetaTempMail session?+
No. GetaTempMail sessions last one hour. Provider retention and availability are separate from access through this interface.