Sign in to a TempMail Cloud account, open Bulk create email addresses, choose 1 to 200 inboxes and select the receiving domains. The result gives each new address its own password. Save the credential list when it appears. These are independent receive-only inboxes owned by your account, not an outbound mailing list.
Set up a batch
- Sign in or create an account. Guest sessions cannot use the bulk creator.
- Open the bulk inbox control on the home workspace or in the profile menu.
- Enter the number of inboxes you actually need, up to 200 in this batch.
- Select one or more available receiving domains. Search the list to narrow the choices.
- Create the inboxes and review the returned count. Copy all credentials to a secure destination before leaving the result.
- Open an address from your account list and use it in an authorized email test.
The account can run additional batches subject to service protections. That is not a promise of unlimited throughput or permission to automate requests without an agreed integration.
Worked example: twelve test cases across three domains
For a QA pass with twelve independent test identities, select twelve inboxes and three available domains. The creator balances the batch across the selected domains, so this example produces four addresses per domain. The order and generated mailbox names are not fixed.
In your test record, assign each returned address to a case such as signup, reset request or delayed confirmation. Keep a separate field for the actual returned address. Do not guess it from a naming pattern or put passwords into screenshots and issue tickets.
| Test requirement | Suggested batch decision | What to record |
|---|---|---|
| Twelve isolated signup cases | Twelve inboxes, one per case | Case identifier and returned address |
| Compare delivery across three domains | Select those three available domains | Domain, request time and arrival outcome |
| Retest one existing identity later | Reopen its owned mailbox | The exact address and test history |
| Let a reviewer inspect messages | Create an appropriate restricted share link | Intended reviewer and when access should end |
Save access and organize the result
The creation result exposes the new plaintext passwords. The server does not later return the original passwords on login. A browser may remember some credentials, but that is not a substitute for a password manager or a controlled test-secret store.
Account-owned inboxes can be opened from your signed-in account without re-entering each mailbox password. Folders organize owned inboxes; they are not permissions, forwarding rules or separate team accounts. See inbox recovery for the distinction between account and mailbox credentials.
Receiving is not sending
Your own application or email provider must send the test messages. TempMail Cloud receives them; it does not provide bulk outbound email, SMS verification or guaranteed delivery from every sender. A clean inbox does not guarantee a website will accept a temporary domain.
Use batches for legitimate QA and other permitted low-risk tasks. Do not create accounts to evade another service's limits or abuse trials. See developer guidance and acceptable use.
If a batch fails
Read the visible error and check the account inbox list before submitting the same batch again. An interrupted browser request does not reliably prove that nothing was created. If the result is unclear, contact support with the approximate time and requested count; do not send the credential list.
To give someone else access to the received test messages, use inbox sharing rather than sending your account password.