Authenticated account
Temporary email sending is a signed-in workflow, not a public anonymous email sender.
Temporary email sending
Send from a temporary email when sending is enabled.
mailfab separates quick receive-only guest inboxes from authenticated workflows. Sending belongs to signed-in accounts and depends on the workspace email service, permissions, and the selected temporary mailbox.
Permission gated
The application keeps sending controls behind account and service configuration boundaries.
Testing use cases
Use sending for controlled QA flows, internal checks, and short-lived product workflows where your account is allowed to send.
How it works
Receive-only and send-capable workflows are different.
A browser-scoped guest inbox is built for quick incoming verification mail. When a workflow needs outbound email, use a signed-in mailbox and make sure the deployment has outbound delivery configured.
- Use guest inboxes for instant receive-only verification checks.
- Use signed-in mailboxes when sending, sharing, API keys, or webhooks are part of the workflow.
- Treat outbound tests as controlled product flows, not anonymous sending.
Responsible use
Do not rely on temporary email for important long-term accounts.
Temporary addresses are useful for verification, QA, and short-lived messages. For account recovery, billing, or permanent identity, use a durable email provider you control.
- Expiry or deletion removes access to that temporary mailbox in Mailfab.
- Password resets sent after expiry will not be available from that inbox.
- Mailfab does not position temporary email as a replacement for permanent personal mail.