// email marketing and newsletters
Native integrationMailazy email verification with pingutil
Mailazy sends your newsletters, automations and behavioral emails through your own SMTP provider, so every bounce from a dead or throwaway subscriber lands on your domain. Connect a pingutil API key on Mailazy's Integrations page and Mailazy checks each contact in the background, marks it Verified, Risky, Unknown or Invalid, and never emails the invalid ones. You then choose per newsletter or automation whether only verified contacts get the send.
Where it connects: Mailazy Integrations page, Email verification card (pingutil)
What goes wrong without it
- Our newsletter list has years of signups in it and every campaign comes back with a pile of bounces on our own SMTP account.
- Bots fill the signup form with throwaway addresses, they join the list, and the welcome automation emails every one of them.
- Someone types gmial.com at signup, the onboarding series bounces on day one, and we never hear from that subscriber again.
What you can do with Mailazy and pingutil
Clean the newsletter list before the next campaign
When you connect the key, choose Check now to verify the contacts you already have, or select contacts on the Contacts page and choose Verify at any time. Invalid contacts move to Contacts, Invalid, drop out of counts and filter-built lists, and no longer count toward your plan's contact limit.
Check automation sign-ups before the first email
With Verify new contacts automatically on (the default), contacts added by your app, a form, the dashboard or an import are checked in the background. A contact who joins a list that starts an automation while still Unverified is checked before the first email goes out.
Send campaigns to verified contacts only
Each newsletter and automation has a Verification setting: Everyone except invalid addresses (the default), Verified contacts only, or Verified and risky contacts. People left out show as Skipped: not verified in the newsletter details, and Mailazy warns you before a send if Unverified contacts are on the list.
Keep throwaway and machine-made signups off the list
pingutil's spam check sends disposable domains and random-looking addresses to Invalid, and shared inboxes such as info@, noreply@ and sales@ to Risky, so a bot wave on your signup form never reaches a campaign.
Set it up
- 1
Create an API key in your pingutil dashboard and copy it (it is shown once).
- 2
In Mailazy, open Integrations in the sidebar and choose Connect on the pingutil card.
- 3
Paste the key and choose Test, then Connect. Mailazy runs one real lookup to test it, and a refused key is not saved.
- 4
Pick Check now to verify the contacts already on your lists, or Only new ones.
- 5
Leave Check that the mailbox exists on Yes for the full check, or set it to No to use only the fast spam check.
- 6
Set each newsletter or automation's Verification option to decide whether Risky and Unknown contacts still get the send.
What to do with each result
| pingutil result | Action in Mailazy |
|---|---|
| category disposable or verdict.is_spam (randomized address) | Mailazy marks the contact Invalid, moves it to Contacts, Invalid, and sends it no newsletter or automation email. |
| verdict.low_trust (info@, noreply@, sales@) | Marked Risky. Left out only when the newsletter or automation is set to Verified contacts only. |
| status invalid, reason mailbox_not_found or mailbox_disabled | Marked Invalid and listed on the Suppressions page as Invalid address. If a real subscriber was wrongly marked, choose Mark verified in the Invalid tab. |
| status risky, reason accept_all or mailbox_full | Marked Risky. Catch-all domains are never reported as valid. |
| status unknown (server would not answer) | Marked Unknown. Decide per newsletter or automation whether Unknown contacts get mail. |
Limits to plan for
- pingutil checks at most 300 mailboxes a day (3,000 a month) per account, and the spam check covers 2,000 lookups a day. Mailazy's docs say that once mailbox checks are used up, contacts that pass the spam check are marked Verified with the reason "Mailbox not checked (daily limit used)", and mailbox checks resume at 00:00 UTC. Those are Free plan limits; Enterprise has custom limits, which matters when you clean a large list.
- Mailazy paces checks to stay under pingutil's 60 requests a minute. Adding a contact never waits for the check, so a new subscriber stays Unverified until its check finishes.
- If pingutil refuses the key three times in a row, Mailazy shows Needs attention and stops checking. Contacts are still added and emailed as usual and stay Unverified until you choose Replace key.
Mailazy documentation
Built into Mailazy.
Common questions
- Do I need to write code to verify subscribers in Mailazy?
- No. Mailazy calls pingutil for you once you paste a pingutil API key on the Integrations page. Your signup forms and app keep creating contacts the way they already do.
- Can I use pingutil and another verifier in Mailazy at the same time?
- No. Mailazy uses one verifier at a time. Connecting a different service disconnects the first one, and statuses already saved on contacts stay.
- Will an automatic check undo a contact I marked verified by hand?
- No. Mailazy shows manual statuses as (marked by you), and automatic checks never overwrite them. A contact you mark verified from the Invalid tab can receive email again and is not checked again.
Stop bad addresses in Mailazy today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Mailazy setup will receive.