How to Verify Emails in Yesware

Yesware CSV Decisions

Yesware imports are sensitive to column structure, so protect the campaign format before and after verification.

Why Verify Your Yesware Contacts

Yesware is a sales engagement tool built as an add-in for Gmail and Outlook. It adds tracking, templates, and multi-step Campaigns to the inbox sales reps already use. Recipients are usually added by uploading a CSV, often one exported from Salesforce, or by pulling contacts directly from the CRM.

The first reason to verify is that Yesware sends through your real mailbox. There is no separate sending service to absorb the impact of bad addresses. When a Campaign hits invalid recipients, those hard bounces are recorded against your own Gmail or Outlook sending reputation, and that reputation decides whether your future email reaches the inbox.

The second reason is the quality of Salesforce data. CRM records accumulate over years, and contacts leave their companies without anyone updating the record. A list exported from Salesforce can include addresses that no longer exist. Verifying before a Campaign filters those out instead of discovering them through bounce reports.

The third reason is mailbox provider thresholds. Gmail and Outlook both watch bounce rates and treat a high rate as a signal of poor list hygiene, which pushes mail toward the spam folder and can trigger sending restrictions. A verified list keeps you well clear of those thresholds. The fourth reason is reliable Campaign metrics. Yesware reports opens and replies, and those numbers only mean something if the first email was actually delivered. Verifying upfront ensures your reporting reflects how real prospects respond, which is what makes testing subject lines and templates worthwhile.

What VeriMails Checks

VeriMails runs each address through a layered verification process, so the recipient list you load into a Yesware Campaign is one you can trust. The email verification process explains how every layer targets a specific reason an address would otherwise bounce.

Syntax validation confirms the address is correctly formatted. MX and DNS checks confirm the domain is real and configured to receive mail, which removes typo domains and dead companies before deeper checks run. The live SMTP handshake connects to the receiving mail server to confirm the individual mailbox exists, which is the strongest single indicator that a Campaign send will be delivered rather than bounced.

VeriMails also performs catch-all detection. A catch-all domain accepts mail for any address at that domain, so the server will not confirm whether one specific mailbox exists. VeriMails reports this as a detection result, not a score, leaving the call to you. Disposable detection flags temporary inbox domains that signal a low-value contact, and role-based detection identifies generic addresses such as info@, sales@, and support@ that perform poorly in one-to-one sales email. VeriMails returns a clear verification result for each address.

Pricing for Yesware Users

VeriMails pricing is straightforward and fits the way sales teams work. Verification starts at $0.0019 per email. A 10,000-credit pack costs $19, which covers a meaningful round of Campaign prep, and credit packs scale up to 5 million credits for $1,499 for larger sales organizations. Use the pricing page to plan the right pack before a Salesforce-sourced export.

If your team prospects on a steady cadence, monthly subscriptions run from $15 per month to $299 per month and often work out cheaper than buying packs as needed. Every new account starts with 100 free credits and no credit card required, so you can verify a sample of your Yesware list and see the results before spending. Credits never expire, so a pack carries over to your next Campaign.

Reading Your Verification Results

When a VeriMails run finishes, every address in your Yesware export carries a clear status, and knowing what each one means helps you decide what to load back into a Campaign. Valid addresses passed every check, including the live SMTP handshake, and are safe to send to. Invalid addresses failed a definitive check, usually because the mailbox does not exist or the domain cannot receive mail, and these are the ones to drop before they bounce.

Catch-all and how to treat it

Catch-all results come from domains configured to accept mail for any address. The server will not confirm whether one specific mailbox exists, so VeriMails reports the address as catch-all detection rather than valid or invalid. Many legitimate companies run catch-all domains, so these are not automatically bad contacts. A common approach for Yesware users is to send to high-value catch-all prospects in a smaller, carefully monitored Campaign while keeping a close eye on the bounce report, and to leave low-priority catch-all addresses out until you have more signal.

Disposable and role-based results

Disposable addresses use temporary inbox domains and rarely belong to a real long-term contact, so they are usually not worth a Campaign slot. Role-based addresses such as sales@ or info@ reach a shared inbox rather than a named person. They are not invalid, but one-to-one sales messaging tends to underperform when it lands in a shared mailbox, so treat them as a lower-priority segment. Sorting your export this way before re-import means each Yesware Campaign goes to the cleanest possible audience.

Workflow Visual

Use this flow to clean Yesware campaign recipients before sending from Gmail or Outlook.

• Export scope: Open the campaign recipient list you intend to reuse or relaunch before exporting; adjacent Gmail workflows can follow the Mixmax guide.
• Matching field: Keep Email in the required first column plus personalization fields used by templates while bulk verification runs.
• Result action: Import valid recipients and hold invalid, catch-all, disposable, and role-based rows for review before the campaign sends from Gmail or Outlook and affects bounce-rate targets.

Step-by-Step

What to Do With Each Result

Yesware Campaigns should be rebuilt from the verified valid file, with review statuses kept separate.

• Valid Put into the Campaign CSV with Email in column A and exact merge-field headings.
• Invalid Exclude and clean the Salesforce or source record before the next export.
• Catch-all Hold for a smaller monitored Campaign only when the account is important.
• Disposable Remove from sales outreach because the inbox is temporary.
• Role-based Review manually; shared inboxes usually do not fit one-to-one sales Campaigns.

Frequently Asked Questions