Catchall Email Guide
Complete guide on Catchall Email

What Is a Catchall Email?
A catchall email is an email setup that receives all emails sent to any address at your domain and forwards them to one main inbox.
Example:
You own the domain
example.comEmails sent to:
All of them are delivered to one inbox you choose
This is extremely useful for:
Creating many store accounts
Account generators
IMAP verification
Keeping all verification emails in one place
Important Notes Before You Start
There are multiple providers that support catchalls
Some websites may detect certain catchall providers
Example:
Walmart has been reported to detect Namecheap catchalls
Google-based domain forwarding may perform better on some sites
We recommend testing and asking your cook group what works best for the site you’re running
How to Create a Catchall Email (Two Common Methods)
Option 1: Namecheap Catchall Setup
Step 1: Buy a Domain
Go to
https://www.namecheap.comSearch for a domain name you want
If your first choice is unavailable, try:
Adding numbers
Changing extensions (.com, .net, .io, etc.)
Purchase the domain
Step 2: Enable Catchall Forwarding
Log into your Namecheap account
Click your profile icon (top right)
Go to your Domain List
Click Manage next to your domain
Scroll to the Email section
Find Redirect Email
Click Add Catchall
Enter the primary email where all emails should be forwarded
Save the changes
Step 3: Add Catchall to Stellar
Open Stellar
Go to Settings
Find the Catchall field
Enter only the domain name Do not include
@
Example:
Domain:
chase35x.comEnter in Stellar:
chase35x.com
Option 2: Google / Google-Style Domain Catchall
This method is often preferred for better deliverability on certain sites.
Step 1: Buy a Domain
Purchase a domain from a provider that supports email forwarding
Complete the domain checkout
Step 2: Enable Catchall Forwarding
Go to your domain provider dashboard
Navigate to Email Settings or Email Forwarding
Create a forwarding rule:
Alias / Recipient:
*Destination: your main email inbox
Save the changes
The * means all emails sent to this domain will be forwarded.
Step 3: Add Catchall to Stellar
Enter only the domain name into Stellar
Do not include
@
Example:
Domain:
test.bikeEnter in Stellar:
test.bike
How Catchalls Are Used in Stellar
Used for account generators
Used for manual or automated account creation
Used with IMAP for auto-verification
Allows unlimited unique emails like:
All emails still go to one inbox.
Best Practices
Always test your catchall with a real signup email
Make sure forwarding works before a drop
Keep IMAP connected if using auto verification
Ask your cook group which provider works best for each site
Beginner Recommendation
If you’re new:
Start with one catchall domain
Test it on one site first
Pair it with IMAP for smooth verification
Expand once confirmed working
Catchall + IMAP Pairing Guide
Pairing a catchall domain with IMAP allows Stellar to automatically read verification emails and enter codes for you. This is the most reliable and hands-free setup for account creation, logins, and checkout verification.
Why Use Catchall + IMAP Together?
Using both together allows you to:
Create unlimited unique emails from one domain
Receive all verification emails in one inbox
Automatically read verification codes
Reduce manual input during drops
Speed up account creation and logins
This setup is strongly recommended for:
Account generators
Sites that send OTP or verification emails
Faster task startup
Large account setups
Step 1: Create Your Catchall Domain
Before setting up IMAP, make sure:
Your catchall domain is working
Emails sent to
[email protected]are forwarding correctlyAll emails land in one main inbox
If this is not confirmed yet, complete the Catchall Guide first.
Step 2: Choose Your IMAP Inbox
Your IMAP inbox must be:
The inbox receiving all forwarded catchall emails
An email provider that supports IMAP access
Recommended email providers:
Gmail (most common and reliable)
Outlook / Hotmail
Custom domain inboxes with IMAP support
Step 3: Add IMAP Session in Stellar
Open Stellar
Go to Settings
Navigate to the IMAP section
Click Add IMAP Session
Enter your email credentials:
Email address (the inbox receiving catchall mail)
App password or IMAP password (recommended over main password)
Save the IMAP session
Once saved, Stellar can now read verification emails automatically.
Step 4: Verify IMAP Is Working
To confirm your IMAP setup:
Send a test email to:
Check that:
The email arrives in your IMAP inbox
Stellar does not show IMAP connection errors
If the email arrives correctly, your setup is good.
Step 5: Use Catchall Emails in Profiles
When creating Profiles or Accounts:
Use unique emails like:
All emails will still arrive in the same inbox and be read by IMAP.
Step 6: Select IMAP Session in Tasks
When creating tasks:
Find the IMAP Session field
Select the IMAP session you created
Start the task
Stellar will now:
Automatically read verification emails
Automatically enter codes when possible
Reduce or eliminate manual popups
What If You Don’t Select an IMAP Session?
If no IMAP session is selected:
Stellar will prompt you to manually enter verification codes
A window will open when a code is required
You must:
Have Google Chrome installed
Have at least one captcha harvester created
IMAP is optional, but recommended for smoother operation.
Best Practices for Catchall + IMAP
Always test IMAP before a big drop
Keep your inbox clean to avoid delays
Avoid email providers that heavily filter forwarded mail
Use app passwords when possible for better security
Don’t reuse the same exact email for every account
Common Beginner Mistakes to Avoid
Entering the catchall domain with
@in StellarUsing an inbox that doesn’t support IMAP
Forgetting to select IMAP session in tasks
Using the same email address for every account
Not testing verification before drop time
Recommended Setup Summary
For best results:
One catchall domain
One clean IMAP inbox
Unique emails per account
IMAP session selected in all supported tasks
This setup gives you the fastest, cleanest, and most automated experience in Stellar.
Last updated
Was this helpful?