Once Email guides and engineering notes
Reviewed, practical guidance about receive-only temporary email, mailbox safety and the engineering decisions behind Once Email. We publish only material that matches the service users can verify.
Choose a reading path
What do you need to decide?
Start with a practical question, then narrow the full library by topic.
Browse verified guide categories
Choose a topic to find the guides relevant to your task.
18 guides shown
Editor’s picks
Email Verification Codes: A Safer Way to Copy, Check and Use Them
Treat an email verification code as a short-lived secret: confirm the request, inspect the destination, copy only the code and clear it when the task is finished.
Testing and engineeringHow to Use a Temporary Email API Without Building Flaky Tests
A practical design for temporary-email API tests: isolate each run, poll with backoff, identify the right message, protect secrets and always clean up.
Lifecycle and riskTemporary Email Threat Model: What It Protects and What It Does Not
Model the assets, adversaries, protections and limits of a receive-only temporary inbox without confusing address separation with anonymity or message safety.
Latest updates
Batch-download Email Attachments and Unpack Them Locally with UnpackFlow
Use a dedicated folder, verify every browser download, then list, plan and unpack multipart or nested archives locally without uploading them to an online service.
Once Email Engineering
How to Read Received Headers and Trace an Email Delivery Path
Follow Received header fields in the correct order, compare timestamps safely and recognise the limits of hostnames, IP addresses and untrusted trace data.
Once Email EngineeringA Safe Checklist Before Downloading an Email Attachment
Check the request, sender, file name, type and handling environment before downloading an attachment—and know what email previews and scanners cannot prove.
Once Email Engineering
A Privacy-First Decision Tree for Email Sign-Ups
Choose between a permanent address, forwarding alias and temporary receive-only inbox by checking recovery, payments, records, replies and website policy.
Once Email Engineering
Email Testing Checklist for Developers: From Request to Expiry
A practical, authorised checklist for testing sign-up, verification and password-reset email flows without masking delivery defects or weakening security controls.
Once Email Engineering
How to Save Email Test Evidence Without Exposing Secrets
Create useful screenshots, headers and bug reports while removing verification codes, reset tokens, email addresses, identifiers and unrelated personal data.
Once Email EngineeringOnce Email EngineeringService boundariesWhy Some Websites Reject Disposable Email AddressesOnce Email EngineeringService boundariesOnce Email Editorial and Review PolicyOnce Email EngineeringDelivery and authenticationHow to Read SPF, DKIM and DMARC Results in an Email HeaderOnce Email EngineeringDelivery and authenticationPostfix vs Dovecot: Different Roles in a Receiving Email ServerOnce Email EngineeringMessage safetyHow to Inspect Email Links and Tracking Pixels Without Opening ThemOnce Email EngineeringLifecycle and riskHow Long Does a Temporary Email Last? Plan Before It ExpiresOnce Email EngineeringDelivery and authenticationVerification Email Not Arriving? A Safe Troubleshooting ChecklistOnce Email EngineeringService boundariesWhy Once Email Is Receive-Only by DesignOnce Email Engineering