Test email flows without cluttering a real inbox
Use temporary addresses for authorized software QA, verification messages, and MIME delivery checks.
Keep test cases isolated
Create a separate inbox for each test scenario. Confirm the expected recipient, sender, subject, and delivery order. Use the opaque access token to query messages rather than assuming the address grants access.
Do not include real customer data in fixtures. Verification codes should stay inside the test and should never be recorded in analytics, screenshots intended for sharing, or advertising events.
Test what happens beyond the happy path
Include multipart messages, Unicode subjects, missing text parts, links, blocked images, oversized attachments, and malformed MIME. Check expiration while a delivery is in flight, and confirm that deleting one inbox cannot affect another.
The development-only MIME injection endpoint uses the same parser and storage path as the email worker. It verifies application behavior, but it does not prove that public SMTP routing, MX records, or a real sender will work.
Validate real delivery in staging
Set up a dedicated domain, Cloudflare Email Routing, D1, and R2 for staging. Send a real email from an external provider, confirm it reaches the right inbox, and repeat for an expired and an unallocated address.
Hushymaily is receive-only. It is not an outbound email test service, an SMTP relay, or a method for bypassing another platform’s account limits and anti-abuse controls.
An API that can grow with your app
The versioned REST API and TypeScript client use the same capability model as the browser. The SwiftUI iPhone source uses device-only Keychain storage and shares server-side expiration and retention rules. The app is in development and not yet available on the App Store.
There is no unrestricted developer API plan in Release 1. Automated high-volume use requires a separate authenticated quota model before it can be offered safely.