sales-safetymails
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSafetyMails Platform Help
SafetyMails 平台帮助
Help the user with SafetyMails platform questions — from bulk email verification and list cleaning through real-time API validation, Email Finder, integrations, and credit management.
SafetyMails is a Brazil-founded email verification platform with 8,000+ customers and 2B+ emails verified. ISO 27001 certified. Core strengths: bulk list cleaning (up to 2M emails), real-time JavaScript embed for form validation, and B2B corporate email finder.
为用户解答SafetyMails平台相关问题,覆盖批量邮件验证、列表清洗、实时API验证、邮箱查找、集成配置、额度管理等全场景功能。
SafetyMails是一家创立于巴西的邮件验证平台,服务超过8000名客户,累计验证邮件超20亿封,获得ISO 27001认证。核心优势包括:批量列表清洗(单列表最多支持200万封邮件)、用于表单验证的实时JavaScript嵌入功能、B2B企业邮箱查找。
Step 1 — Gather context
步骤1 - 收集上下文信息
Ask the user:
-
What area of SafetyMails do you need help with?
- A) Bulk Email Verification — upload and clean an email list
- B) Real-Time API — JavaScript embed for forms/landing pages
- C) Email Finder — find corporate emails by name + domain
- D) Free Tools — single email verifier, password generator, email name generator
- E) Integrations — RD Station, HubSpot, Mailchimp, Zapier, etc.
- F) Reporting & Analytics — verification result breakdowns
- G) Account & Billing — credits, pricing, plans
- H) Something else — describe it
-
What type of verification or lookup do you need?
- A) One-time list cleaning before a campaign
- B) Ongoing form validation (real-time)
- C) Finding corporate email addresses (Email Finder)
- D) Checking a single email address
- E) Not sure yet
-
What's your goal? (describe your specific objective — e.g., "clean 50K contacts before a Mailchimp campaign", "add real-time validation to a WordPress form", "find emails for 200 prospects")
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
向用户询问以下信息:
-
你需要使用SafetyMails的哪个功能模块?
- A) 批量邮件验证 —— 上传并清洗邮件列表
- B) 实时API —— 为表单/落地页嵌入JavaScript验证功能
- C) 邮箱查找 —— 通过姓名+域名查找企业邮箱
- D) 免费工具 —— 单邮箱验证、密码生成器、邮箱名生成器
- E) 集成功能 —— RD Station、HubSpot、Mailchimp、Zapier等工具集成
- F) 报告与分析 —— 验证结果明细统计
- G) 账户与账单 —— 额度、定价、套餐相关问题
- H) 其他问题 —— 请描述具体需求
-
你需要哪种类型的验证或查询服务?
- A) 营销活动前的一次性列表清洗
- B) 持续的表单实时验证
- C) 查找企业邮箱地址(邮箱查找功能)
- D) 验证单个邮箱地址
- E) 暂不确定
-
你的使用目标是什么?(请描述具体需求,例如:「在Mailchimp营销活动前清洗5万个联系人」、「为WordPress表单添加实时验证功能」、「为200个潜在客户查找邮箱地址」)
**如果用户的请求已经提供了大部分上下文信息,可以直接跳转到对应的处理步骤。**优先基于合理假设(需明确说明假设内容)给出尽可能完善的回答,最后仅询问1-2个最关键的补充问题,不要在收集完全部信息后才回复用户。
Step 2 — Route or answer directly
步骤2 - 转接其他技能或直接解答
If the request maps to a specialized skill, route:
- General deliverability strategy (SPF/DKIM/DMARC, warmup, inbox placement) →
/sales-deliverability - Enrichment strategy across tools (waterfall, CRM hygiene) →
/sales-enrich - Building prospect lists / ICP definition →
/sales-prospect-list - Connecting tools via Zapier/webhooks generically →
/sales-integration
Otherwise, answer directly from platform knowledge using the reference below.
如果用户的需求匹配其他专项技能,请转接对应技能:
- 通用送达率策略(SPF/DKIM/DMARC、域名预热、收件箱 placement、退信管理)→
/sales-deliverability - 跨工具数据丰富策略(流水式数据补充、CRM数据健康度维护、额度优化)→
/sales-enrich - 构建潜在客户列表 / 理想客户画像(ICP)定义 →
/sales-prospect-list - 通过Zapier/ webhook实现通用工具连接 →
/sales-integration
如果不属于以上场景,请参考下方平台知识库直接解答用户问题。
Step 3 — SafetyMails platform reference
步骤3 - SafetyMails平台参考指南
Provide guidance based on the user's area:
根据用户的需求场景提供对应指导:
Bulk Email Verification
批量邮件验证
- What it is: Upload email lists (CSV, TXT, XLS, XLSX, or paste) and SafetyMails runs a 19-step verification algorithm on every address
- Scale: Up to 2M emails per list
- Algorithm checks: Syntax validation, MX record lookup, catch-all/accept-all detection, spamtrap identification, disposable/temporary email detection, role-based address detection (info@, sales@, etc.), domain typo correction, and more (19 steps total)
- Credit cost: 1 credit per email verified
- Turnaround: Processing time depends on list size — small lists (under 10K) typically complete in minutes
- Output: Downloadable results with per-email status and overall list health summary
- Best practices: Remove duplicate emails before uploading to save credits. Segment results by verification status before importing into your campaign tool. Re-verify lists older than 3 months — email addresses decay over time.
- 功能说明:你可以上传CSV、TXT、XLS、XLSX格式的邮件列表,或是直接粘贴邮件内容,SafetyMails会对每个地址执行19步验证算法
- 处理规模:单列表最多支持200万封邮件
- 算法检测项:语法验证、MX记录查询、全收/收所有域名检测、垃圾陷阱识别、一次性/临时邮箱检测、角色型地址检测(info@、sales@等)、域名拼写纠错等,共计19个检测步骤
- 额度消耗:每验证1封邮件消耗1个额度
- 处理时效:处理时间取决于列表规模,1万封以下的小型列表通常几分钟即可完成
- 输出结果:可下载的验证结果文件,包含每封邮件的验证状态和整体列表健康度汇总
- 最佳实践:上传前先删除重复邮件以节省额度;导入营销工具前根据验证状态对结果做分层;超过3个月的列表需要重新验证,邮箱地址的有效性会随时间衰减。
Real-Time API (JavaScript Embed)
实时API(JavaScript嵌入)
- What it is: A JavaScript snippet you embed in forms and landing pages to validate email addresses as users type them, before they enter your database
- Response time: Under 1 second
- How it works: Add the JavaScript embed code to your form page. Configure with your API key (generated at panel.safetymails.com). Customize error messages for invalid emails.
- Use cases: Landing page forms, newsletter signups, registration flows, checkout forms
- Best practices: Always customize error messages to match your brand voice. Use the API to prevent invalid emails from entering your CRM/ESP in the first place — this is cheaper than cleaning lists after the fact.
API documentation note: SafetyMails API docs at docs.safetymails.com are help-center style guides, not a formal REST API reference. There is no comprehensive endpoint-by-endpoint reference with request/response schemas. The primary API surface is the JavaScript embed for form validation. For programmatic bulk verification, use the web panel at panel.safetymails.com or integrations. If the user needs detailed REST API documentation, flag that it may be incomplete and recommend contacting SafetyMails support.
- 功能说明:你可以将JavaScript代码片段嵌入到表单和落地页中,在用户输入时就验证邮箱地址有效性,避免无效地址进入你的数据库
- 响应速度:低于1秒
- 使用方法:将JavaScript嵌入代码添加到你的表单页面,使用你在panel.safetymails.com生成的API密钥完成配置,自定义无效邮箱的错误提示信息
- 适用场景:落地页表单、通讯订阅、注册流程、结算表单
- 最佳实践:始终自定义错误提示信息,使其符合你的品牌调性;优先使用API从源头阻止无效邮箱进入你的CRM/ESP,成本远低于后续清洗列表。
API文档说明:docs.safetymails.com上的SafetyMails API文档是帮助中心风格的指南,不是正式的REST API参考文档,没有包含完整的接口级请求/响应Schema说明。核心API能力是用于表单验证的JavaScript嵌入功能。如果需要程序化批量验证,请使用panel.safetymails.com的网页面板或是集成功能。如果用户需要详细的REST API文档,请告知文档可能不够完善,建议联系SafetyMails官方支持。
Email Finder
邮箱查找
- What it is: B2B corporate email lookup — provide a first name, last name, and company domain, and SafetyMails returns the corporate email address
- Credit cost: 7 credits per found email. 1 credit if the domain is risky/unverifiable. 0 credits if no email is found.
- Auto-verified: Found emails are automatically verified — no need to run a separate verification step
- Best practices: Use for targeted prospecting when you know the person and company. Budget 7 credits per successful lookup when planning credit purchases. Combine with bulk verification for lists that mix known and unknown emails.
- 功能说明:B2B企业邮箱查询服务,你只需要提供联系人的名、姓和公司域名,SafetyMails就会返回对应的企业邮箱地址
- 额度消耗:每成功找到1个邮箱消耗7个额度;如果域名存在风险/无法验证消耗1个额度;未找到邮箱不消耗额度
- 自动验证:查找到的邮箱会自动完成验证,不需要额外执行验证步骤
- 最佳实践:适用于你知晓目标人员和公司的精准拓客场景;采购额度时按每次成功查询消耗7个额度做预算;如果列表中同时包含已知和未知邮箱,可以搭配批量验证功能使用。
Free Tools
免费工具
- Single Email Verifier: Check one email address at a time for free on the SafetyMails website
- Password Generator: Generate secure passwords (utility tool)
- Email Name Generator: Generate professional email address suggestions from a name
- 单邮箱验证:可以在SafetyMails官网免费单次验证单个邮箱地址
- 密码生成器:生成安全密码的实用工具
- 邮箱名生成器:根据姓名生成专业的邮箱地址建议
Reporting & Analytics
报告与分析
- Verification results: Detailed breakdown of your list by status category (valid, invalid, catch-all, disposable, spamtrap, etc.)
- List health score: Overall assessment of list quality
- Use: Review reports to understand the hygiene of your lists and identify patterns (e.g., high spamtrap rate may indicate a purchased or scraped list)
- 验证结果:按状态分类(有效、无效、全收域名、一次性邮箱、垃圾陷阱等)的列表明细统计
- 列表健康度得分:对列表质量的整体评估结果
- 使用建议:通过查看报告了解列表的健康度,识别异常规律(例如垃圾陷阱占比过高可能说明列表是购买或爬取获得的)。
Data Model — Verification Statuses
数据模型 - 验证状态说明
| Status | Meaning | Action |
|---|---|---|
| Valid | Email exists and is deliverable | Safe to send |
| Invalid | Email does not exist or is undeliverable | Remove immediately — sending will hard bounce |
| Catch-All / Accept-All | Domain accepts all addresses — cannot confirm specific mailbox | Include with caution — monitor bounce rates closely |
| Disposable / Temporary | Throwaway email from services like Guerrilla Mail, Mailinator | Remove — these addresses expire quickly and indicate low-intent signups |
| Spamtrap | Known spam trap address maintained by blocklist providers | Remove immediately — sending to spamtraps severely damages sender reputation and can get your domain blocklisted |
| Role-Based | Generic address like info@, sales@, support@ (not a person) | Remove from prospecting lists — these go to shared inboxes, not individuals. OK for transactional email. |
| Syntax Error | Malformed email address (missing @, invalid characters, etc.) | Remove — not a real email address |
| Domain Error | Domain does not exist or has no MX records | Remove — domain cannot receive email |
| 状态 | 含义 | 处理建议 |
|---|---|---|
| 有效 | 邮箱真实存在,可以正常送达 | 可安全发送 |
| 无效 | 邮箱不存在或无法送达 | 立即删除,发送会产生硬退信 |
| 全收/收所有域名 | 域名会接收所有地址的邮件,无法确认具体邮箱是否存在 | 谨慎包含,密切监控退信率 |
| 一次性/临时邮箱 | Guerrilla Mail、Mailinator等服务提供的临时邮箱 | 立即删除,这类地址很快会失效,代表低意向注册 |
| 垃圾陷阱 | 反垃圾邮件机构维护的已知垃圾陷阱地址 | 立即删除,向垃圾陷阱发送邮件会严重损害发件人信誉,可能导致你的域名被拉黑 |
| 角色型地址 | info@、sales@、support@等通用地址(不属于具体个人) | 从拓客列表中删除,这类地址是共享收件箱,不会触达具体个人,可用于事务性邮件发送 |
| 语法错误 | 邮箱地址格式错误(缺少@、包含无效字符等) | 立即删除,不是真实的邮箱地址 |
| 域名错误 | 域名不存在或没有MX记录 | 立即删除,该域名无法接收邮件 |
API Quick Reference
API快速参考
| Feature | Details |
|---|---|
| Primary API surface | JavaScript embed for real-time form validation |
| Auth | API key generated at panel.safetymails.com |
| Docs | docs.safetymails.com (help-center style guides, not REST reference) |
| Response time | <1 second for real-time validation |
| Bulk verification | Via web panel upload or integrations (not a documented REST endpoint) |
| Trial | 1,000 API credits free for 15 days on signup |
| API access requirement | Monthly subscription plan required (not available on pay-as-you-go) |
| 功能 | 详情 |
|---|---|
| 核心API能力 | 用于实时表单验证的JavaScript嵌入 |
| 鉴权方式 | 在panel.safetymails.com生成的API密钥 |
| 文档地址 | docs.safetymails.com(帮助中心风格指南,不是REST接口参考) |
| 响应时间 | 实时验证响应小于1秒 |
| 批量验证 | 通过网页面板上传或集成功能实现,没有公开的REST接口 |
| 试用额度 | 注册后15天内可免费获得1000个API额度 |
| API使用要求 | 需要购买月度订阅套餐,随用随付套餐不支持API功能 |
Integrations
集成支持
| Integration | Type | What it does |
|---|---|---|
| RD Station | Marketing automation | Sync and verify contacts from RD Station |
| SendGrid | ESP | Verify contacts before sending via SendGrid |
| HubSpot | CRM / Marketing | Clean HubSpot contact lists |
| Mailchimp | ESP | Verify Mailchimp audience lists |
| ActiveCampaign | Marketing automation | Clean ActiveCampaign contact lists |
| WordPress | CMS | Plugin for form validation on WordPress sites |
| E-goi | Marketing automation | Sync and verify E-goi contacts |
| Pipedrive | CRM | Verify Pipedrive contact emails |
| Brevo | ESP | Clean Brevo (formerly Sendinblue) contact lists |
| Salesforce | CRM | Verify Salesforce contact/lead emails |
| Zapier | Automation | Connect SafetyMails to 6,000+ apps |
| Make | Automation | Visual automation workflows with SafetyMails |
| n8n | Automation | Self-hosted automation with SafetyMails |
| Pabbly Connect | Automation | Workflow automation integration |
| Pluga | Automation | Brazil-focused integration platform |
| 集成工具 | 类型 | 功能说明 |
|---|---|---|
| RD Station | 营销自动化 | 同步并验证RD Station中的联系人 |
| SendGrid | ESP | 在通过SendGrid发送邮件前验证联系人 |
| HubSpot | CRM / 营销工具 | 清洗HubSpot中的联系人列表 |
| Mailchimp | ESP | 验证Mailchimp的受众列表 |
| ActiveCampaign | 营销自动化 | 清洗ActiveCampaign中的联系人列表 |
| WordPress | CMS | 为WordPress站点提供表单验证插件 |
| E-goi | 营销自动化 | 同步并验证E-goi中的联系人 |
| Pipedrive | CRM | 验证Pipedrive中的联系人邮箱 |
| Brevo | ESP | 清洗Brevo(原Sendinblue)的联系人列表 |
| Salesforce | CRM | 验证Salesforce中的联系人/潜在客户邮箱 |
| Zapier | 自动化工具 | 将SafetyMails连接到6000+应用 |
| Make | 自动化工具 | 搭建SafetyMails可视化自动化工作流 |
| n8n | 自动化工具 | 实现SafetyMails自托管自动化 |
| Pabbly Connect | 自动化工具 | 工作流自动化集成 |
| Pluga | 自动化工具 | 面向巴西市场的集成平台 |
Pricing (as of March 2026 — verify current pricing)
定价(2026年3月版本 —— 请以官方最新定价为准)
| Plan | Price | Credits | Notes |
|---|---|---|---|
| Free signup | $0 | 100 bulk + 1,000 API trial (15 days) | No credit card required |
| Pay-as-you-go | From $7.50 | 1,000 credits | Credits never expire. No API access. |
| Monthly subscription | From $6.80/mo | 1,000 credits | Required for API/real-time access. Also available annually ($68/yr for 1K). |
| Volume (pay-as-you-go) | Tiered | Up to 2M credits | Per-credit cost decreases at higher volumes |
| Volume (subscription) | Tiered | Up to 2M credits/mo | Per-credit cost decreases at higher volumes |
Credit economics:
- Bulk verification: 1 credit = 1 email verified
- Email Finder: 7 credits per found email, 1 credit if domain is risky, 0 if not found
- Real-time API: 1 credit per validation
- API access requires a monthly subscription plan — pay-as-you-go does not include API access
| 套餐 | 价格 | 额度 | 说明 |
|---|---|---|---|
| 免费注册 | $0 | 100个批量验证额度 + 15天1000个API试用额度 | 无需绑定信用卡 |
| 随用随付 | 最低$7.50 | 1000个额度 | 额度永久有效,不支持API访问 |
| 月度订阅 | 最低$6.80/月 | 1000个额度 | 使用API/实时功能必须订阅该套餐,也可选择年付(1000额度每年$68) |
| 大额随用随付 | 阶梯定价 | 最高200万额度 | 额度越高,单额度成本越低 |
| 大额订阅 | 阶梯定价 | 每月最高200万额度 | 额度越高,单额度成本越低 |
额度消耗规则:
- 批量验证:1个额度 = 验证1封邮件
- 邮箱查找:每找到1个邮箱消耗7个额度,域名存在风险消耗1个额度,未找到不消耗
- 实时API:每次验证消耗1个额度
- API访问必须购买月度订阅套餐,随用随付套餐不包含API访问权限
Step 4 — Actionable guidance
步骤4 - 可落地操作指导
Based on the user's specific question, provide step-by-step instructions:
根据用户的具体问题,提供分步操作指引:
Bulk list verification workflow
批量列表验证工作流
- Prepare your list: Remove duplicates. Export as CSV, TXT, XLS, or XLSX with one email per row (or paste directly).
- Upload: Log in at panel.safetymails.com → click "Verify List" → upload file or paste emails.
- Wait for processing: SafetyMails runs the 19-step algorithm on every address. Small lists finish in minutes; large lists (1M+) take longer.
- Review results: Check the breakdown by status (Valid, Invalid, Catch-All, Disposable, Spamtrap, Role-Based, Syntax Error, Domain Error).
- Download clean list: Export only Valid emails for campaigns. Optionally include Catch-All with monitoring.
- Import to your campaign tool: Upload the clean list to your ESP or campaign platform.
- Re-verify regularly: Lists decay — re-verify every 3 months or before any major campaign.
- 准备列表:删除重复内容,导出为CSV、TXT、XLS或XLSX格式,每行仅包含1个邮箱地址(也可直接粘贴内容)。
- 上传列表:登录panel.safetymails.com → 点击「Verify List」 → 上传文件或粘贴邮箱内容。
- 等待处理:SafetyMails会对每个地址执行19步验证算法,小型列表几分钟即可完成,100万以上的大型列表需要更长时间。
- 查看结果:查看按状态分类的统计结果(有效、无效、全收域名、一次性邮箱、垃圾陷阱、角色型地址、语法错误、域名错误)。
- 下载干净列表:仅导出有效邮箱用于营销活动,也可选择包含全收域名邮箱并后续监控退信情况。
- 导入营销工具:将清洗后的列表上传到你的ESP或营销平台。
- 定期重新验证:列表有效性会随时间衰减,建议每3个月或大型营销活动前重新验证一次。
Real-time API setup (JavaScript embed)
实时API配置(JavaScript嵌入)
- Get your API key: Log in at panel.safetymails.com → navigate to API settings → generate a key.
- Requires subscription plan: API access is only available on monthly subscription plans, not pay-as-you-go.
- Add JavaScript embed: Copy the JavaScript snippet from your SafetyMails dashboard and add it to your form page's HTML.
- Configure validation: Set which form fields to validate, customize error messages, and define behavior for invalid entries.
- Test: Submit your form with known valid, invalid, and disposable emails to confirm validation works.
- Monitor: Check your SafetyMails dashboard for validation stats and credit consumption.
- 获取API密钥:登录panel.safetymails.com → 进入API设置页面 → 生成密钥。
- 确认套餐权限:API功能仅支持月度订阅套餐,随用随付套餐无法使用。
- 添加JavaScript嵌入代码:从SafetyMails后台复制JavaScript代码片段,添加到表单页面的HTML中。
- 配置验证规则:设置需要验证的表单字段、自定义错误提示信息、定义无效输入的处理逻辑。
- 测试功能:分别用已知的有效、无效、一次性邮箱提交表单,确认验证功能正常工作。
- 监控使用情况:在SafetyMails后台查看验证统计数据和额度消耗情况。
Email Finder workflow
邮箱查找工作流
- Gather prospect info: You need first name, last name, and company domain for each lookup.
- Run the lookup: Use the Email Finder tool in the SafetyMails panel — enter the name and domain.
- Review results: Found emails are auto-verified. Note the credit cost: 7 credits per found email, 1 for risky domains, 0 if not found.
- Budget credits: For a list of 200 prospects, budget up to 1,400 credits (200 x 7) in the best case. Actual cost will be lower if some emails aren't found.
- Export and use: Add found emails directly to your campaign — no separate verification needed.
- 收集潜在客户信息:你需要提供每个查询对象的名、姓和公司域名。
- 执行查询:在SafetyMails后台使用邮箱查找工具,输入姓名和域名。
- 查看结果:查找到的邮箱已经自动完成验证,注意额度消耗规则:每找到1个邮箱消耗7个额度,风险域名消耗1个额度,未找到不消耗。
- 额度预算:如果需要查询200个潜在客户,按最多消耗1400个额度(200×7)做预算,如果部分邮箱未找到,实际成本会更低。
- 导出使用:查找到的邮箱可以直接添加到营销活动中,不需要额外验证。
Gotchas
注意事项
Best-effort from research — review these, especially items about pricing tiers and API limitations that may have changed.
- Don't assume API access comes with every plan. The real-time JavaScript API requires a monthly subscription plan. Pay-as-you-go credits do not include API access. If you only need bulk verification, pay-as-you-go works. If you need form validation or real-time checks, you must subscribe.
- Don't underestimate Email Finder credit cost. At 7 credits per found email, a batch of 500 lookups can cost up to 3,500 credits. Budget accordingly. The upside: you pay 0 credits when an email is not found, and only 1 credit for risky domains.
- Don't expect a full REST API reference. SafetyMails documentation at docs.safetymails.com is help-center style (guides, FAQs, how-tos), not a formal REST API reference with endpoint schemas. The primary programmatic interface is the JavaScript embed for form validation. For bulk verification, use the web panel or integrations rather than trying to build custom REST calls.
- Don't send to Catch-All addresses without monitoring. Catch-All/Accept-All domains accept all emails at the SMTP level — SafetyMails cannot confirm individual mailbox existence. Including these in campaigns is a judgment call: they may be fine, or they may bounce. Monitor bounce rates closely if you include them.
- Don't ignore spamtrap results. If SafetyMails flags addresses in your list as spamtraps, take it seriously. Even a single spamtrap hit can get your sending domain blocklisted. A high spamtrap rate in your list likely means the list was purchased, scraped, or hasn't been cleaned in a very long time — consider the source.
基于调研整理的最佳实践,请重点关注可能变动的定价层级和API限制相关内容。
- 不要默认所有套餐都包含API访问权限。实时JavaScript API需要购买月度订阅套餐,随用随付额度不包含API访问权限。如果仅需要批量验证功能,随用随付套餐即可满足需求;如果需要表单验证或实时检测功能,必须购买订阅套餐。
- 不要低估邮箱查找的额度消耗。每找到1个邮箱需要消耗7个额度,500次查询最多可能消耗3500个额度,请提前做好预算。优势是未找到邮箱不消耗额度,风险域名仅消耗1个额度。
- 不要期望有完整的REST API参考文档。docs.safetymails.com上的SafetyMails文档是帮助中心风格(指南、FAQ、操作教程),不是包含接口Schema的正式REST API参考文档。核心的程序化接口是用于表单验证的JavaScript嵌入功能,批量验证建议使用网页面板或集成功能,不要尝试自定义REST请求。
- 不要未经监控就向全收域名地址发送邮件。全收/收所有域名会在SMTP层接收所有邮件,SafetyMails无法确认单个邮箱是否真实存在。是否在营销活动中包含这类地址需要自行判断,可能可以正常发送,也可能产生退信,如果选择包含请密切监控退信率。
- 不要忽略垃圾陷阱检测结果。如果SafetyMails标记列表中的地址为垃圾陷阱,请严肃处理,哪怕仅向1个垃圾陷阱发送邮件都可能导致你的发件域名被拉黑。如果列表中垃圾陷阱占比很高,大概率说明列表是购买、爬取获得的,或是长时间未清洗,请谨慎使用。
Step 5 — Related skills
步骤5 - 相关技能
- — Email deliverability strategy across tools (SPF/DKIM/DMARC, warmup, inbox placement, bounce management)
/sales-deliverability - — Enrichment strategy across tools (waterfall enrichment, CRM hygiene, credit optimization)
/sales-enrich - — Connect SafetyMails to CRM and other tools via Zapier, Make, or direct integrations
/sales-integration - — Build targeted prospect lists with ICP definition and segmentation
/sales-prospect-list - — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
/sales-donpx skills add sales-skills/sales --skills sales-do
- —— 跨工具邮件送达率策略(SPF/DKIM/DMARC、域名预热、收件箱 placement、退信管理)
/sales-deliverability - —— 跨工具数据丰富策略(流水式数据补充、CRM数据健康度维护、额度优化)
/sales-enrich - —— 通过Zapier、Make或原生集成将SafetyMails连接到CRM和其他工具
/sales-integration - —— 结合ICP定义和分层搭建精准潜在客户列表
/sales-prospect-list - —— 不确定使用哪个技能?路由工具会将任何销售目标匹配到对应的技能。安装命令:
/sales-donpx skills add sales-skills/sales --skills sales-do
Examples
示例
Example 1: Cleaning an email list before a Mailchimp campaign
示例1:Mailchimp营销活动前清洗邮件列表
User says: "I have 25,000 contacts in Mailchimp and want to verify them before sending a product launch email"
Skill does:
- Recommends exporting the Mailchimp audience as CSV
- Walks through uploading to SafetyMails for bulk verification (25,000 credits needed)
- Explains how to interpret results — remove Invalid, Spamtrap, Disposable, Syntax Error, and Domain Error
- Advises on handling Catch-All addresses (include with bounce monitoring or exclude for safety)
- Points to the Mailchimp integration as an alternative to manual export/import Result: Clean, verified list re-imported to Mailchimp with invalid and risky addresses removed
用户提问:「我在Mailchimp中有25000个联系人,想在发送产品发布邮件前验证这些地址」
技能处理逻辑:
- 建议用户将Mailchimp受众导出为CSV文件
- 指导用户上传到SafetyMails做批量验证(需要消耗25000个额度)
- 解释如何解读结果:删除无效、垃圾陷阱、一次性邮箱、语法错误、域名错误的地址
- 给出全收域名地址的处理建议:可以保留并监控退信率,或是为了安全直接排除
- 告知用户可以使用Mailchimp集成功能,省去手动导出导入的步骤 结果:清洗验证后的列表重新导入Mailchimp,已删除无效和高风险地址
Example 2: Adding real-time validation to a landing page form
示例2:为落地页表单添加实时验证功能
User says: "I want to stop fake emails from entering our HubSpot database through our demo request form"
Skill does:
- Confirms a monthly subscription plan is needed for API access
- Walks through generating an API key at panel.safetymails.com
- Shows how to add the JavaScript embed to the landing page form
- Recommends blocking Invalid, Disposable, and Role-Based addresses at the form level
- Suggests custom error messages like "Please enter your corporate email address" Result: Real-time form validation preventing invalid and disposable emails from entering HubSpot
用户提问:「我想阻止虚假邮箱通过 demo 申请表单进入我们的HubSpot数据库」
技能处理逻辑:
- 告知用户需要购买月度订阅套餐才能使用API功能
- 指导用户在panel.safetymails.com生成API密钥
- 展示如何将JavaScript嵌入代码添加到落地页表单中
- 建议在表单层面直接拦截无效、一次性、角色型地址
- 建议自定义错误提示信息,比如「请输入你的企业邮箱地址」 结果:实时表单验证功能生效,阻止无效和一次性邮箱进入HubSpot
Example 3: Finding corporate emails for a prospect list
示例3:为潜在客户列表查找企业邮箱
User says: "I have a spreadsheet with 150 names and company domains — I need to find their email addresses"
Skill does:
- Explains Email Finder: input first name + last name + domain, output is auto-verified corporate email
- Calculates credit budget: up to 1,050 credits (150 x 7) for successful lookups, likely less
- Walks through using the Email Finder in the SafetyMails panel for each prospect
- Notes that found emails are auto-verified — no separate verification step needed
- Points to if the user also needs phone numbers, titles, or company data beyond what SafetyMails provides Result: Verified corporate email addresses for the prospect list, ready for outreach
/sales-enrich
用户提问:「我有一个表格,包含150个姓名和公司域名,我需要找到对应的邮箱地址」
技能处理逻辑:
- 介绍邮箱查找功能:输入名+姓+域名,输出自动验证后的企业邮箱
- 计算额度预算:如果全部查询成功最多消耗1050个额度(150×7),实际消耗通常更低
- 指导用户在SafetyMails后台为每个潜在客户使用邮箱查找功能
- 告知用户查找到的邮箱已经自动验证,不需要额外执行验证步骤
- 如果用户还需要电话号码、职位、公司信息等SafetyMails不提供的数据,引导用户使用/sales-enrich技能 结果:获得潜在客户列表的已验证企业邮箱,可直接用于 outreach
Troubleshooting
故障排查
High percentage of Catch-All results
全收域名结果占比过高
Symptom: A large portion of your list comes back as Catch-All/Accept-All, making it hard to judge list quality
Cause: Many corporate domains configure catch-all mail servers that accept all addresses — SafetyMails (and any verification tool) cannot confirm individual mailbox existence on these domains
Solution: Segment catch-all results separately. For high-value prospects on catch-all domains, include them in campaigns but monitor bounce rates per-send. For bulk campaigns, consider excluding catch-all addresses to protect sender reputation. If most of your list is catch-all, the list may skew toward large enterprises — this is normal.
现象:你的列表中很大一部分验证结果为全收/收所有域名,难以判断列表质量
原因:很多企业域名配置了全收邮件服务器,会接收所有地址的邮件,SafetyMails(以及任何验证工具)都无法确认这类域名下单个邮箱是否真实存在
解决方案:将全收域名的结果单独分层。如果是全收域名下的高价值潜在客户,可以包含在营销活动中,但每次发送都要监控退信率。如果是批量营销活动,为了保护发件人信誉可以考虑排除全收域名地址。如果列表中大部分都是全收域名,可能说明列表的目标以大型企业为主,属于正常情况。
API key not working / "Unauthorized" errors
API密钥不工作 / 「未授权」错误
Symptom: JavaScript embed or API calls return authentication errors
Cause: API key may be invalid, expired, or your account may be on a pay-as-you-go plan (which does not include API access)
Solution: Verify your API key at panel.safetymails.com → API settings. Confirm you are on a monthly subscription plan — pay-as-you-go does not include API access. Regenerate the key if needed. Check that the key is correctly embedded in your JavaScript snippet without extra spaces or line breaks.
现象:JavaScript嵌入或API调用返回鉴权错误
原因:API密钥可能无效、过期,或是你的账户使用的是随用随付套餐(不支持API访问)
解决方案:在panel.safetymails.com → API设置页面验证你的API密钥,确认你使用的是月度订阅套餐,随用随付套餐不支持API访问。如有需要可以重新生成密钥,检查JavaScript代码片段中的密钥是否正确,没有多余空格或换行。
Credits consumed faster than expected
额度消耗速度超出预期
Symptom: Credit balance dropping faster than anticipated, especially when using Email Finder
Cause: Email Finder costs 7 credits per found email (vs. 1 credit per bulk verification). Duplicate emails in uploaded lists also consume credits.
Solution: Deduplicate lists before uploading to avoid paying twice for the same email. Track Email Finder usage separately — 100 successful lookups cost 700 credits. Use the free single email verifier on the SafetyMails website for one-off checks instead of spending bulk credits. Review usage reports in your dashboard to identify where credits are going.
现象:额度余额下降速度比预期快,尤其是使用邮箱查找功能时
原因:邮箱查找每找到1个邮箱需要消耗7个额度(而批量验证仅需1个额度),上传列表中的重复邮件也会额外消耗额度
解决方案:上传列表前先去重,避免为同一邮件重复付费。单独统计邮箱查找的使用量,100次成功查询会消耗700个额度。单次验证可以使用SafetyMails官网的免费单邮箱验证工具,不需要消耗批量额度。查看后台的使用报告,了解额度消耗的具体场景。