Create a new inbox, then send a synthetic message from an application you own or are authorized to test. Verify the recipient, subject, readable body, and timestamp. Test both plain text and HTML-only messages, because HaruMail displays readable text rather than the original HTML. Use test codes and fictional names; never include real passwords, payment details, or customer records.
Keep tests small and respect request limits. A successful receive test checks this delivery path at that moment; it does not prove delivery to all providers. Check long-lived account workflows with a permanent test account that you can recover later.
A small, repeatable test
In a service you own or are authorized to test, create one HaruMail address and request one test message containing a unique, non-sensitive marker such as DEMO-2026-01. Check recipient, subject, text and arrival time. Open the message and compare the displayed code with the sender’s test record. HaruMail extracts likely codes from text; a highlighted number is a convenience, not proof that the message is authentic.
Know what this test does not measure
The reader displays plain text and does not render email HTML, load remote images or open attachments. Use dedicated email previews to test responsive layouts and images. One message reaching HaruMail does not measure deliverability to all providers. Keep load tests in infrastructure you control; do not repeatedly create mailboxes or accounts on third-party services. After testing, remove test accounts in your own application and keep only the non-sensitive results you need.
How this guide is maintained
HaruMail publishes these guides based on the service’s implemented behavior and the references below. Examples use fictional data. If a step or explanation is incorrect, send a correction through the contact page without including private email content.