How do I see email sending history and errors?
If an email is on the bounce list, Hubhus will automatically stop trying to send future emails to that address.
On this page
Jump to any section using the links below
Hubhus provides multiple places to review how emails were sent, delivered, blocked, or bounced.
This article explains all available tools and how to use them to diagnose delivery issues.
1. Check email history directly on the lead
Table of Contents
Every lead has a detailed history panel where you can filter for email activity.
How to open it
Open the lead
Scroll to History
Use the search field at the top
Type “email”, then select:
Emails sent
Delivered at
What you can see
When the email was triggered
Which automation or action sent it
The recipient
The subject line
Delivery result (Delivered / Failed)
Error text (if any)
Whether the email was opened (if email tracking is enabled)
This is the fastest way to confirm whether Hubhus attempted to send the email.
2. Check global email logs for bounce errors
If an email address is invalid or repeatedly rejected by a mail server, Hubhus marks it as bounced.
All bounce information is stored centrally under Account → Email logs.
Where to find bounce logs
Go to Account
Open Email logs
Select Bouncing addresses
What bounce logs show
For each blocked email address you can see:
The failing email address
The bounce message returned by the mail server
When the first rejection happened
All leads that attempted to send to that address
Which emails failed
The exact rejection reason
Common bounce reasons
“User does not exist” — email address misspelled
“Mailbox unavailable” — inbox disabled
“No MX record” — domain cannot receive email
“Connection timed out” — receiving server unavailable
“Policy rejection” — recipient server rejected message (often due to SPF/DKIM)
If an email is on the bounce list, Hubhus will automatically stop trying to send future emails to that address.
3. Enable notifications when emails fail
You can receive automatic notifications when emails fail to deliver.
How to enable
Go to Account → Email logs
Open the Notifications tab
Create or edit a notification rule
You can configure:
Who receives the notification
Notification frequency (e.g. once per hour)
Which campaigns to monitor
Whether to include all emails or only specific ones
This is useful for admins who want to monitor email delivery across the entire organisation.
4. Typical reasons emails fail (based on real Hubhus behaviour)
A. Invalid email
95% of all failures come from:
typos
spaces in the address
domain mistakes (e.g. gmial.com)
Bounce logs will confirm this.
B. Validation issues
Some campaigns have field validation rules that prevent:
automation triggers
email send actions
form submissions
For example:
invalid email format
required fields not filled
number fields containing text
Check the lead history → filter on Validation error.
C. Spam protection rules
Hubhus may block sending if:
max emails per lead is reached
max emails per address (24-hour limit) is exceeded
blacklist/whitelist rules apply
the lead has unsubscribed
These blocks appear in the lead’s History as “Blocked by spam protection”.
D. Domain verification problems
If your sending domain lacks proper DNS configuration, some recipients reject emails.
Check:
SPF
DKIM
DMARC
Domain-related errors are visible in the lead’s history or bounce logs.
5. Summary
You now have three ways to see exactly what happened to any email:
Lead-level history
✔ See what was sent
✔ See triggers
✔ See delivery status
✔ See exact error messages
Account-level bounce logs
✔ Permanent failures
✔ Reasons from the receiving server
✔ All failed attempts per address
Failure notifications
✔ Automatic alerts
✔ Campaign-specific monitoring
These tools combined make it possible to diagnose nearly any email delivery issue.
? Common searches
email setup • send email • email template • automated email
? Also known as
message • notification • mail
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article