- Source
- fmail
- Access model
- Public inbox
- Upstream retention
- 7 days / 50 messages upstream
- Removal here
- Request source deletion
A public source with a message-count limit
fmail documents public disposable inboxes with both a retention window and a message-count limit. A mailbox can lose older messages when it fills, even if those messages have not reached the time limit. This matters when a test triggers several notifications at once.
For a manual test, send a small, identifiable set of messages and compare their subjects against your expected sequence. Do not treat the oldest visible message as proof that all earlier mail was delivered. The sender’s logs are a better place to investigate missing history.
Seven days and fifty messages are upstream limits
The published source limits are seven days and fifty messages. Neither overrides the one-hour GetaTempMail session. A successful refresh retrieves the provider’s current list and can remove a cached entry that no longer exists there.
GetaTempMail requests source deletion when you delete an fmail message. Deleting a message does not remove any copy held by the sender. If you need an ongoing archive, use a permanent mailbox instead of trying to keep a temporary session open.
A few common questions
Why could an older fmail message disappear?+
Provider expiry, the mailbox capacity limit, or deletion may remove it. The GetaTempMail session also has its own one-hour lifetime.
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.