# InboxAlly Documentation — Full Content > Complete content export for AI indexing. See [llms.txt](https://www.inboxally.com/docs/llms.txt) for a structured overview. > Generated: 2026-06-03 --- ## What are the 2024 Gmail and Yahoo bulk sender requirements? - URL: https://www.inboxally.com/docs/compliance-industry-updates/gmail-and-yahoo-changes-for-bulk-senders-in-2024/ - Section: Compliance & Industry Updates - Last Modified: 2026-03-11 - Description: Gmail and Yahoo now require SPF, DKIM, DMARC, one-click unsubscribe, and low spam rates for senders over 5,000 emails/day. - Keywords: Gmail bulk sender requirements 2024, Yahoo bulk sender changes, email authentication requirements, SPF DKIM DMARC bulk senders, one-click unsubscribe requirement, bulk email compliance > Starting in 2024, Gmail and Yahoo require bulk senders (5,000+ emails/day) to authenticate emails with SPF, DKIM, and DMARC, support easy one-click unsubscribe, and keep spam complaint rates below a strict threshold. Non-compliant senders risk having their emails rejected or routed to spam. In early 2024, Gmail and Yahoo began enforcing new requirements for anyone sending more than 5,000 emails per day: full email authentication (SPF, DKIM, and DMARC), one-click unsubscribe support, and spam complaint rates below a strict threshold. Senders who don't comply risk having their messages rejected outright or filtered to spam. Provider Email Authentication Requirements This comparison shows the bulk sender authentication requirements for Gmail, Microsoft Outlook, and Yahoo Mail — the three providers that collectively handle the majority of consumer and business email. Gmail, Microsoft, and Yahoo bulk sender requirements compared across authentication, spam rates, and enforcement. 1. All three providers require SPF authentication for bulk senders sending 5,000+ emails per day. 2. All three providers require DKIM authentication for bulk senders. 3. All three providers require DMARC with at least p=none policy. 4. Google enforces a two-tier spam rate: 0.1% target with 0.3% hard maximum. Microsoft and Yahoo enforce 0.3% maximum. 5. Google and Yahoo require RFC 8058 one-click unsubscribe. Microsoft strongly recommends it. 6. Non-compliant mail faces rejection or spam filtering depending on provider and violation. Pivotal changes for bulk email senders Come 2024, Gmail and Yahoo are updating their bulk sender requirements to effectively counteract spam. The implications for businesses that rely on email communication are significant, and we at InboxAlly are here to help you navigate these changes. In brief, what's changing? Google and Yahoo will soon require bulk senders - anyone sending over 5,000 emails per day to their networks - to: authenticate their emails securely including use of DMARC simplify the process for unsubscribing keep the spam score of emails below a strict threshold. The ramification of these new changes means for many a pivotal shift in strategy: prioritizing "quality over quantity" in your email outreach. InboxAlly has always championed this approach, advocating for personalized engagement rather than indiscriminate email blasts. Our innovative tools help you significantly increase engagement while adhering to the new daily limits and maintaining your emails’ integrity. In light of these updates, it's essential that your technical settings are set using the current best practices . Email authentication using a Custom Tracking Domain, DKIM, SPF, and DMARC protocols is now more critical than ever to ensure your communication is seen as legitimate, safeguarding your brand's reputation and fostering trust with your receivers. With InboxAlly by your side, you're not alone in monitoring these technical requirements. Our platform can alert you if your campaigns stray towards risky territory, enabling swift corrective actions to protect your sender status. Maintaining a healthy sender reputation and deliverability score is another key strategy to assure your emails reach their intended inboxes. InboxAlly's signature warm-up and deliverability booster service plays an indispensable role here and provides automated notifications to warn you of potential drops in deliverability or increased risks of landing in the spam folder. If you're thinking “this is getting complicated,” don’t worry! We've got you covered with a wide range of material in our extensive knowledge base. It's a must-use resource for anyone serious about maintaining stellar deliverability. InboxAlly is not just a tool—it's your active partner in avoiding the dreaded spam folder for good. As Google and Yahoo roll out their new policies, remember that compliance isn't just about following rules; it's about enhancing how you connect with your audience, building credible and lasting relationships through every email sent. Take the next step to ensure you're ready for the future of email sending with InboxAlly. Reach out to us today, and let's work together to keep your emails effective, compliant, and consistently landing in the inbox where they should. --- ## What is RFC 8058 and why does it matter for bulk email senders? - URL: https://www.inboxally.com/docs/compliance-industry-updates/the-importance-of-rfc-8058-for-bulk-mailer-compliance-and-customer-trust/ - Section: Compliance & Industry Updates - Last Modified: 2026-03-10 - Description: RFC 8058 defines the one-click unsubscribe header now required by Gmail and Yahoo. Non-compliant emails face spam filtering or rejection. - Keywords: RFC 8058 one-click unsubscribe, List-Unsubscribe header, email unsubscribe compliance, Gmail unsubscribe requirements, bulk email sender compliance, one-click unsubscribe standard > RFC 8058 defines the **one-click unsubscribe** standard — a `List-Unsubscribe` header that lets recipients opt out with a single action. Gmail and Yahoo now require RFC 8058 compliance for bulk senders. Non-compliant emails risk higher spam complaint rates, reduced inbox placement, and eventual rejection by major mailbox providers. RFC 8058 defines the one-click unsubscribe mechanism for email — a standardized List-Unsubscribe header that lets recipients opt out of a mailing list with a single action, without navigating to external pages or filling out forms. Gmail and Yahoo now require RFC 8058 compliance for bulk senders, and non-compliant messages risk higher spam complaint rates, reduced inbox placement, or outright rejection. Understanding RFC 8058 Before diving into the need for compliance, let's unpack what RFC 8058 actually is. RFC 8058, also known as "One-Click Unsubscribe," is an email standard that outlines a method for users to easily unsubscribe from mailing lists with a single action. It is designed to enhance user experience and reduce the friction associated with opting out of unwanted communications. Compliant emails include a 'List-Unsubscribe' header with a direct link that, when triggered, sends a signal to the originating server to remove the user from the mailing list. Why Compliance Matters With the adoption of RFC 8058 by major email service providers like Google and Yahoo, compliance has become a non-negotiable aspect of email marketing. These changes, primarily driven by a dedication to improving user experience and cracking down on spam, have significant implications: Sender Reputation: Your sender reputation is pivotal in ensuring your emails make it to your subscribers' inboxes rather than being relegated to the spam folder. Compliance with standards like RFC 8058 signifies to ESPs that you're a responsible sender, willing to respect user preferences. Email Deliverability: ESPs like Google and Yahoo use compliance with standards as factors in their filtering algorithms. By adhering to RFC 8058, you not only facilitate a better experience for your recipients but also boost deliverability rates. Legal Compliance: Regulations such as the CAN-SPAM Act of 2003 and the GDPR mandate clearer, easier unsubscribe options. Non-compliance can result in hefty fines and legal repercussions for your business. Customer Trust: Providing an easy and transparent way to unsubscribe builds trust with your audience, showing that you value their preferences and consent. This can lead to higher engagement rates and a more positive brand image. Implementing RFC 8058 So, how do you go about integrating RFC 8058 one-click unsubscribe into your email campaigns? It starts with understanding your current email service provider's capabilities and ensuring that the 'List-Unsubscribe' header is included in your outgoing emails. Here are a few steps to get you started: Review your ESP’s features and support articles to ensure they offer RFC 8058 compliance. Update your email headers by including a 'List-Unsubscribe' option with a mailto link or a URL directing to the unsubscribe mechanism. Test your email campaigns to verify that the unsubscribe feature is working correctly and is accessible with a single click or minimal user interaction. Monitor user feedback and unsubscribe rates to measure the impact of implementing RFC 8058 on your email campaigns. Remember, as an email marketer, adaptation and respect for evolving standards and user preferences aren't just best practices; they are necessities for sustaining a successful email strategy. Embracing RFC 8058 isn't just about playing by the rules; it's an investment in the integrity of your brand and the longevity of your relationship with your audience. At InboxAlly, we know that compliance can be a complex road to navigate alone. If you're still uncertain about where to begin or seek to optimize your email campaigns further, reach out to us. Our team of email deliverability experts is committed to steering you towards email excellence, achieving impeccable compliance, and fostering trust with your subscribers. Let us help you turn these changes into opportunities to shine in the dynamic world of email marketing. --- ## What are Microsoft Outlook's 2025 bulk sender requirements? - URL: https://www.inboxally.com/docs/compliance-industry-updates/microsoft-outlook-changes-for-bulk-senders-in-2025/ - Section: Compliance & Industry Updates - Last Modified: 2026-03-11 - Description: Starting May 2025, Microsoft requires SPF, DKIM, DMARC, and one-click unsubscribe for Outlook.com, Hotmail, and Live.com senders. - Keywords: Microsoft Outlook bulk sender requirements 2025, Outlook email authentication, Hotmail DMARC requirements, Microsoft one-click unsubscribe, Outlook spam filtering changes, bulk email compliance Outlook > Effective **May 5, 2025**, Microsoft requires high-volume senders targeting Outlook.com, Hotmail, and Live domains to implement SPF, DKIM, and DMARC authentication, use functional From/Reply-To addresses, include one-click unsubscribe, and maintain list hygiene. Non-compliant messages will be routed to Junk, with full rejection planned for future enforcement phases. Effective May 5, 2025, Microsoft will enforce new email authentication and sender best practices for high-volume senders targeting Outlook.com, Hotmail.com, Live.com, and related domains. These changes aim to enhance email security and reduce spam and phishing attacks. Key requirements include: Implementing SPF, DKIM, and DMARC authentication protocols. Ensuring functional and valid "From" and "Reply-To" addresses. Including one-click unsubscribe links in bulk emails. Maintaining list hygiene and transparent mailing practices. Non-compliant messages will initially be routed to recipients' Junk folders, with full rejection of non-compliant emails anticipated in future enforcement phases. Provider Email Authentication Requirements This comparison shows the bulk sender authentication requirements for Gmail, Microsoft Outlook, and Yahoo Mail — the three providers that collectively handle the majority of consumer and business email. Gmail, Microsoft, and Yahoo bulk sender requirements compared across authentication, spam rates, and enforcement. 1. All three providers require SPF authentication for bulk senders sending 5,000+ emails per day. 2. All three providers require DKIM authentication for bulk senders. 3. All three providers require DMARC with at least p=none policy. 4. Google enforces a two-tier spam rate: 0.1% target with 0.3% hard maximum. Microsoft and Yahoo enforce 0.3% maximum. 5. Google and Yahoo require RFC 8058 one-click unsubscribe. Microsoft strongly recommends it. 6. Non-compliant mail faces rejection or spam filtering depending on provider and violation. Detailed Requirements 1. Email Authentication Protocols High-volume senders must ensure the following: SPF (Sender Policy Framework): Publish an SPF record that authorizes your sending IP addresses. DKIM (DomainKeys Identified Mail): Sign outgoing messages with a valid DKIM signature. DMARC (Domain-based Message Authentication, Reporting, and Conformance): Publish a DMARC policy (minimum of p=none) that aligns with your SPF and/or DKIM settings. Note: Proper alignment between the "From" domain and the domains used in SPF and DKIM is crucial for DMARC compliance. 2. Functional Sender Addresses "From" and "Reply-To" Addresses: Must be valid, reflect the true sending domain, and be capable of receiving replies. Microsoft recommends avoiding "no-reply" addresses to ensure transparency and user trust. 3. One-Click Unsubscribe Include a visible and functional one-click unsubscribe link in all bulk or marketing emails, complying with RFC 8058. 4. List Hygiene and Mailing Practices Regularly remove invalid or inactive email addresses to reduce bounce rates and spam complaints. Use accurate subject lines and avoid deceptive headers. Ensure recipients have consented to receive your messages. Enforcement Timeline Starting May 5, 2025: Non-compliant messages will be routed to the Junk folder. Future Enforcement (Date TBD): Microsoft plans to reject non-compliant messages entirely to further protect users. Microsoft Deliverability Monitoring Tools Microsoft provides tools like SNDS and JMRP for limited visibility. JMRP (Junk Mail Reporting Program) What it does: Provides real-time complaint feedback when Microsoft users mark your emails as spam. Why it matters: High complaint rates (>0.3%) are one of the leading causes of deliverability degradation. Action: Enroll your domains and monitor complaints. Remove complainers from your active sending lists immediately. SNDS (Smart Network Data Services) What it does: Provides IP-level data on spam trap hits, complaint rates, traffic volume, and filtering actions. Why it matters: Although Microsoft's new policies are domain-focused, poor IP behavior still impacts acceptance rates. Action: Regularly review SNDS data to detect early signs of trouble (even if your domain reputation is strong). How InboxAlly Can Help InboxAlly extends beyond Microsoft’s native reporting and provides multiple deliverability advantages for clients facing these new standards: Seed Inbox Monitoring: Get early warning if inbox placement to Outlook users drops. Engagement: Drive positive signals (opens, replies) to boost sender reputation. List Hygene Tools: Build and maintain clean, engaged lists to comply with Microsoft's expectations. Additional Resources Microsoft's Official Announcement RFC 8058 - One-Click Unsubscribe Microsoft Complaint Feedback Programs For personalized assistance in aligning with these new requirements, please contact your InboxAlly representative or visit our support center. --- ## What changed in Yahoo's April 2025 deliverability update? - URL: https://www.inboxally.com/docs/compliance-industry-updates/yahoo-april-2025-deliverability-update/ - Section: Compliance & Industry Updates - Last Modified: 2026-03-10 - Description: Yahoo shifted from IP-based to domain-focused filtering in April 2025, disrupting deliverability across all major sending platforms. - Keywords: Yahoo deliverability update 2025, Yahoo domain reputation filtering, Yahoo email going to spam, AOL email deliverability issues, Yahoo IP to domain filtering change > In April 2025, Yahoo shifted from IP-based filtering to a **domain-focused reputation model**, causing widespread deliverability disruptions across all major sending platforms. This affects Yahoo, AOL, AT&T, Verizon, and related domains. If your engagement rates dropped sharply for these domains or you're seeing increased soft bounces, you're likely impacted. In April 2025, Yahoo deployed a significant deliverability update that shifted its filtering logic from IP-based evaluation to a domain-focused model. This change has led to widespread disruptions across all major sending platforms, affecting both dedicated and shared IP pools, regardless of historical sender reputation. Affected domains include: yahoo.com, ymail.com, aol.com, att.net, verizon.net, sbcglobal.net, bellsouth.net, rocketmail.com, frontier.net, cox.net, netscape.com, aim.com If your engagement rates have declined sharply for these domains or if you're seeing an increase in soft bounces or spam placement, you may be impacted by this update. What Changed Domain-Level Reputation Now Primary: Yahoo's filters now heavily prioritize domain reputation over IP reputation. Lower Tolerance for Complaint Rates: Senders exceeding a 0.3% spam complaint threshold are far more likely to be filtered. Increased Scrutiny of Monetized Content: Campaigns with affiliate links, aggressive tracking, or promotional-heavy templates are receiving higher filtering rates. Broad Impact Across Platforms: Deliverability issues have been reported on all infrastructure providers. Recommended Response Strategy 1. Do Not Panic — Do Not Fully Pause Sending We recommend a controlled adjustment in order to maintain high-quality engagement activity. Suppress disengaged Yahoo addresses immediately. Continue sending to recent, highly engaged Yahoo users to preserve your domain reputation. Focus on maintaining consistent, predictable mail streams. 2. Tighten Your Segments For Yahoo-managed domains, send only to recent clickers: Sending Frequency Engagement Window Daily Last 3–5 day clickers 2–3x per week Last 7-day clickers Weekly or less Last 14-day clickers Avoid expanding to "openers" or less-engaged contacts until Yahoo inbox placement normalizes. 3. Optimize Your Content Minimize or remove third-party tracking and affiliate links where possible. Simplify design: prioritize text-based layouts with fewer images. Maintain a healthy text-to-image ratio. Use clear, straightforward subject lines without heavy promotions. 4. Monitor Deliverability Signals Closely Use InboxAlly’s deliverability monitoring to: Track inbox vs. spam folder placement specifically for Yahoo addresses. Catch early signs of deferrals or spam placements as you adjust. 5. Authentication Must Be Perfect Ensure full compliance: SPF: Authorizes your sending IP addresses. DKIM: Provides a verifiable signature for message integrity. DMARC: Instructs Yahoo on handling authentication failures. SPF, DKIM, and DMARC must be aligned properly with your sending domain; misalignment will exacerbate filtering under Yahoo’s new model. How InboxAlly Helps InboxAlly users have an advantage in recovering and maintaining deliverability: Seed Testing: Early warning if Yahoo placement shifts. Engagement Boosting: Opens, clicks, and replies provide positive signals for sender reputation during volatile periods. List Hygene: Clean you lists regularly. Final Recommendations Remain calm and be aggressive with list pruning and content adjustments. Expect multi-week effort for deliverability recovery. Be disciplined: patience and precision are critical to long-term inbox recovery. For personalized assistance in adjusting your Yahoo strategy, please contact our support team. --- ## How do I set up an SPF record for my domain? - URL: https://www.inboxally.com/docs/email-authentication-dns/how-to-set-up-an-spf-record-for-your-domain/ - Section: Email Authentication & DNS - Last Modified: 2026-05-29 - Description: Publish a single SPF TXT record that authorizes every sending service, stay under the 10-lookup limit, and verify SPF pass in headers. - Keywords: SPF record setup, how to create SPF record, Sender Policy Framework DNS, SPF TXT record email authentication, SPF 10 DNS lookup limit, fix SPF PermError too many lookups > Publish a single SPF TXT record in your domain's DNS that lists every server authorized to send email on your behalf. SPF tells receiving mail servers which IPs are legitimate, reducing spoofing and improving inbox placement. You can only have one SPF record per domain and are limited to 10 DNS lookups. DNS Records for Email — Complete Map SPF is one of eight DNS records that affect email deliverability. This diagram shows where each record lives, what type it is, and whether it's required. All eight DNS records for email — where they live, what type they are, and whether they're required. 1. SPF: TXT record at @ listing authorized sending servers. 2. DKIM: TXT or CNAME record at selector._domainkey with cryptographic public key. 3. DMARC: TXT record at _dmarc setting authentication policy and reporting address. 4. MX: MX record at @ specifying inbound mail servers. 5. PTR: reverse DNS record set by IP provider mapping sending IP to hostname. 6. MTA-STS: TXT record at _mta-sts enforcing strict TLS for inbound email. 7. TLS-RPT: TXT record at _smtp._tls for TLS failure reporting. 8. BIMI: TXT record at default._bimi for brand logo display in supporting inboxes. SPF record setup is the process of publishing a Sender Policy Framework (SPF) TXT record in DNS that tells receiving mail servers which sending servers are authorized to send email for your domain, helping prevent spoofing and improving inbox placement. In this guide, you’ll first locate any existing SPF TXT record, then build or merge a correct SPF policy that includes every legitimate sender (your mailbox provider, marketing platform, transactional service), publish the final record in DNS, and **verify that messages return an “SPF=pass” result. A few constraints matter from the start: you can have only one SPF record per domain (multiple SPF TXT records cause SPF to fail), and SPF evaluations are limited to 10 DNS lookups—too many include: statements or redirects can trigger PermError and hurt deliverability. Done correctly, SPF reduces authentication failures that lead to spam filtering. For example, a valid SPF record typically starts like: v=spf1 include:example-sender.com ~all What an SPF record is (Sender Policy Framework) and why you need one SPF (Sender Policy Framework) is an email authentication method that tells receiving mail servers which sending sources are allowed to send mail for your domain. You publish this policy as a DNS SPF TXT record. When you send an email, the recipient’s server looks up your domain’s SPF record and checks whether the sending IP address (or sending host) is on the approved list. If it is, SPF can pass; if not, it can fail. A simple SPF TXT record looks like this: example.com. TXT "v=spf1 ip4:203.0.113.10 include:_spf.yourprovider.com -all" What SPF does (and doesn’t do) SPF helps: Reduce spoofing of your domain by blocking unauthorized senders. Improve inbox placement by giving mailbox providers a clear authorization signal (especially when combined with DKIM and DMARC). Support more reliable deliverability testing — tools like InboxAlly’s Domain Reports can track SPF pass rates over time. SPF does not: Encrypt email content (it’s not a privacy mechanism). Prove message integrity (it doesn’t guarantee the message wasn’t altered). That’s DKIM’s job. Authenticate the visible From: header by itself. How SPF is evaluated (MAIL FROM vs From:) and why alignment matters SPF is evaluated against the domain used in the SMTP envelope, commonly shown as the Return-Path (also called MAIL FROM). This domain can be different from the human-visible From: domain in the email header. If the sending IP is authorized by the Return-Path domain’s SPF record → SPF can pass. DMARC later checks whether the authenticated domain (SPF and/or DKIM) aligns with the visible From: domain. That’s why SPF can “pass” but still fail DMARC if the Return-Path domain doesn’t align. For next steps, see How to Configure DMARC Monitoring with InboxAlly. Anatomy of an SPF TXT record: mechanisms, qualifiers, and the “all” rule An SPF TXT record is a single policy string evaluated by receiving mail servers to decide whether the connecting IP is allowed to send for your domain. v=spf1 and common mechanisms (with examples) Every SPF record starts with v=spf1 (the version tag). After that, you list mechanisms that describe allowed senders: include: Authorizes a third party’s SPF policy (common for ESPs and CRMs). Use when a vendor tells you to “add this include.” v=spf1 include:_spf.example-sender.com ~all a Authorizes the IP(s) returned by your domain’s A/AAAA record (or a specified hostname). Use when your web/app server also sends mail. v=spf1 a ~all mx Authorizes the IP(s) of your domain’s MX hosts. Use if your inbound mail servers also send outbound mail. v=spf1 mx ~all ip4: / ip6: Authorizes specific sending IPs or CIDR ranges. Use for dedicated IPs, on-prem servers, or known relays. v=spf1 ip4:203.0.113.10 ip4:203.0.113.0/24 ip6:2001:db8::/32 ~all exists: Performs a DNS lookup and matches if a domain exists. Use only for advanced, dynamic authorization patterns (it’s easy to misconfigure). v=spf1 exists:%{i}._spf.yourdomain.com ~all Qualifiers: +, -, ~, ? (and rollout guidance) Each mechanism can be prefixed with a qualifier: + Pass (default): +a is the same as a. - Fail: Explicitly unauthorized (hard fail). ~ Softfail: “Not authorized, but don’t outright reject.” ? Neutral: No assertion. Practical guidance: Start with ~all during rollout while you confirm every legitimate sender is included (especially if multiple teams/tools send mail). Move to -all once you’ve verified SPF pass rates and you’re confident nothing legitimate is missing. You can use Domain Reports in the InboxAlly app to confirm consistent SPF alignment before tightening policy. Never use +all. It effectively authorizes any server on the internet to send as your domain, enabling spoofing and damaging deliverability. The all mechanism, evaluation order, and result codes SPF is evaluated left-to-right. The first matching mechanism determines the result. all matches everything, so it must be last: v=spf1 ip4:203.0.113.10 include:_spf.example-sender.com -all Common SPF results you’ll see in headers/logs: pass (authorized) fail (hard fail, typically from -all) softfail (from ~all) neutral (from ?all or ? qualifier) permerror (permanent error, e.g., multiple SPF records or >10 DNS lookups) temperror (temporary DNS failure/timeouts) DNS lookup counting (why includes can explode) SPF has a 10-DNS-lookup limit. These mechanisms trigger lookups: include, a, mx, exists (and redirect, if used). ip4/ip6 do not. Includes are the usual culprit: each include: may itself contain more include, a, and mx lookups, quickly exceeding the limit and causing permerror. Keep includes minimal, remove unused senders, and validate changes before rollout. Step-by-step SPF record setup: find your current SPF, create/merge, and publish in DNS 1) Find your current SPF record (TXT) with dig or nslookup SPF is published as a TXT record, usually at the root of your domain (example.com). Start by checking what’s already live. macOS / Linux (dig): dig +short TXT example.com dig +short TXT _spf.example.com Windows (nslookup): nslookup -type=TXT example.com nslookup -type=TXT _spf.example.com How to interpret results You’re looking for a TXT string that starts with v=spf1. Example output: "v=spf1 include:_spf.google.com ip4:203.0.113.10 ~all" Common scenarios: No SPF found: no TXT record contains v=spf1 → you’ll create one. One SPF found: great → you’ll update/merge it as needed. Multiple SPF records found: problem → receivers may treat this as an SPF PermError. You must consolidate to one SPF record at the same hostname. Tip: If you use subdomains for sending (e.g., mail.example.com), check SPF there too. SPF is evaluated on the RFC5321.MailFrom/Return-Path domain, which may differ from your visible “From” domain. 2) Inventory your real sending sources (then map them to SPF mechanisms) Before writing SPF, list every system that sends mail “from” your domain: Mailbox providers: Google Workspace, Microsoft 365 Website/app servers: web host, VPS, on-prem server (contact your dev/IT team for outbound IPs) Marketing/CRM platforms: newsletters, sales automation Transactional providers: receipts, password resets, notifications Support tools: ticketing/helpdesk sending as your domain Then map each source to an SPF mechanism: include: for vendors that publish their own SPF (most SaaS senders) ip4: / ip6: for fixed outbound IPs you control a / mx only if your domain’s A/MX hosts actually send mail (often unnecessary) Example “starter” SPF (replace with your real sources): v=spf1 include:_spf.google.com ip4:203.0.113.10 ~all If you'd rather not hand-write the syntax, our free SPF Record Generator walks you through adding each sender and assembles a single, correctly ordered record for you. Qualifiers matter: ~all (softfail) is a common safe starting point during rollout. -all (fail) is stricter; use when you’re confident all senders are authorized. 3) Merge safely if an SPF record already exists (one record only) If you already have SPF, edit the existing record—don’t add a second one. Safe merge rules Keep v=spf1 first Keep the all mechanism (~all or -all) last Add new senders as additional include: and/or ip4:/ip6: mechanisms Remove duplicates (repeating the same include wastes DNS lookups) Avoid overly broad mechanisms unless you truly need them Before (existing): v=spf1 include:_spf.google.com ~all After (merged with a server IP and another sender include): v=spf1 include:_spf.google.com include:spf.vendor-example.net ip4:203.0.113.10 ~all Note: SPF has a 10 DNS-lookup limit (includes, a, mx, redirect). If you’re close to the limit, remove unused includes first. 4) Publish the SPF TXT record in DNS (generic steps) In your DNS host (registrar, CDN/DNS provider, or managed DNS): Open DNS management for the domain you’re authenticating. Add or edit a TXT record. Set the Host/Name: Use @ or leave blank to target the root (example.com), depending on the DNS UI. Set the Value to your SPF string (single line): v=spf1 include:_spf.google.com ip4:203.0.113.10 ~all Some providers auto-quote; others don’t. Either is fine as long as the published TXT content is correct. Set TTL: 300–3600 seconds is typical. Lower TTL helps faster iteration during setup. Save and wait for propagation: Many changes appear within minutes, but global propagation can take up to 24–48 hours depending on TTL and caching. After publishing, re-run dig/nslookup to confirm the live record matches what you intended. You can also verify SPF status in Domain Reports in the InboxAlly app — it includes an SPF validation check. Once SPF is stable, continue with DKIM and DMARC (see How to Configure DMARC Monitoring with InboxAlly). Adding common ESPs and third-party senders to your SPF record (real examples) When you send mail from multiple systems (your mailbox provider, a marketing platform, a transactional sender, and maybe a web server), they must all be authorized in one SPF TXT record per domain/hostname. Ready-to-use include: snippets (verify vendor docs) Use the provider’s published SPF include(s) and keep them up to date: Google Workspace: include:_spf.google.com Microsoft 365: include:spf.protection.outlook.com Mailchimp: include:servers.mcsv.net SendGrid: include:sendgrid.net Always confirm the current include domains in the vendor’s documentation—providers occasionally change or add includes, and some accounts require additional entries (especially for dedicated IPs). Complete SPF TXT record examples (copy/paste patterns) 1) Google Workspace only example.com. TXT "v=spf1 include:_spf.google.com ~all" 2) Microsoft 365 + website server IP example.com. TXT "v=spf1 include:spf.protection.outlook.com ip4:203.0.113.10 ~all" 3) Google Workspace + Mailchimp example.com. TXT "v=spf1 include:_spf.google.com include:servers.mcsv.net ~all" 4) Microsoft 365 + SendGrid + dedicated IPs example.com. TXT "v=spf1 include:spf.protection.outlook.com include:sendgrid.net ip4:198.51.100.25 ip4:198.51.100.26 -all" Adding multiple services without breaking SPF Keep a single SPF record per hostname (e.g., one for example.com, one for mail.example.com if needed). Multiple SPF TXT records on the same name can cause SPF failures. Order for readability: start with v=spf1, then include: entries, then explicit ip4:/ip6:, end with ~all (soft fail) or -all (hard fail). Minimize includes: remove unused senders and avoid redundant includes. Each include can trigger additional DNS lookups. Watch the 10-DNS-lookup limit: too many includes can cause PermError. If you’re close, reduce includes or consider SPF flattening. Edge cases: subdomains, marketing domains, and return-path Marketing subdomain (recommended): if you send campaigns as news@mail.example.com, publish SPF on that subdomain: mail.example.com TXT "v=spf1 include:servers.mcsv.net ~all" Separate bounce/return-path domain: many senders use a dedicated bounce domain (e.g., bounces.example.com). Publish SPF on the bounce domain too if it sends mail or is used for alignment. When to publish SPF on subdomains: any hostname that appears in the RFC5321.MailFrom/Return-Path or is used as the visible From domain for a distinct stream should have its own SPF record. For best results, pair SPF with DKIM/DMARC (see How to Configure DMARC Monitoring with InboxAlly). Troubleshooting SPF: multiple records, missing includes, and “too many DNS lookups” (PermError) Can I have multiple SPF records on one domain? No. A domain must publish one SPF policy (one v=spf1 string) on the same host. If you publish multiple SPF TXT records (for example, two separate TXT values that both start with v=spf1), many receivers treat the result as SPF PermError because SPF evaluation becomes ambiguous. Fix: merge into a single TXT record that authorizes all legitimate senders. # ✅ One SPF record (merged) @ TXT "v=spf1 include:_spf.google.com include:spf.yourvendor.com ip4:203.0.113.10 -all" Tip: Keep only one v=spf1 record at the root (@) unless you intentionally send from a subdomain (then publish SPF on that subdomain host). Common mistakes (and what they look like) Missing include for a third-party sender Symptom: Some platforms pass SPF, but a specific tool shows SPF=fail or neutral. Fix: Add the vendor’s required include: (or IP ranges) to your single SPF record. Using +all Symptom: SPF “passes” for almost anything, but deliverability suffers and spoofing risk increases. Fix: Use ~all (softfail) during testing, then move to -all when confident. Putting all in the middle Symptom: Anything after all is ignored; legitimate senders still fail. Fix: Ensure ~all/-all is the last mechanism. Publishing SPF on the wrong host Symptom: SPF fails for @yourdomain.com because the record was added to www or another hostname. Fix: Publish at the correct host (@ for the root domain; subdomain for subdomain mail). Forgetting IPv6 (ip6) Symptom: Mail sent from IPv6-enabled infrastructure fails SPF intermittently. Fix: Add required ip6: entries when your sender uses IPv6. Stale vendors / old includes Symptom: You hit lookup limits or authorize senders you no longer use. Fix: Remove unused include: mechanisms. “SPF PermError: too many DNS lookups” explained SPF has a hard limit of 10 DNS lookups during evaluation. These mechanisms count when they trigger DNS queries: include, a, mx, ptr (avoid), exists, and redirect. Lookups can multiply via nested includes (an include that includes others). How to diagnose lookup usage Retrieve your SPF TXT record (dig txt yourdomain.com). Expand each include: and redirect= to see what they reference. Count total lookups across the full chain (including nested records). Check Domain Reports in the InboxAlly app to confirm SPF pass rates aren't dropping or showing PermError spikes after changes. How to stay under the 10-lookup limit Remove unused includes (old CRMs, legacy ESPs, retired sending services). Avoid nested includes where possible; prefer simpler, direct authorization. Replace includes with ip4/ip6 when a vendor provides stable IP ranges (reduces lookups). Use SPF flattening to convert include chains into IP lists. Caution: Flattened IPs change over time—set a maintenance cadence to refresh, or you may break SPF unexpectedly. When you rework the record to trim lookups, rebuild it with the free SPF Record Generator so the merged result stays a single, valid record. After making changes, use Domain Reports in the InboxAlly app to validate that SPF consistently returns Pass, not PermError. How to verify SPF is working (and what to do next with DKIM/DMARC) 1) Verification workflow (DNS → external tests) Confirm DNS is publishing the SPF TXT record Look up the TXT record on the exact domain you send from (root domain or subdomain). You should see one SPF record that starts with v=spf1. Example: yourdomain.com. TXT "v=spf1 include:_spf.google.com ip4:203.0.113.10 ~all" Test the record Use Domain Reports in the InboxAlly app — it includes an SPF validation check that confirms your record is correctly published and passing. You can also send a test email and inspect the headers (see step 2 below). How to interpret results in practice Pass: The sending IP is authorized by your SPF record. This is the expected outcome. Softfail (~): The IP is not authorized, but the policy is “accept but mark.” Many receivers treat repeated softfails as suspicious—fix authorization gaps. Fail (-): The IP is not authorized and the policy is “reject.” If legitimate mail fails, you’re missing an include, ip4/ip6, a, or mx mechanism. PermError: SPF evaluation broke (commonly too many DNS lookups, multiple SPF records, or syntax errors). Receivers may treat this like a fail—reduce lookups and ensure a single SPF TXT record. 2) Validate in real email headers (the definitive check) Send a test email to a mailbox you control, then open the full headers. Look for: Received-SPF: pass|softfail|fail|permerror ... Authentication-Results: ... spf=pass|fail ... dkim=... dmarc=... Confirm the correct domain is being checked SPF is evaluated against the envelope-from/Return-Path domain (not always the visible “From” domain). In headers, verify: Return-Path: (or your ESP’s bounce domain) Authentication-Results: ... spf=pass (domain of bounce@yourdomain.com) 3) Track SPF pass rates over time Authentication issues can undermine your deliverability even when everything else is right. Use Domain Reports in the InboxAlly app to track SPF pass rates, spot sudden drops by sender or source, and validate fixes after DNS changes. If you don't have an account yet, start a free trial to baseline your authentication status. 4) SPF isn’t enough: what to do next Set up DMARC visibility: How to Configure DMARC Monitoring with InboxAlly Add brand indicators after DMARC enforcement: What is BIMI and how to set it up Ensure infrastructure alignment: What is Reverse DNS and why is it important --- ## How do I set up DKIM for my domain? - URL: https://www.inboxally.com/docs/email-authentication-dns/how-to-set-up-dkim-for-your-domain/ - Section: Email Authentication & DNS - Last Modified: 2026-03-12 - Description: Generate a DKIM key pair in your ESP, publish the public key as a DNS record, enable signing, and confirm DKIM pass for DMARC alignment. - Keywords: DKIM setup guide, how to set up DKIM, DKIM DNS record, DomainKeys Identified Mail configuration, DKIM key pair email authentication, DKIM selector and public key > Generate a DKIM key pair in your ESP, publish the public key as a DNS TXT or CNAME record, and enable DKIM signing. DKIM adds a cryptographic signature to each outbound email that proves the message came from your domain and wasn't altered in transit — a major trust signal for inbox placement and a core requirement for DMARC alignment. DNS Records for Email — Complete Map DKIM is one of eight DNS records that affect email deliverability. This diagram shows where each record lives, what type it is, and whether it's required. All eight DNS records for email — where they live, what type they are, and whether they're required. 1. SPF: TXT record at @ listing authorized sending servers. 2. DKIM: TXT or CNAME record at selector._domainkey with cryptographic public key. 3. DMARC: TXT record at _dmarc setting authentication policy and reporting address. 4. MX: MX record at @ specifying inbound mail servers. 5. PTR: reverse DNS record set by IP provider mapping sending IP to hostname. 6. MTA-STS: TXT record at _mta-sts enforcing strict TLS for inbound email. 7. TLS-RPT: TXT record at _smtp._tls for TLS failure reporting. 8. BIMI: TXT record at default._bimi for brand logo display in supporting inboxes. DKIM setup is one of the fastest ways to increase inbox placement because it proves your messages are authentic. DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each outbound email using a private key held by your sender. Receiving servers then fetch your public key from a DKIM DNS record and verify two things: the message really came from your domain and it wasn’t altered in transit. That verification is a major deliverability trust signal. A valid DKIM signature reduces successful spoofing and phishing attempts against your domain, and it also helps your mail pass DMARC (DKIM alignment is a core DMARC requirement). DKIM works best alongside SPF—think of SPF as “who is allowed to send,” and DKIM as “this specific message is intact and signed.” If you’re following our SPF companion guide, DKIM is the next essential authentication layer. In this tutorial, you’ll complete a practical DKIM setup end-to-end: Generate a 2048-bit DKIM key pair in your ESP (and note the selector name). Publish the provided DKIM DNS record as a TXT or CNAME in your domain’s DNS. Enable DKIM signing in the ESP once DNS is in place. Verify DKIM is working by checking message headers (look for DKIM-Signature) and confirming the record with a DKIM lookup tool. What DKIM does (and how it improves deliverability) DomainKeys Identified Mail (DKIM) is an email authentication method that adds a cryptographic signature to each outgoing message. Receiving mailbox providers use that signature to confirm the email is legitimately associated with your domain and hasn’t been altered in transit. What DKIM protects (and what it doesn’t) DKIM primarily protects: Message integrity: the signed parts of the header/body can’t be modified without breaking the DKIM signature. Domain-level authentication: the receiver can verify the message was signed using a private key that matches the public key published in your DKIM DNS record. DKIM does not: Encrypt email content (anyone who can access the message can still read it). Guarantee inbox placement by itself. DKIM is a prerequisite for trust, but inboxing also depends on reputation, engagement, content, and complaint rates. How DKIM improves deliverability Mailbox providers treat DKIM as a strong signal that you control your sending identity. When DKIM passes consistently, providers can: Build domain reputation tied to your authenticated domain (not just an IP). Reduce spoofing/phishing risk by making it harder for attackers to impersonate your domain without access to your DKIM private key. Increase confidence in your mailstream, which supports better filtering outcomes over time. DKIM vs SPF (and why you need both) SPF and DKIM solve different problems: SPF validates where an email is allowed to come from (authorized sending IPs). DKIM validates what was sent (integrity) and who signed it (domain authentication). Best practice is to publish both so receivers have multiple ways to authenticate your mail, improving resilience across forwarding and different sending paths. DKIM’s role in DMARC and BIMI DKIM is a key input to DMARC alignment and enforcement—without DKIM (or SPF) passing and aligning, DMARC can’t reliably protect your domain. See How to Configure DMARC Monitoring with InboxAlly. DKIM is also a prerequisite for BIMI (brand logos in supported inboxes). Learn more in What is BIMI and how to set it up. How DKIM works: keys, signatures, and DNS records Mechanics: keys + signatures in plain terms DomainKeys Identified Mail (DKIM) adds a tamper-evident signature to each outgoing message: Your sending system uses a private key to create a DKIM signature over: selected headers (like From, To, Subject, Date) and the message body (or a canonicalized form of it) The signature is inserted into the email as a DKIM-Signature: header. When the recipient’s mail server receives the message, it: reads the selector and domain from the DKIM-Signature header looks up the matching public key in DNS verifies the signature to confirm the message wasn’t altered in transit and that the signer controlled the domain’s DKIM key. Anatomy of a DKIM DNS record (selector, name, and tags) A DKIM public key is published as a DNS TXT record at: ._domainkey. Where: selector = a label like s1, s2, k1, or provider-specific names (you can have multiple selectors for rotation) _domainkey = fixed namespace for DKIM domain = the domain you’re authenticating Common TXT tags you’ll see: v=DKIM1 — DKIM version k=rsa — key type (RSA is most common) p=... — the Base64-encoded public key (no spaces/quotes inside the key) t=s — optional; “strict” mode (limits subdomain signing) h=sha256 — optional; acceptable hash algorithms Example DKIM record: s1._domainkey.example.com. 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A...IDAQAB" What happens during verification (pass/fail/none) Receivers typically report one of these outcomes: pass: signature validates with the DNS public key. fail: signature is present but doesn’t validate. none: no DKIM signature found (or no usable key record exists). Common failure reasons: Body modified after signing (footers added by gateways, broken line wrapping, link rewriting). Wrong key/selector (signing with s1 but DNS publishes s2, or key was rotated without updating DNS). Missing/invalid DNS record (typos, wrong host name, TXT split incorrectly, propagation not complete). What receivers do with failures depends on their policies and your DMARC settings. Many will downgrade trust, route to spam, or reject when DMARC requires it. Selectors and key length: getting DKIM right the first time What a DKIM selector is (and why you may have more than one) A DKIM selector is the label that tells receivers which public key to fetch from DNS to verify a DKIM signature. You’ll see selectors like s1, s2, google, or k1. The selector becomes part of the DKIM DNS hostname: ._domainkey. Example: s1._domainkey.example.com TXT "v=DKIM1; k=rsa; p=MIIBI...;" You might publish multiple selectors to support: Key rotation (publish s2 before retiring s1) Multiple sending systems/ESPs (each signs with its own selector) Separate streams (marketing vs. transactional) for cleaner operations and audits Key length guidance: 1024 vs 2048-bit Use 2048-bit DKIM keys whenever possible. They’re the modern default and provide stronger cryptographic protection, which supports long-term trust and deliverability. 2048-bit: recommended for new DKIM setup; better security posture 1024-bit: legacy; sometimes required by older providers or DNS limitations If you’re stuck on 1024-bit: Keep it temporary and document why. Plan an upgrade path (new selector + 2048-bit key). Validate signing and alignment after changes using Domain Reports in the InboxAlly app. Operational best practices Rotation strategy: rotate on a schedule (e.g., quarterly/biannually) or after incidents. Publish the new selector first, enable signing, then retire the old record. Naming conventions: use predictable names like mktg2026q1 or tx-s1 to avoid confusion. Avoid selector collisions: don’t reuse generic selectors across vendors; each sender should have a unique selector per domain. Audit-ready records: maintain a simple log (selector, key length, owner system, created/retired dates). DKIM setup steps (works for any ESP): generate keys, publish DNS, enable signing DKIM setup follows the same universal workflow across providers: pick the exact domain you’ll send from, generate DKIM keys in your sending platform, publish the DKIM DNS record, then turn on DKIM signing. 1) Choose the sending domain (or subdomain) Confirm the From domain you’ll use (e.g., example.com) or a dedicated subdomain (e.g., mail.example.com). Decide whether you need separate DKIM for different streams (marketing vs transactional). Many ESPs issue multiple selectors (e.g., s1, s2)—that’s normal. 2) Generate DKIM keys in your ESP/admin console In your ESP, open domain authentication settings and select DKIM. Generate keys (prefer 2048-bit when offered). Copy the provided DNS record(s). You’ll typically receive either: A TXT record containing the public key, or A CNAME record pointing to the ESP’s hosted DKIM key. 3) Publish the DKIM DNS record (TXT vs CNAME) Most DNS providers ask for Name/Host and Value/Target. The “name” is usually the selector plus ._domainkey plus your domain. TXT pattern (public key stored in your DNS): Type: TXT Name/Host: s1._domainkey.example.com Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A... TTL: 3600 CNAME pattern (ESP hosts/rotates the key): Type: CNAME Name/Host: s1._domainkey.example.com Target/Value: s1._domainkey.esp-dkim-provider.net TTL: 3600 Why many ESPs prefer CNAME: it reduces copy/paste errors, avoids TXT length/quoting issues, and lets the ESP rotate keys without requiring you to update DNS. Host/name formatting gotchas: Some DNS UIs auto-append your zone (enter s1._domainkey, not s1._domainkey.example.com). Others require the full FQDN. If verification fails, re-check whether your DNS provider appended the domain twice. For subdomains, the DKIM name still includes the selector and _domainkey, but it must match the sending domain (e.g., s1._domainkey.mail.example.com if you send from mail.example.com). 4) Explicitly enable DKIM signing Publishing DNS isn’t enough. Back in your ESP, ensure DKIM is enabled/active for the correct domain/subdomain. Some platforms keep signing “off” until they detect the record. 5) Timing, propagation, and validation (pre-flight checklist) Propagation: expect 5–60 minutes typically, but allow up to 24 hours depending on DNS and caching. TTL: 300–3600 seconds is common. Lower TTL helps during setup; raise later if desired. Before sending real campaigns: SPF record exists for the same sending domain (see your SPF guide). DKIM record resolves publicly (TXT returns a key, or CNAME resolves to the target). Domain/subdomain matches your From address and ESP configuration. DKIM signing toggle is on. Plan next steps: DKIM is foundational for DMARC (see How to Configure DMARC Monitoring with InboxAlly) and a prerequisite for BIMI. Provider-specific examples: Google Workspace, Microsoft 365, and common ESP patterns Google Workspace (Gmail) Google Workspace uses a TXT-based DKIM record you generate in the Admin Console. In Google Admin Console: Apps → Google Workspace → Gmail → Authenticate email (DKIM). Select your domain, then Generate new record. Key length: choose 2048-bit. Selector: pick something descriptive (common: google, s1, dkim1). You can rotate later by generating a new selector. Publish the TXT record in DNS at: ._domainkey. Return to Admin Console and click Start authentication (DKIM won’t sign until you start it). Realistic TXT record example (format varies by tenant): Host/Name: google._domainkey Type: TXT Value: "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr...IDAQAB" TTL: 3600 Common gotchas: publishing at _domainkey without the selector, splitting the p= value incorrectly, or forgetting to start authentication after DNS is live. Microsoft 365 (Exchange Online) Microsoft 365 typically uses two CNAME-based DKIM selectors and requires you to turn DKIM on after DNS is correct. In the Microsoft 365/Defender portal, locate DKIM for your custom domain. Add the provided CNAME records (usually selector1 and selector2). Wait for DNS propagation, then enable DKIM signing for the domain. Typical CNAME examples: Host/Name: selector1.domainkey Type: CNAME Value: selector1-yourdomain-com.domainkey.yourtenant.onmicrosoft.com. Host/Name: selector2.domainkey Type: CNAME Value: selector2-yourdomain-com.domainkey.yourtenant.onmicrosoft.com. Notes: The destination includes your tenant-specific onmicrosoft.com namespace. If you enable DKIM before the CNAMEs resolve, the portal may show errors or DKIM will remain off. Common ESP patterns (domain authentication wizards) Many email platforms follow a similar flow: a domain authentication wizard issues DNS records to create a branded sending domain (often a subdomain like email.yourdomain.com) and then signs mail with DKIM. What you’ll usually see: CNAME chains: you create a CNAME that points to another hostname, which ultimately resolves to the provider’s DKIM key infrastructure. Multiple records: separate DKIM selectors (e.g., s1, s2) and sometimes additional tracking/return-path CNAMEs. Best practices for multiple sending domains/subdomains: Use one subdomain per stream (e.g., marketing.yourdomain.com, transactional.yourdomain.com) to isolate reputation. Ensure DKIM alignment with your From domain and pair it with DMARC (see How to Configure DMARC Monitoring with InboxAlly). Verify DKIM is working (and troubleshoot common mistakes) 1) Verify by sending a test email and inspecting headers Send a test message from the exact system that should be signing (your ESP, CRM, or SMTP relay) to a mailbox you can inspect (Gmail works well). Open the message original headers and look for: Authentication-Results: (receiver’s verdict) DKIM-Signature: (the signature your sender added) What a pass typically looks like in Authentication-Results: Authentication-Results: mx.google.com; dkim=pass header.i=@example.com header.s=s1 header.b=AbCd... spf=pass smtp.mailfrom=example.com Confirm: You see dkim=pass The signing identity domain (header.i=@example.com) matches the domain you intend to authenticate (ideally the same domain used in your From address for alignment). The selector (header.s=s1) matches the selector you published in DNS. If DKIM-Signature is missing entirely, the sender likely isn’t signing yet (see “forgetting to enable signing” below). 2) Verify the DKIM DNS record is published correctly Use two approaches: Domain Reports (in the InboxAlly app): includes DKIM validation that confirms your record is published and passing. Direct DNS query (for precision): query the exact hostname: s1._domainkey.example.com Expected results: Record type matches your provider’s instructions (TXT or CNAME). The lookup returns a public key (TXT with p=) or a CNAME target that resolves to a TXT containing the key. Example TXT format: s1._domainkey.example.com. 3600 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkq..." 3) Common mistakes (and fixes) TXT vs CNAME confusion: Publish the record type your ESP generated. Don’t convert CNAME instructions into TXT (or vice versa). Wrong host/name: The hostname must include the selector and _domainkey (e.g., s1._domainkey, not just _domainkey). Quoting/line breaks: Keep the p= value intact. If your DNS UI splits strings, ensure it concatenates correctly (no extra spaces/quotes). Multiple records for the same selector: Only one TXT (or one CNAME) should exist per selector hostname. Remove duplicates. Propagation delays: Wait for TTL/propagation, then re-check with direct DNS queries from multiple resolvers. DNS added but signing not enabled: Many platforms require toggling DKIM signing on after publishing DNS. Re-send a test email to confirm DKIM-Signature appears. After DKIM passes, move on to How to Configure DMARC Monitoring with InboxAlly. DKIM is also a prerequisite for BIMI. DKIM alignment, DMARC, and what to do after fixing DKIM issues DKIM alignment (why “DKIM=pass” can still fail DMARC) DMARC doesn’t just check whether DKIM validates—it checks whether the DKIM signing domain aligns with the visible From: domain. DKIM signing domain: the d= value in the DKIM-Signature header (derived from your DKIM DNS record). Visible domain: the domain in the message’s From: header. Alignment modes: Relaxed alignment (default): organizational domains match (subdomains allowed). Example: From: news.example.com aligns with d=example.com. Strict alignment: exact domain match required. Example: From: example.com does not align with d=mail.example.com. Misalignment is a common cause of DMARC failure even when DKIM passes: DKIM: pass (d=send.vendor-mail.com) From: example.com DMARC: fail (no aligned identifier) How DKIM feeds into DMARC (pass conditions + monitoring) DMARC passes when either: SPF passes and aligns, or DKIM passes and aligns If DKIM is fixed but DMARC still fails, confirm: The d= domain aligns with From: Your DMARC policy and reporting are publishing correctly Next steps: Set up reporting using How to Configure DMARC Monitoring with InboxAlly. Not sure if your DKIM is set up correctly? Open the IA Assistant in the InboxAlly app — it can check your authentication status and walk you through any issues. After remediation: rebuild trust and keep auth healthy Once DKIM alignment is corrected: Track ongoing authentication status with Domain Reports in the InboxAlly app (DKIM/SPF/DMARC pass rates over time). If DKIM was broken and you've fixed it, InboxAlly seed emails can help rebuild engagement signals while your reputation recovers. Validate related dependencies like reverse DNS — misconfigured rDNS can still hurt inboxing. See What is Reverse DNS and why is it important. If you don't have an InboxAlly account yet, start a free trial to monitor your authentication status and inbox placement. --- ## How do I set up DMARC monitoring with InboxAlly? - URL: https://www.inboxally.com/docs/email-authentication-dns/how-to-configure-dmarc-monitoring-with-inboxally/ - Section: Email Authentication & DNS - Last Modified: 2026-05-29 - Description: Generate a monitoring-mode DMARC record in InboxAlly, publish it in DNS, and track who sends email from your domain. - Keywords: DMARC monitoring setup, how to set up DMARC, DMARC record configuration, InboxAlly DMARC analytics, email authentication DMARC, DMARC policy none quarantine reject > In InboxAlly, go to **DMARC Analytics** to generate a monitoring-mode DMARC record (`p=none`), publish it as a TXT record in your DNS, and start receiving reports on who is sending email from your domain — including whether those messages pass SPF and DKIM authentication. DMARC monitoring lets you see who is sending email using your domain, whether those messages pass SPF/DKIM authentication, and where problems (like spoofing or misconfiguration) are coming from. In InboxAlly, you can generate a safe “monitoring mode” DMARC record (p=none), publish it in DNS, and then use the DMARC Analytics pane (and Domain Reports for ongoing monitoring) to review compliance trends and drill into failures. Introduction to DMARC How SPF, DKIM, and DMARC work together to authenticate email and determine delivery placement. 1. SPF verification — receiving server checks whether sending IP is authorized by domain's SPF DNS record. 2. DKIM verification — receiving server validates cryptographic signature in email header against DNS public key. 3. DMARC alignment evaluation — checks whether From header domain aligns with domain that passed SPF or DKIM. 4. DMARC policy enforcement when alignment fails: p=none (deliver + report), p=quarantine (spam folder), p=reject (bounce). 5. Authentication results forwarded to filtering system as one signal among many. 6. DMARC aggregate (rua) and forensic (ruf) reports sent back to domain owner. Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a technical standard that helps protect email senders and recipients from spam, spoofing, and phishing. It gives domain owners control over how receiving mail servers should handle messages that claim to be from their domain. The primary outcome of implementing DMARC is improved integrity of email communication—plus visibility into authentication issues and unauthorized use. Understanding DMARC Records A DMARC policy is published as a TXT record in the DNS records for a domain. This TXT record contains the policy that defines how email receivers handle messages from your domain that do not have valid SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) records. If you'd rather assemble the record by hand (or want to understand each tag before you publish), you can build a valid policy with our free DMARC Record Generator — it lets you choose your policy mode (none, quarantine, or reject), set your reporting address, and copy a syntactically correct record to paste into DNS. Setting Up InboxAlly DMARC Monitoring Step 1: Generate a DMARC Record To initiate DMARC monitoring, you will need to generate a DMARC TXT record for your domain. InboxAlly simplifies this process through its user-friendly platform. Log into your InboxAlly account and navigate to the "DMARC Analytics" pane. Select your verified domain from the list presented. Click on "Generate DNS Record" to create your default DMARC TXT record. A record will be produced, resembling: v=DMARC1; p=none; rua=mailto:xxxx@yyyy.com; sp=none; ri=86400; pct=100; adkim=r; aspf=r Here is a breakdown of what each tag means: Field Description v=DMARC1 This indicates the DMARC version in use. p=none This is the DMARC policy. In this case, none specifies a monitoring mode where no action is taken on non-compliant messages. rua=mailto:xxxx@yyyy.com This specifies the email address where aggregate reports should be sent. sp=none This is the subdomain policy, which matches the main domain policy here. ri=86400 This defines the interval for reports in seconds. Here, it's set to once every 24 hours. pct=100 This indicates that the DMARC policy applies to 100% of email messages. adkim=r This defines the alignment mode for DKIM, which can either be r for relaxed or s for strict. aspf=r Like adkim, this defines the SPF alignment mode, which can also be r for relaxed or s for strict. Step 2: Publish the DMARC Record Once you have your DMARC record: Access the DNS management console for your domain. This is usually where you bought your domain name, such as GoDaddy, Namecheap, or your hosting provider. Navigate to the section where you can add new DNS records. Create a new TXT record with the following attributes: Host/Name: _dmarc.yourdomain.com (replace yourdomain.com with your actual domain name) Value: Paste the full DMARC TXT record generated by InboxAlly Save or publish the new record. Step 3: Start Monitoring After the DMARC record is published, it could take up to 48 hours to propagate throughout the internet. Once active, ISPs (Internet Service Providers) that support DMARC will begin sending compliance reports to the email address specified in your DMARC record. InboxAlly will start receiving these DMARC reports and aggregate the data for analysis. For ongoing monitoring of authentication status and domain health, you can also review Domain Reports inside the InboxAlly platform. Analyzing DMARC Reports with InboxAlly Understanding the Summary Report InboxAlly’s dashboard provides you with a comprehensive summary of your email channels' compliance status. Here's what you can expect from the summary report: Compliant Sends: Shows the daily volume of emails from your domain that passed DMARC (i.e., emails that were properly aligned with both SPF and DKIM). SPF / DKIM Non-compliance: Indicates the number or percentage of emails failing SPF and/or DKIM checks, which are important qualifiers for DMARC compliance. In order to dive deeper into non-compliance issues, you have the ability to inspect the details of individual reports within InboxAlly's interface. Interpreting Raw Data Reports For an in-depth analysis, InboxAlly also provides parsed raw data from the DMARC reports in an easy-to-view format. Here's how to interpret this data: Source IP: This field identifies the IP address from which the email was sent. You can use this information to pinpoint the geographical source and potentially identify unauthorized senders. Reporter: The ISP who sent the report Country: The country of the source IP Count: Indicates the number of messages sent from the IP address during the reporting period. SPF: Shows whether the SPF check passed or failed. DKIM: Similarly, this column shows whether the DKIM check passed or failed. Alignment: Reflects whether the message's From domain aligns with the SPF and DKIM domains. This plays a part in determining the overall DMARC compliance. The key is to look for any discrepancies or patterns that indicate unauthorized use of your domain. For example, if you see a source IP that you do not recognize, it may be an indication of spoofing or abuse. Ongoing Management Implementing and monitoring DMARC with InboxAlly is a crucial step towards securing your email ecosystem. It helps you identify and mitigate issues that could damage your brand's reputation and the trust of your recipients. Ongoing management includes: Reviewing DMARC reports regularly (in the DMARC Analytics pane and Domain Reports) Keeping your SPF/DKIM settings current as sending sources change Gradually moving from none to quarantine to reject to enforce stronger security measures over time (after you’ve confirmed legitimate sources are authenticating correctly) By understanding and acting on the data provided by InboxAlly, you're contributing to safer communications and helping uphold the integrity of email as a trusted channel. Getting more from DMARC monitoring with seed emails DMARC reports tell you what authenticated (or failed). Seed emails tell you where messages landed (inbox vs. spam). Used together, they help you diagnose deliverability issues faster and validate improvements. 1) Baselining Before you evaluate real campaign performance, establish a clean baseline: Send seed-only campaigns for several days (no customer/prospect list mail). Keep variables stable (same From address, same sending source, similar content). Use the results as your “known good” reference point for: DMARC pass rates (SPF/DKIM alignment) Consistent sending sources/IPs Inbox vs. spam placement trends This baseline makes it easier to spot when a new sending source, DNS change, or configuration update introduces authentication failures. 2) Correlating seed placement with DMARC reports When you see a placement problem, use DMARC data to narrow down the cause: If seed emails from a specific ESP consistently land in spam and DMARC reports show authentication failures (SPF and/or DKIM misalignment) tied to that same sending source (often visible via Source IP and pass/fail columns) …you can pinpoint the issue to that sending source’s authentication setup (for example, missing DKIM signing, incorrect SPF include, or misaligned From domain). Practical workflow: Identify the failing placement pattern in your seed results (provider, sender, or stream). In DMARC Analytics, filter/drill into the same timeframe. Match the placement issue to DMARC failures by Source IP, SPF/DKIM results, and Alignment. Fix authentication for that source, then re-test and compare against your baseline. 3) Performance benchmarking Use seed inbox placement rates over time as a benchmark to measure the impact of changes, such as: Updating SPF/DKIM records Moving from p=none to quarantine/reject Adjusting sending patterns or content strategy Track trends week-over-week (not just day-by-day). When your authentication and sending strategy improve, you should see: Higher DMARC compliance (fewer SPF/DKIM failures) More consistent inbox placement in seed results Fewer unexplained dips tied to specific sources or providers If you don’t have an InboxAlly account yet, start a free trial to run seed email tests and monitor DMARC results together: Start a free trial of InboxAlly. --- ## What is reverse DNS and why does it matter for email? - URL: https://www.inboxally.com/docs/email-authentication-dns/what-is-reverse-dns-and-why-is-it-important/ - Section: Email Authentication & DNS - Last Modified: 2026-03-12 - Description: Reverse DNS maps your sending IP to a hostname via PTR record. A missing or generic rDNS entry flags spam filters even when SPF/DKIM pass. - Keywords: reverse DNS email, PTR record setup, what is reverse DNS, rDNS email deliverability, reverse DNS lookup sending IP, fix missing PTR record > Reverse DNS (rDNS) maps your sending IP address back to a hostname using a PTR record. Mailbox providers check rDNS during the SMTP connection as a quick trust signal — a missing or generic PTR record is a common spam indicator and can hurt inbox placement even if SPF, DKIM, and DMARC all pass. DNS Records for Email — Complete Map PTR is one of eight DNS records that affect email deliverability. This diagram shows where each record lives, what type it is, and whether it's required. All eight DNS records for email — where they live, what type they are, and whether they're required. 1. SPF: TXT record at @ listing authorized sending servers. 2. DKIM: TXT or CNAME record at selector._domainkey with cryptographic public key. 3. DMARC: TXT record at _dmarc setting authentication policy and reporting address. 4. MX: MX record at @ specifying inbound mail servers. 5. PTR: reverse DNS record set by IP provider mapping sending IP to hostname. 6. MTA-STS: TXT record at _mta-sts enforcing strict TLS for inbound email. 7. TLS-RPT: TXT record at _smtp._tls for TLS failure reporting. 8. BIMI: TXT record at default._bimi for brand logo display in supporting inboxes. Reverse DNS (rDNS) is a lookup that maps an IP address back to a hostname using a PTR (pointer) record. In email, mailbox providers use rDNS as a quick trust signal: the IP you’re sending from should resolve to a sensible hostname that aligns with your sending identity. What reverse DNS / PTR records are (in plain terms) A normal DNS lookup finds an IP from a domain (e.g., mail.example.com → 203.0.113.10). Reverse DNS does the opposite: it finds a hostname from an IP (e.g., 203.0.113.10 → mail.example.com) using a PTR record. PTR records live in the IP owner’s DNS (the “reverse” zone), not in your typical domain DNS zone. Why mailbox providers check reverse DNS Mailbox providers and spam filters commonly check rDNS during the SMTP connection because it helps validate that the sending infrastructure is legitimate and consistently configured. They use it to: Reduce spam and abuse: Many spam sources come from compromised or throwaway servers with missing or generic rDNS. Support the authentication chain: rDNS isn’t a replacement for SPF/DKIM/DMARC, but it complements them as an infrastructure sanity check. Improve traceability: A meaningful hostname is easier to log and investigate than a raw IP address. What providers typically expect: The sending IP has a PTR record (rDNS exists). The PTR points to a hostname that looks intentional (not random). Often (not always), the hostname also has a forward DNS record back to the same IP (this is sometimes called forward-confirmed reverse DNS). If rDNS is missing or clearly misconfigured, some providers will throttle, spam-folder, or reject mail—especially from new or low-reputation IPs. How to check your PTR record You can check rDNS from your own computer in a few seconds. You’ll need the sending IP address (the public IP your mail server or ESP uses). Option 1: dig -x (macOS/Linux) dig -x 203.0.113.10 +short Option 2: nslookup (Windows/macOS/Linux) nslookup 203.0.113.10 Option 3: Online checks (quick verification) If you suspect reputation or blocking issues alongside rDNS problems, run your IP/domain through InboxAlly’s free Spam Database Lookup to see if you’re listed on major blocklists: Spam Database Lookup What “good” looks like: the command returns a hostname (for example, mail.example.com.). What’s concerning: no result (NXDOMAIN), or a generic provider hostname that doesn’t match your sending identity. How to set up or fix reverse DNS (the key detail most senders miss) PTR records are controlled by whoever owns the IP address, not by whoever owns the domain. That usually means: Your hosting provider Your VPS/cloud provider Your ISP Your email service provider (ESP) (if they provide the sending IP) What to do Identify the sending IP Check your mail server configuration, your ESP documentation, or your SMTP relay settings. Determine who owns that IP If you’re on a VPS/dedicated server, it’s typically your VPS provider. If you’re on shared hosting, it’s the hosting company. If you’re using an ESP, it’s usually the ESP (and you may not control rDNS at all). Request a PTR record change from the IP owner Ask them to set the PTR to a hostname you control, commonly something like: mail.yourdomain.com or smtp.yourdomain.com Make sure the hostname resolves forward to the same IP Create an A record in your domain DNS so: mail.yourdomain.com → 203.0.113.10 This alignment helps avoid “reverse/forward mismatch” flags. If you don’t have control of the IP (common with shared hosting or many ESP plans), you typically cannot set rDNS yourself—your best option is to ask the provider what they support or move to an option that includes a dedicated IP. Common reverse DNS problems (and what they mean) Missing PTR record Symptom: dig -x returns nothing / NXDOMAIN. Impact: Higher chance of filtering, throttling, or outright rejection. PTR points to a generic hostname Example: ip-123-45-67-89.provider.com Impact: Not always fatal, but can be a trust negative—especially for cold IPs or strict receivers. PTR mismatch (PTR doesn’t align with your sending domain) Example: You send as @yourdomain.com but rDNS resolves to mail.otherdomain.com. Impact: Can look like spoofing or poor infrastructure hygiene. Forward/reverse mismatch PTR points to mail.yourdomain.com, but mail.yourdomain.com does not resolve back to the sending IP. Impact: Some filters treat this as suspicious. If you’re also seeing deliverability drops, timeouts, or blocks, check whether your IP/domain reputation is contributing. InboxAlly’s Spam Database Lookup can quickly surface blocklist listings, and Domain Reports (in the InboxAlly platform) can help you monitor authentication and reputation signals over time. When reverse DNS matters most (and when it usually doesn’t) It matters most when: You send from a dedicated IP (your own mail server, dedicated SMTP relay, or dedicated IP add-on). You’re warming up a new IP or troubleshooting bounces/blocks. You send higher volume and need consistent infrastructure signals. It usually matters less when: You send through an ESP on a shared IP pool. In that case, the ESP typically manages rDNS for the shared sending IPs, and you won’t be able to change it. Your focus should shift to list hygiene, content, complaint rates, and authentication (SPF/DKIM/DMARC). Shared vs. dedicated IP: what to expect Shared IP rDNS is managed by the provider. You generally can’t (and don’t need to) set PTR records yourself. Deliverability depends heavily on the shared pool’s reputation and your sending behavior. Dedicated IP You (or your provider) should configure rDNS specifically for your sending domain. A clean, matching PTR + forward DNS is a baseline requirement for professional sending. If you’re on a dedicated IP and rDNS is wrong, fix it first—then validate reputation and blocklists using InboxAlly’s Spam Database Lookup and monitor ongoing signals in Domain Reports. --- ## How do I set up a custom tracking domain for email? - URL: https://www.inboxally.com/docs/email-authentication-dns/how-to-set-up-a-custom-tracking-domain-for-email/ - Section: Email Authentication & DNS - Last Modified: 2026-03-10 - Description: Replace your ESP's shared tracking domain with a branded subdomain via CNAME and HTTPS to protect link reputation and boost deliverability. - Keywords: custom tracking domain email, email tracking domain setup, branded click tracking domain, custom link tracking deliverability, CNAME tracking domain DNS > Add a DNS CNAME record pointing a subdomain you control (like `click.yourdomain.com`) to your ESP's tracking host, enable HTTPS/SSL, and configure the custom domain in your ESP settings. This replaces the shared tracking domain so your open/click links align with your sending domain — preventing inherited reputation damage and improving deliverability. A custom tracking domain email setup means your open/click tracking links are rewritten to use a subdomain you control (for example, click.yourdomain.com) instead of a shared, default tracking domain—making it a low-effort, high-impact deliverability lever. When you rely on a provider’s shared tracking domain, your messages can inherit someone else’s poor link reputation; if another sender gets flagged, spam filters may distrust the same tracking host and route your campaigns to junk. Filters also scrutinize link domains for consistency, so branded tracking links that align with your From domain look less suspicious and can improve tracking link deliverability. In this tutorial, you’ll complete a straightforward email tracking domain setup: add a DNS CNAME record for your custom click tracking domain, enable HTTPS/SSL (often required), and confirm everything is working by sending a test email and inspecting the rewritten URLs. The free Email Spam Checker can surface shared tracking-domain risks before you send, and a custom tracking domain fits alongside your authentication stack—see SPF Record Setup, DKIM Setup, and DMARC Monitoring with InboxAlly. What a Tracking Domain Does (and Why Your ESP Rewrites Links) Most ESPs don’t send your original destination URL “as-is.” To measure engagement, they rewrite each link in your email to a tracking URL that points to a redirect service. When a recipient clicks, the redirect service logs the event, then forwards the browser to the final destination. How open and click tracking works Click tracking: Every hyperlink is replaced with a unique, encoded URL. The tracking domain is the domain recipients and spam filters see in the visible link (and in the underlying HTML). Open tracking: A tiny tracking pixel is loaded from a tracking host when images are displayed. (Opens are a signal, not a guarantee—privacy features can block or prefetch.) Simple link mapping example A typical flow looks like this: ESP default tracking link (shared): https://click.esp.com/abc Your custom click tracking domain (branded): https://track.yourdomain.com/abc Final destination: https://yourdomain.com/pricing With a custom tracking domain email setup, step #2 is what appears in the rewritten link, improving brand consistency and reducing “mismatched domain” risk. What’s tracked vs. what filters “see” Tracked (varies by ESP): Total clicks and unique clicks Timestamp, approximate geo/IP, device/client hints User agent and other anti-fraud signals Seen by recipients and filters: The link domain (your tracking domain), its reputation, and whether it aligns with your brand. Tracking domain vs. From domain vs. sending domain From domain: What users see (e.g., news@yourdomain.com) Sending domain: The authenticated infrastructure domain used with SPF/DKIM/DMARC Tracking domain: The domain inside rewritten links Alignment across these domains looks more legitimate to filters and users. Treat your tracking domain as part of your authentication stack alongside SPF record setup, DKIM setup, and DMARC monitoring with InboxAlly. The free Email Spam Checker can also flag shared/default tracking domains that may be dragging down deliverability. Why Default/Shared Tracking Domains Hurt Deliverability Default (shared) tracking domains are the “redirect” domains your ESP uses to rewrite links for click tracking. They’re convenient—but they introduce risk you don’t control. 1) Reputation inheritance you can’t opt out of Shared tracking domains pool many senders under one link domain. If other senders generate spam complaints, hit traps, or get blocklisted, mailbox providers may downgrade the reputation of that tracking domain. Result: your links inherit the penalty, even if your From domain and IP reputation are clean. 2) Spam-filter heuristics flag “generic” redirects Filters evaluate whether the domains in an email align with expected brand identity. Two common trust reducers: Domain mismatch: your visible From domain is brand.com, but links resolve through a generic redirect domain. Redirect patterns: short, non-branded tracking hosts and multi-hop redirects look like phishing infrastructure. Even when the message content is fine, these signals can lower trust and push mail to spam or promotions. 3) Common symptoms of shared tracking-domain issues Watch for patterns like: Strong sender reputation metrics, but unexpectedly poor inbox placement Link-related blocks (clicks fail, security gateways rewrite/quarantine URLs) Sudden spam spikes after switching ESPs or enabling a new tracking feature (because the tracking domain changed) 4) How InboxAlly helps you spot the red flags The free Email Spam Checker surfaces link-domain and redirect issues before you scale a send—highlighting suspicious tracking hosts, mismatches, and deliverability-impacting URL patterns. Use it alongside your authentication stack—SPF, DKIM, and DMARC—to validate trust end-to-end (see SPF Record Setup(#), DKIM Setup(#), and DMARC Monitoring with InboxAlly(#)). Prerequisites and Planning: Pick a Branded Tracking Subdomain + Understand DNS/SSL Requirements Choose a dedicated tracking subdomain (don’t reuse your main host) Use a purpose-built subdomain such as track.example.com or click.example.com for your custom tracking domain email setup. Avoid pointing tracking to your primary website host (e.g., www.example.com) because: Tracking links generate high-volume redirects that can skew web analytics and caching rules. Reputation risk is isolated: if tracking traffic is flagged, it won’t directly impact your main site’s routing and performance. It keeps branding consistent across “From” domain, landing pages, and branded tracking links, which helps tracking link deliverability. The free Email Spam Checker can also surface issues caused by shared/default tracking domains—this is a quick win alongside SPF/DKIM/DMARC (see SPF Record Setup, DKIM Setup, and DMARC Monitoring with InboxAlly). DNS basics: CNAME vs A, TTL, and propagation Most email tracking domain setup flows require a CNAME record (alias) from your tracking subdomain to your ESP’s tracking hostname. Less commonly, an A record points to a fixed IP (harder to maintain if the provider changes infrastructure). TTL: Set 300–3600 seconds during rollout for faster iteration; increase later for stability. Propagation: Expect minutes to 24 hours depending on resolvers and prior TTL. Who controls DNS: DNS may live at your registrar, hosting provider, or a CDN/DNS platform—update records where authoritative nameservers are managed. HTTPS/SSL requirements (custom domain SSL) Many ESPs require HTTPS so tracking redirects aren’t blocked or downgraded by browsers and security filters. “Custom domain SSL” means an SSL certificate is issued for track.example.com and installed/managed by the tracking provider (often automated via ACME/Let’s Encrypt) after your DNS is verified. Operational considerations Pick a name you’ll keep long-term (click/track) and reuse across brands/environments. Confirm the subdomain won’t conflict with existing app routes, proxies, or HSTS rules. Roll out before major sends; allow time for DNS/SSL issuance and verification. Email Tracking Domain Setup (General Steps That Work for Most ESPs) A custom tracking domain email setup is usually a fast, high-impact deliverability win. Most ESPs follow the same pattern: 1) Create a tracking subdomain in your ESP In your ESP’s tracking/link settings, choose Custom click tracking domain (or similar). Enter a subdomain you control (common: click.yourdomain.com or track.yourdomain.com). The ESP will display a target hostname (the destination your CNAME must point to). Copy it exactly. 2) Add the CNAME record in DNS In your DNS provider, create a CNAME for the tracking subdomain. Concrete example (typical format): Type: CNAME Host/Name: click (or click.yourdomain.com depending on provider) Points to/Target: your-esp-tracking-host.example.net TTL: 300 seconds (or “Auto”) Common DNS variations: Some providers want only the subdomain label (click), others require the full hostname (click.yourdomain.com). Some show “Value” instead of “Points to.” If your DNS has a proxy/CDN toggle, set it to DNS-only during verification (proxying often breaks validation/SSL). 3) Enable/issue SSL (HTTPS) Most ESPs require HTTPS for branded tracking links. ESP-managed certificate (recommended): After the CNAME is detected, enable SSL in the ESP and wait for issuance. Bring-your-own certificate: Upload a cert/key bundle for the tracking subdomain and ensure the full chain is included. If SSL validation fails, check: CAA records: If you use CAA, allow the certificate authority your ESP uses (or temporarily remove restrictive CAA). Proxy/CDN settings: Disable proxying until the ESP verifies and issues the cert. Mixed content: Ensure your email templates and landing pages don’t force http:// assets that cause browser warnings. 4) Wait for verification, then test DNS propagation can take minutes to hours; verification may lag. Send a test email and confirm links resolve to your branded domain and redirect cleanly. Best practices for tracking link deliverability Keep redirects minimal (tracking domain → final URL; avoid extra hops). Don’t stack URL shorteners on top of tracking links. Use consistent branding: align From domain, tracking domain, and visible link text. The free Email Spam Checker can flag shared/default tracking domains and other authentication-stack gaps alongside SPF record setup, DKIM setup, and DMARC monitoring with InboxAlly. ESP-Specific Notes (Klaviyo, HubSpot, Mailchimp, SendGrid, and Others): What to Look For in Settings Where the setting typically lives (and what you’ll enter) Most ESPs place custom tracking under Domains, Tracking, Branded links, or Link branding. Expect fields like: Tracking domain / branded link domain (e.g., click.yourdomain.com) Root domain selection (choose the same domain as your From address when possible) Optional toggles for HTTPS/SSL, open tracking, and click tracking What the ESP provides (and how to read it safely) After you enter the subdomain, the ESP usually generates: A CNAME destination (their tracking host/server) you must copy into DNS Sometimes extra records (verification CNAME/TXT, or redirects) Interpret instructions literally: Create the record exactly as shown (host/name vs full domain varies by DNS provider) Don’t add extra A records or “flatten” unless the ESP explicitly supports it Common gotchas by platform Multiple workspaces/accounts: each workspace may require its own tracking domain and CNAME. Region-specific hosts: the CNAME target can differ by data center; don’t reuse values from another account. Prerequisites: some ESPs require a verified sending domain first (part of your authentication stack alongside SPF/DKIM/DMARC). See SPF Record Setup, DKIM Setup, and DMARC Monitoring with InboxAlly. Document it for admins (future-proofing) Capture: Final DNS records (host, type, value, TTL) ESP screenshots of the tracking-domain page A dated change log (who changed what, and why) for migrations/audits InboxAlly’s content testing can also flag shared/default tracking domains that quietly hurt deliverability. Verify It’s Working (and Monitor Ongoing Deliverability) Verification checklist (fast, high-impact) Send a test campaign to a seed list (Gmail, Outlook, Yahoo, and your corporate inbox). Inspect the raw link URLs in the received email: In most clients, right-click a link → Copy link address (or view message source). Confirm the link host matches your branded tracking domain (not a shared/default domain). Confirm the tracking domain appears consistently across all links (CTA buttons, header/footer links, image links). Click through and verify HTTPS: The browser should show a lock icon. No certificate warnings, interstitials, or “Not secure” messages. Technical validation (DNS + SSL + redirects) DNS lookup the CNAME for your tracking subdomain and confirm it resolves to the destination your ESP provided. If you have CLI access: dig CNAME track.yourdomain.com (or nslookup -type=CNAME ...). Confirm the certificate: Visit https://track.yourdomain.com (or a real rewritten link) and check the certificate is valid for that hostname. Confirm redirects resolve quickly: Clicks should land without multiple hops, timeouts, or 4xx/5xx errors. Troubleshooting common issues CNAME typos: wrong hostname, missing trailing dot, or pointing to the wrong target. DNS not propagated: wait for TTL; re-check from multiple networks. CDN/DNS proxying enabled: some proxies break CNAME-based tracking or SSL issuance—set the record to DNS-only if required. SSL issuance delays: certificates can take time after DNS is correct; retry later. Mixed-domain links in templates: hardcoded links (or old templates) may still use the default tracking domain—update templates and re-test. Keep it healthy: deliverability stack + monitoring A custom tracking domain is one piece of your authentication stack alongside SPF, DKIM, and DMARC. See: SPF Record Setup(#), DKIM Setup(#), and DMARC Monitoring with InboxAlly(#). For ongoing performance, pair this with Email Content Best Practices and use the Placement Tester and Email Audit in InboxAlly to catch shared-domain remnants, link mismatches, and placement drops early. Need help setting up your tracking domain? Open the IA Assistant in the InboxAlly app for step-by-step guidance, or start a free trial to test your deliverability. --- ## What is BIMI and how do I set it up? - URL: https://www.inboxally.com/docs/email-authentication-dns/what-is-bimi/ - Section: Email Authentication & DNS - Last Modified: 2026-05-29 - Description: BIMI displays your brand logo in supported inboxes like Gmail. Requires DMARC enforcement, an SVG logo, and an optional VMC certificate. - Keywords: what is BIMI, BIMI email setup, brand logo in email inbox, BIMI DNS record, Verified Mark Certificate VMC, BIMI Gmail logo display > BIMI (Brand Indicators for Message Identification) displays your brand logo next to your emails in Gmail, Yahoo, and Apple Mail. To set it up: enforce DMARC (`p=quarantine` or `p=reject`), create a square SVG Tiny P/S logo (max 32KB), optionally get a VMC from Entrust or DigiCert, then publish a TXT record at `default._bimi.yourdomain.com`. Gmail and Apple Mail require a VMC; Yahoo does not. BIMI (Brand Indicators for Message Identification) is an email standard that displays your brand's verified logo next to your messages in supported inboxes like Gmail, Yahoo Mail, and Apple Mail. It requires DMARC enforcement (p=quarantine or p=reject), an SVG logo in the correct format, and optionally a Verified Mark Certificate (VMC). A Red Sift study found that BIMI resulted in a 90% boost in consumer confidence in sender legitimacy. What is BIMI? BIMI stands for Brand Indicators for Message Identification. It’s an email standard that enables the display of a brand’s official logo next to their message in email inboxes. This innovative email specification offers authenticated senders the ability to represent their brands effectively in messaging services. What are the benefits of BIMI? BIMI is highly beneficial. It enables email marketers to build a strong brand image by placing their logos next to email messages. This one-of-a-kind approach creates a visual connection and brand recognition that’s instrumental to improving deliverability and conversion. This added visibility also helps protect users from fraudulent emails, such as phishing or spoofing attempts. In a nutshell, BIMI is the email standard of choice if you’re looking to reinforce brand credibility and improve deliverability. How Does BIMI Work? To implement BIMI, you’ve to create and publish a new DNS (Domain Name System) record that contains your BIMI TXT record. When a BIMI-supporting email service provider receives an email, it evaluates it using some validation protocols. After authentication, the provider will do a DNS lookup in search of a BIMI record. Your BIMI record consists of the link to your logo and other technical information. The email service provider will display your brand’s logo if the BIMI record is valid. BIMI works based on some authentication protocols, including: Sender Policy Framework (SPF) DomainKeys Identified Mail (DKIM) Domain-based Message Authentication, Reporting, and Conformance (DMARC) You may require a Verified Mark Certificate (VMC) to be BIMI-compliant. The VMC is what validates that the logo’s trademark is truly owned by your company. Even though this requirement is optional (although some mailbox providers may require it), VMC could improve deliverability. Why Do You Need BIMI? Having covered what BIMI is and how it works, let’s take a quick look at why you need it. Here’re the major benefits of setting up BIMI: 1. Security To implement BIMI, you are required to adopt protocols like SPF, DKIM, and DMARC. These are protocols built to boost security and deliverability. With your brand’s logo being displayed alongside your messages, impostors will find it extremely difficult to deceive your subscribers. 2. Make Your Message Stand Out Having your logo displayed alongside your message improves brand recognition. And that’s what you need to stand out from the crowd. In a fiercely competitive business landscape, doing things differently is the way to go if you want to stay ahead of the curve. 3. Earn Subscriber Trust Given the impact of spoofing and phishing attacks on the cybersecurity landscape, subscriber trust is low. This affects how users respond to brand messages. With BIMI, you can offer your subscribers amazing experiences and confidence in your email campaigns. 4. Increase Deliverability Rates Implementing BIMI sends a positive signal to email service providers that your emails are authentic and trustworthy. As a result, you’ve got a higher chance of boosting deliverability. 5. Boost Open Rates It helps you to build trust that translates to higher open rates over time. Having your logo displayed next to your messages offers your brand the recognition it needs to win subscribers' attention. A study done during the BIMI beta program for Yahoo! Mail recorded an average of 10% boost in open rates. How to Set Up BIMI? Next, you’ll learn the step-by-step process involved in setting up BIMI. It works only with compliant mailbox providers. BIMI-supporting email services include AOL, Google, and Yahoo! That said, here’s how to set up BIMI: Step 1: DMARC Compliance The first step in BIMI setup is to ensure full DMARC compliance, which verifies that SPF and/or DKIM for all mail are properly aligned and authenticated with your From-domain. BIMI Needs DMARC to Work Ensure DMARC compliance by setting a reject policy in your DMARC record — either p=quarantine or p=reject. Step 2: Create Your BIMI Logo Image Create a brand logo that meets BIMI’s official specifications. Here are the basic requirements: Square dimensions SVG file size no more than 32KB Non-transparent background Solid background color is recommended Next, format your logo to be BIMI-compliant. The image must be in SVG Tiny P/S format. There are conversion tools available, but they can be difficult to use. After reviewing this article on the full specifications, we found the simplest way to create a compliant file is as follows: Step 2.1: Use Adobe Illustrator to “Save As…” an SVG Select the “SVG Tiny 1.2” profile when exporting your file. Step 2.2: Open the SVG File in a Text Editor and Make the Following Changes Edit the profile name Remove the x and y positioning attributes Remove the overflow attribute (if present) Convert any CSS styling into XML attributes SVG Before Edits SVG After Edits InboxAlly Step 3: Get a Verified Mark Certificate (VMC) Not every provider currently requires a VMC for BIMI to function, but this may change over time. To obtain a VMC, your logo must be trademarked with the relevant authority. After verifying trademark ownership, you can purchase a VMC from a certified authority such as: Entrust DigiCert Step 4: Publish a BIMI Record in DNS After creating a BIMI-compliant logo, go to your domain’s DNS records to publish a BIMI record. Insert a new TXT record in the default._bimi subdomain. This includes the BIMI version and where your logo is located (make sure the URL is HTTPS). Save the new record and you’re good to go! default._bimi.[domain] IN TXT “v=BIMI1; l=[SVG URL]; a=[PEM URL];" If this is too technical for you, you can build the record with our free BIMI Record Generator, which also runs a built-in DMARC prerequisite check and validates your SVG logo before you publish — so you can confirm the requirements from Steps 1–2 are met in one place. As an example the BIMI record for inboxally is as follows: v=BIMI1; l=https://assets.inboxally.com/images/ia-logo-bimi.svg; a=; Step 5: Check to Ensure Your BIMI is Properly Set Up As soon as your record is published, double check the SVG image, DMARC, and other requirements using the BIMI Inspector to look up your domain and check if BIMI is set up properly. You will see alert icons about all potential issues. After setting things up, you’ll need to give it about 24 hours to propagate and see the logo appear in the inboxes. What to expect with BIMI BIMI enables you to stay ahead of the curve by enhancing your brand recognition & reputation, offering more security, and enabling a better subscriber experience. It’s harder to stand out in the inbox than ever before so we recommend investing the effort to gain that extra credibility. What Inbox Providers Support BIMI? Gmail (Google) – Displays BIMI logos; typically requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC). Yahoo Mail (Verizon Media) – Supports BIMI logo display and often allows self-asserted records (no VMC needed). Apple Mail (iOS 16+, iPadOS 16+, macOS Ventura+, iCloud.com) – Fully supports BIMI with VMC requirement. Fastmail – Allows BIMI logo display, even with self-asserted records (no VMC required). AOL Mail – Supports BIMI with proper authentication setup. La Poste (France) – Supports BIMI; domains without VMC may require manual verification. Zone – Fully supports BIMI logo display. Cloudmark (Proofpoint) – Supports BIMI. GMX – Supports BIMI. Zoho Mail – Supports BIMI. Zoner – Supports BIMI. Frequently Asked Questions About BIMI What is BIMI used for? BIMI (Brand Indicators for Message Identification) displays a brand’s verified logo next to emails in the inbox. It enhances brand recognition, builds subscriber trust, and signals legitimacy to inbox providers. As adoption grows globally, BIMI is becoming essential to modern email marketing. Is BIMI a form of email authentication? No. BIMI is not an authentication protocol. It works alongside SPF, DKIM, and DMARC. These authenticate the sender’s identity, and BIMI uses that verification to display the brand’s logo once the domain passes those checks. Do you have to pay for BIMI? BIMI itself is free to implement. However, some inbox providers (like Gmail and Apple Mail) require a Verified Mark Certificate (VMC) to show your logo. A VMC, issued by a trusted authority, usually costs a few hundred to a few thousand dollars per year. What are VMCs? A Verified Mark Certificate (VMC) is a digital certificate from an approved authority (such as Entrust or DigiCert) verifying that your logo is trademarked and officially owned by your company. Some providers require a VMC for BIMI logos to appear, adding trust and brand protection. --- ## How do I set up InboxAlly for the first time? - URL: https://www.inboxally.com/docs/getting-started/quick-start-guide/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Five steps to go live: log in, verify your sender email, create a profile, set engagement rules, and import seed emails into your ESP. - Keywords: InboxAlly setup guide, how to set up InboxAlly, InboxAlly quick start, create sender profile InboxAlly, download seed emails, InboxAlly getting started > To set up InboxAlly: (1) log in, (2) add and verify your sender email, (3) create a sender profile, (4) choose engagement rules, and (5) download your seed emails. Once you import the seed list into your ESP and send your first campaign, InboxAlly begins generating engagement to improve your inbox placement. To get started with InboxAlly, you’ll (1) log in, (2) add and verify your sender email, (3) create a sender profile, (4) choose engagement rules, and (5) download your seed emails so you can begin sending campaigns and tracking inbox placement. How emails flow through mailbox provider systems from send to delivery, with engagement feeding back into reputation. 1. Email sender transmits a message using its sending infrastructure and domain. 2. Mailbox providers authenticate the sender using SPF, DKIM, and DMARC. 3. Mailbox providers evaluate the sender's historical reputation using engagement, complaints, and sending behavior. 4. Spam filtering algorithms analyze message content, links, authentication alignment, and reputation signals. 5. Based on filtering signals the message is delivered to inbox, promotions, or spam. 6. Opens, clicks, and spam complaints feed back into sender reputation and influence future filtering. How do I log in to InboxAlly? Go to the InboxAlly login page. Enter your registered email address and password. Select Log In. If you don’t have an account yet, start a free trial here: Create an InboxAlly account. How do I add a sender email? A sender email is the “From” address you’ll send campaigns from (for example, newsletter@yourdomain.com). In the left navigation, open Sender Emails. Select Add New Sender Email. Enter the email address you’ll be sending from. Verify the address: Check that inbox for a verification message from InboxAlly. Select the verification link inside the email. Tip: You can’t use an address in a sender profile until it’s verified. How do I create a sender profile? A sender profile groups your sending identity and engagement behavior so InboxAlly can train mailbox providers (like Google and Microsoft) using the seed email network. In the left navigation, open Sender Profiles. Select Create Sender Profile. Choose a verified From-Address from the dropdown. Enter a profile name (for example, “Main Newsletter” or “Sales Outreach – Domain A”). Save the profile. How do I configure engagement rules? Engagement rules control how InboxAlly’s seed email network interacts with your emails (for example: opens, clicks, moving messages to the inbox). Open your sender profile. Find Engagement Rules. Choose a preset or customize using the available sliders/dials. Select Apply Instructions to save. If you’re unsure which settings to use, start with a preset and adjust after you review results in your Dashboard and Reports. How do I download seed emails? Seed emails are InboxAlly-provided addresses you add to your sending list so InboxAlly can measure placement and generate engagement signals. In the left navigation, open Seed Emails. Choose one of the download options: Download all seed emails as a single file, or Use the range selector to download a specific subset. Add the downloaded seed emails to the audience/list you’ll be sending to (in your ESP), then send as normal. What should I do after sending emails? Monitor engagement and placement Most engagement activity happens within about 4 hours of sending. Check Broadcasts and your Dashboard for near real-time performance. Analyze results Use Reports to filter performance by mailbox provider (for example, Gmail vs. Microsoft) and spot patterns. If results look off (unexpected spam placement, low engagement, or inconsistent provider performance), run a Placement Tester or an Email Audit inside InboxAlly to pinpoint what’s limiting inbox placement. Additional resources Use these before you send to prevent common deliverability issues: Email Spam Checker (free): Analyze your email for spam triggers and get recommendations Email Content Tester (free): Check subject lines and content for common filter triggers Email List Verification (free): Clean your list to reduce bounces, spam traps, and risky addresses Spam Database Lookup (free): Check whether your domain or IP appears on major blacklists Ready to improve your email deliverability? Start a free trial of InboxAlly to improve your inbox placement: Create an InboxAlly account Once you’re in, set up your first Sender Email, create a Sender Profile, download your Seed Emails, and send your first campaign to begin tracking results in the Dashboard, Broadcasts, and Reports. --- ## How does InboxAlly work? - URL: https://www.inboxally.com/docs/getting-started/how-does-inboxally-work/ - Section: Getting Started - Last Modified: 2026-03-16 - Description: InboxAlly generates real engagement — opens, clicks, and inbox moves — to train Gmail, Yahoo, and Outlook that your emails belong in the inbox. - Keywords: how does InboxAlly work, email deliverability tool, improve sender reputation, seed email engagement, inbox placement improvement, get emails out of spam folder > InboxAlly improves email deliverability by generating authentic, human-like engagement on your emails — opens, clicks, and inbox moves — through real mailbox interfaces. This teaches providers like Gmail, Yahoo, and Outlook that your emails are wanted, which strengthens sender reputation and increases inbox placement. InboxAlly is an email deliverability tool that improves inbox placement by generating real engagement — opens, clicks, replies, and inbox moves — on your emails through real mailbox interfaces. These interactions train providers like Gmail, Yahoo, and Outlook to recognize your emails as wanted, which strengthens sender reputation and reduces spam folder placement. Email Deliverability Flow Diagram This diagram shows how mailbox providers process incoming emails from authentication through delivery and how recipient engagement feeds back into sender reputation. How emails flow through mailbox provider systems from send to delivery, with engagement feeding back into reputation. 1. Email sender transmits a message using its sending infrastructure and domain. 2. Mailbox providers authenticate the sender using SPF, DKIM, and DMARC. 3. Mailbox providers evaluate the sender's historical reputation using engagement, complaints, and sending behavior. 4. Spam filtering algorithms analyze message content, links, authentication alignment, and reputation signals. 5. Based on filtering signals the message is delivered to inbox, promotions, or spam. 6. Opens, clicks, and spam complaints feed back into sender reputation and influence future filtering. Why use a service like InboxAlly? Deliverability problems can be caused by a whole slew of issues, from poor list hygiene to authentication issues, spammy sending practices, and more. Even the most careful senders occasionally end up on a blacklist or have a ding against their sender reputation. While these issues are common - they can also cause dramatic changes in the deliverability and open rates of your emails. The last thing a business owner wants to see is their emails going to the spam folder. A poor sender reputation decreases the engagement rates on all of your emails - which in turn causes your sender reputation to fall further. The only reliable way to break out of this cycle is to get your recipients to reengage with your emails. This is where InboxAlly comes in. We work to improve your reputation by engaging with your email content when it’s sent to our “seed emails.'' These seed emails help train inbox providers to see your content as valuable and to prioritize delivery to the inbox. What are seed emails, and how do they work? Seed emails are unique email addresses we provide to every client, which you can load into your email sending platform. These seed emails each have unique engagement patterns that improve your reputation with inbox providers. When a seed email engages with the content you send, they start to show inbox providers that users value your content and want to see it in their inbox. This in turn improves your deliverability and open rates for future emails, improving your reputation further. What engagement actions do seed emails perform to improve your reputation? Every seed email has several actions that they can perform to ensure your emails are seen as important by inbox providers. These actions vary based on the provider and are essential to improving your reputation. Some examples of actions that a seed email can perform: Removing your emails from spam and sending to the primary inbox. Moving emails from the “promotions” or “updates” tabs into the primary inbox. Marking your emails as important. Opening your emails. “Reading” (scrolling through) your emails. Clicking links in your emails. Replying to emails Our AI interacts with each of our seed emails also using the native user interface for the platform they have been created on - instead of using an API or other interface. This ensures that inbox providers see these interactions as valuable user feedback, and not some automated computer script. Why is user engagement so important? The kind of user engagement performed by InboxAlly’s seed emails is critically important to improving and maintaining your reputation as a sender. Each inbox provider monitors senders (like you) very carefully, to ensure they aren’t spammers. The goal of every inbox provider is to ensure that important messages end up in the inbox - and spam stays out of it. When you send emails that have low open rates, low clickthrough rates, and high spam reports - your emails start looking a lot like spam to inbox providers. This hurts your sending reputation and means your emails will end up in the spam or promotions folders much more often. Using seed emails, we train these inbox providers to see your emails as valuable content that users love engaging with. Your goal as a sender should always be for your emails to look as different from spam as possible - and our service helps you quickly accomplish that. How quickly will I see an improvement in my deliverability when using InboxAlly? When using InboxAlly’s deliverability tool, you’ll see engagement rates in near real-time, and be able to monitor your progress as emails begin moving away from spam and into the inbox. After beginning to use the service consistently, most clients see an improvement in their deliverability and open rates in as little as 4 to 14 days. Some clients even see their open rates more than DOUBLE during this time! Every sender has their own reputation and history, so your progress may be faster or slower based on your past sending practices. Most senders will see a dramatic increase in their open rates, click through rates, and in turn revenue in a very short period of time. Is InboxAlly helping Spammers? InboxAlly is anti-spam and if you are a spammer, our services will provide just a temporary fix. You should first adopt good sending practices before using our services. I am ready to to learn more about InboxAlly, what should I do next? To schedule a product demo please click on the following link and select a day and time to talk with a product specialist: https://calendly.com/inboxally/inboxally-demo --- ## How do I use the InboxAlly Setup Wizard? - URL: https://www.inboxally.com/docs/getting-started/using-the-setup-wizard-to-get-started/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: The Setup Wizard walks you through adding a sender email, choosing seed seats, and downloading your seed list — the fastest path to first send. - Keywords: InboxAlly setup wizard, InboxAlly onboarding, how to configure InboxAlly account, InboxAlly first time setup, add sender email InboxAlly > The Setup Wizard walks new users through the minimum steps to start using InboxAlly: add your sender email address, choose how many seed email seats you need, and download your seed list to import into your sending platform. It's optional but the fastest way to get configured. When you first create an InboxAlly account, the Setup Wizard walks you through the minimum steps to start using InboxAlly’s seed email network. In most cases, you’ll: (1) start the wizard, (2) add your sender email address, (3) choose how many seed emails (seats) you want, and (4) download your seed list to import into your email sending platform. You can also follow along with this InboxAlly Setup Video. Using the setup wizard is optional, but it’s the fastest way for new users to get configured. If you prefer, you can skip it and adjust everything later in Sender Profiles and Sender Emails inside the InboxAlly app. Before you start Before you open the wizard, make sure you have: The sender email address you’ll be sending campaigns from (you can add more later) A plan to import a CSV file of seed emails into your email sending platform (the wizard provides the download) If you’re still planning your warmup schedule, use the free Email Warmup Planner to estimate an appropriate ramp-up and seed ratio. Start Setup To begin, click Start Setup in the Guided Setup panel. This initiates the account setup process. Sender Email Address Next, the setup wizard will prompt you to enter a Sender Email Address. This is the “from” address you’ll use to send campaigns. Key notes: If you have multiple sender addresses, you can add them later in Sender Emails. You can use the same email you signed up with by selecting the checkbox option in the wizard. Seed Setup In Seed Setup, you choose how many seed emails (seats) you want associated with your sender profile. Typical starting point for new users: 50–100 seed emails, linked to a single sender profile Note: InboxAlly supports seed email auto-subscribe using your newsletter landing page. This is an advanced option—contact Client Support if you think it applies to your setup and you’d like it enabled. Ready to Go! Once your sender profile is created, you’re ready to start using your seed emails. Follow the on-screen instructions to: Download your seed emails Import them into your email sending platform as a CSV file Send to them the same way you send to your regular contacts (InboxAlly’s seed email network will interact with your campaigns to help train inbox providers that your mail is wanted) Next steps (recommended) After you complete the wizard, these are the most common next actions: If you need to change anything later, go to Sender Profiles to modify your configuration. Consider booking an onboarding call if you want help choosing the right seed count, ramp-up approach, or sender profile structure. If you want to validate a list before sending, use InboxAlly’s free Email List Verification. If you don’t have an account yet, start a free trial of InboxAlly. --- ## What is the IA Assistant? - URL: https://www.inboxally.com/docs/getting-started/what-is-the-ia-assistant/ - Section: Getting Started - Last Modified: 2026-05-20 - Description: The IA Assistant is InboxAlly's in-app AI chat that diagnoses deliverability issues, checks SPF/DKIM/DMARC, and walks you through the fix step by step. - Keywords: IA Assistant, InboxAlly AI assistant, AI email deliverability assistant, InboxAlly chat assistant, AI deliverability help, email deliverability chatbot, what is the IA Assistant, InboxAlly AI chat > The **IA Assistant** is InboxAlly's in-app AI chat assistant. It diagnoses your deliverability issues using your real account data — IA Reputation Score, placement test results, authentication records, and DMARC reports — then walks you through the right checks and recommends concrete next steps. You describe what's happening in plain language — "my emails are going to spam at Gmail," "is my DMARC set up correctly?", "I switched ESPs and placement dropped" — and the IA Assistant diagnoses the issue using your actual account data, then guides you through the fix. It's available in every plan and activates automatically when you log in. What can the IA Assistant do? The IA Assistant is designed to do four things well: Diagnose deliverability issues by analyzing your specific sending situation rather than giving generic advice Check your authentication status — SPF, DKIM, and DMARC alignment — and explain what (if anything) needs to change Walk you through the right checks in the right order so you're not guessing which lever to pull first Recommend concrete next steps — authentication fixes, list hygiene actions, content changes, or reputation recovery moves — based on what it sees in your account Unlike a generic chatbot, the IA Assistant references your real account data when answering: your IA Reputation Score, Placement Tester results, Domain Reports, and DMARC reports. That means its recommendations are grounded in your sending reality, not averages from a knowledge base. How is the IA Assistant different from a generic AI chatbot? The IA Assistant combines an AI model with the diagnostic playbooks used by InboxAlly's in-house deliverability team. The same logic InboxAlly's experts apply when helping customers manually is what the Assistant follows when it walks you through a problem. Three things make the IA Assistant different from a generic AI chatbot: Account-aware — it sees your real sender reputation, placement test history, email authentication status, and DMARC data Expertise-grounded — its diagnostic logic mirrors how InboxAlly's deliverability team troubleshoots a real case Action-oriented — every diagnosis ends with a concrete next step, not a list of possibilities What questions can I ask the IA Assistant? You can ask the IA Assistant in your own words. A few examples to get you started: "Why did my Gmail open rate drop yesterday?" "Is my SPF record set up correctly?" "I switched from Mailgun to SendGrid and now I'm landing in spam — what should I check?" "How do I read my Domain Report?" "What's the next thing I should fix to improve my IA Score?" "Is my domain ready to send to a larger list this week?" "My DMARC policy is set to 'none' — should I change it?" "I'm getting blocked at Outlook. Where do I start?" The Assistant pulls the relevant data from your account, walks you through the diagnostic, and tells you what to do next. When should I use the IA Assistant? The IA Assistant is most useful when: You're new to InboxAlly and want a guided introduction to what to look at first Something changed — new ESP, new domain, new template, new list segment — and placement dropped A metric moved in a direction you don't understand (IA Score dropped, Gmail inbox placement fell, complaints spiked) You see a Domain Report flag and aren't sure what it means or how serious it is You're about to send to a larger audience and want a sanity check on your setup first You can also use it as an alternative to digging through documentation. If you'd rather ask a question than read an article, that's exactly what it's built for. What data does the IA Assistant use? The IA Assistant draws on the data already in your InboxAlly account, including: Your IA Reputation Score and how it's trended over time Placement Tester results across providers (Gmail, Outlook, Yahoo, and others) Domain Reports showing authentication status and reputation signals DMARC report data, where available The configuration of your Sender Profiles and Sender Emails The more data your account has accumulated, the more specific the Assistant's answers can be. New trials get useful guidance from day one, but accuracy improves as you run tests and send real campaigns. Should I use the IA Assistant or troubleshoot manually? You don't have to use the IA Assistant — InboxAlly's knowledge base covers every diagnostic step it walks through, and many articles include manual self-diagnosis references. The two work well together: Use the IA Assistant when you want a fast, account-aware answer Use the knowledge base when you want to understand the underlying framework, learn the "why," or investigate without context-switching into the app Articles like Why are my emails going to spam? and How to repair email sender reputation are designed to pair with the Assistant — the Assistant runs the diagnosis on your account; the articles explain the underlying mechanics. How do I access the IA Assistant? Log in to your InboxAlly account at app.inboxally.com. Open the IA Assistant from the app sidebar. Describe your situation in plain language and follow its guidance. If you don't have an account yet, start a free trial of InboxAlly — the IA Assistant is included, along with the Setup Wizard, Placement Tester, Domain Reports, and seed emails. Frequently Asked Questions Is the IA Assistant available in the free trial? Yes. The IA Assistant is included in every InboxAlly plan, including the 10-day free trial. It activates automatically when you log in and is accessible from the app sidebar. Does the IA Assistant use my account data? Yes. The IA Assistant references your IA Reputation Score, Placement Tester results, Domain Reports, DMARC report data, and your Sender Profile configuration to give you account-specific recommendations rather than generic advice. Can the IA Assistant fix my deliverability issues directly? The IA Assistant diagnoses issues and recommends concrete next steps, but you apply the changes yourself — for example, updating DNS records, adjusting your list segmentation, or modifying email content. It tells you exactly what to change and why. How is the IA Assistant different from ChatGPT or a generic AI chatbot? The IA Assistant is grounded in your real InboxAlly account data and in the diagnostic playbooks used by InboxAlly's in-house deliverability team. A generic chatbot can only give you broad advice; the IA Assistant gives you advice tied to what's actually happening with your sending. What if I'd rather talk to a human? You're always welcome to. The InboxAlly customer success team is available by live chat or by booking a meeting whenever you want to walk through something complex, unusual, or strategic. The IA Assistant handles the high-volume, common diagnostic patterns instantly, but a human expert is just a click away whenever you'd prefer one. Related articles How does the InboxAlly free trial work? Why are my emails going to spam? How to repair email sender reputation after deliverability issues Using the Setup Wizard to get started --- ## How do sender profiles, engagement rules, and seed emails work? - URL: https://www.inboxally.com/docs/getting-started/account-setup/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Configure sender profiles, pick engagement rule presets, and manage seed emails — everything after initial setup. - Keywords: InboxAlly sender profiles, email engagement rules, seed emails setup, how to configure InboxAlly, email deliverability seed list, sender profile engagement settings > A **Sender Profile** defines which verified email address InboxAlly monitors and what engagement rules to apply. **Engagement rules** control the types of actions (opens, clicks, moves to inbox) performed on your seed emails. **Seed emails** are InboxAlly-owned addresses you add to your sends so the platform can measure placement and generate engagement signals. A Sender Profile defines which verified email address InboxAlly monitors and what engagement actions to perform. Engagement rules control the specific interactions — opens, clicks, replies, moves to inbox — that seed emails carry out on your broadcasts. Seed emails are InboxAlly-owned addresses you include in your sends so the platform can measure placement and generate the engagement signals that improve deliverability. Seed emails: what they are and when to download them On the Seed Emails page, you’ll find a list of seed emails to download. Seed emails are InboxAlly-owned email addresses that you send to so InboxAlly can: assess your sending platform’s deliverability, and perform engagement actions (opens, clicks, moves, etc.) to help improve inbox placement. In most cases, you only need to download your seed emails once (unless you change plans, including upgrading from a trial). You can always return later and download them again. You’ll see two download options: Download the full list (all seed emails) Download a range (useful if your sending platform makes segmentation difficult) When you download a range, the file name includes the range for easier uploading/management. ⚠ Important: If you cancel InboxAlly or your trial ends, stop sending to the seed emails. Your emails will no longer be engaged with, and continuing to send to them could negatively affect your overall deliverability. Sender Profiles: what they are and how they’re used A Sender Profile defines the rules for mail sent from a specific From address (or IP address, depending on your setup). Sender Profiles also group your results so you can view reporting as separate broadcasts. Key points: Each Sender Profile is tied to a verified sender email that is not attached to another Sender Profile (even if that other profile is inactive). When you create a Sender Profile, InboxAlly generates a default name with a timestamp. You can rename it to something more recognizable (e.g., a client name or list name). This name is only visible to you. Sender Profile limit (and how to manage it) Your plan’s Sender Profile limit applies to active profiles only (not profiles you’ve marked inactive). If you need to send from a new From address but you’ve reached your limit: Deactivate an existing Sender Profile. Create the new Sender Profile. (Optional) Reactivate the old profile later. ⚠ 12-hour warning: Do not mark a profile inactive if a broadcast was sent from a From address in that profile within the last ~12 hours. Seed emails are only tracked and engaged with when the From address matches a From address in an active Sender Profile. You also have the option to purchase additional Sender Profiles. Engagement Rules: what they control Engagement Rules determine what actions InboxAlly’s seed emails take when they receive your broadcasts (for example: open, click, reply, move to inbox, etc.). You’ll find Engagement Rule presets on the Sender Profile page. You can: choose a preset that matches your situation, then tweak settings, or start by changing settings directly (which will create a “Custom” configuration). Engagement rule presets Rule Preset Description Default For general sending Traditional warmup Use this when you have a cold domain or IP. Also be sure to ramp up slowly and spread your sending throughout the day if possible. Contact us if you need help with a ramp up schedule. Domain & IP reputation repair Use this when you are having trouble getting out of the spam folder. Also, if possible, it's best first to stop sending to your own list and instead send to just our seeds for a week or two. Before using our service, you should first check and get your domain/IP delisted from any blacklist. Reputation boost Use this when you have been sending to one or more lists on a regular basis and feel you have experienced a drop in opens. Send to our (highly engaged) emails about 4 hours before sending to the rest of your list with the same exact subject, content and from-address. Mailbox providers will learn from our highly engaged seeds as part of your "real" broadcast. Reputation protect Use this when things are going well but you want to make sure you keep up your good reputation, especially if there is something special coming up such as holiday sale, new product launch, or other important announcement. Send to our (highly engaged) emails about 4 hours before sending to the rest of your list with the same exact subject, content and from-address. This will make it seem as our highly engaged seeds are part of your "real" broadcast. Custom When you tweak any of the settings, you will see a radio box titled "custom" appear in a selected state. When you’re finished adjusting your rules: Click Apply instructions, or Click Apply instructions & view emails to see your seed emails with instructions applied. How InboxAlly randomly applies engagements (and why) Every night at 12:00 AM in your profile’s local time, InboxAlly randomly reapplies your rules to your seed emails. This is intentional: it makes interaction behavior look more natural. If every seed email performed the exact same actions every day, it could look unnatural to mailbox providers. If you’re sending to the same seeds from the same From address more than once per day, you should reapply instructions manually: Open the relevant Sender Profile(s) Scroll to the bottom and click Reapply instructions Reporting and analytics (where results appear) Once you start sending campaigns that include seed emails, you’ll begin seeing placement data in reporting. As you send day over day, you’ll be able to track changes in placement over time and review results by broadcast. For deeper interpretation of results, see the KB article on Analyzing Engagement. --- ## How does the InboxAlly free trial work? - URL: https://www.inboxally.com/docs/getting-started/how-does-the-free-trial-work/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: 10-day, no-credit-card trial with full platform access — run real placement tests and see deliverability results before you commit. - Keywords: InboxAlly free trial, email deliverability free trial, try InboxAlly free, InboxAlly 10 day trial, test inbox placement free > InboxAlly offers a **10-day, no-credit-card free trial** that gives you access to the full platform — including the Setup Wizard, Dashboard, Placement Tester, and IA Assistant. You can configure a sender, connect your ESP, and run real placement tests to see how InboxAlly improves your inbox delivery. InboxAlly’s free trial is a 10-day, no-credit-card trial designed to help you set up InboxAlly, run a few real tests, and understand what the platform will do for your sending. During the trial, you can configure a sender, connect your sending method, and use core tools like the Setup Wizard, IA Assistant, Dashboard, and Placement Tester to evaluate inbox placement and reputation signals. Start your free trial here: Start a free trial of InboxAlly What you get in the 10-day free trial Your trial gives you access to the InboxAlly platform so you can: Set up a sender identity (via Sender Profiles and Sender Emails) Use the Setup Wizard to connect InboxAlly to your ESP or sending setup Send test campaigns and have InboxAlly’s seed emails interact with them (opens/clicks/moves to inbox) to help mailbox providers recognize your mail as wanted Monitor results in the Dashboard and Reports Run a Placement Tester to see inbox vs. spam placement across providers Review Domain Reports to spot authentication/reputation issues Use IA Assistant for guided, in-app recommendations and next steps Trial limits (what to expect) The trial includes limited daily volume and configuration capacity so you can evaluate the workflow without running a full-scale program. Specific limits (like daily seed sends or number of sender profiles) may vary over time—your account will show the current limits inside the app. What the trial can (and can’t) accomplish The free trial is best for learning the platform and validating your setup, not for fully repairing long-term deliverability issues. The trial is ideal for: Confirming InboxAlly works with your ESP/sending method Running a few controlled sends to see inbox placement trends Identifying obvious issues (authentication gaps, content red flags, list quality problems) Learning how to read InboxAlly metrics (including your IA Score) The trial is not enough for: A complete deliverability turnaround if you have significant reputation damage High-volume warmup or long-term reputation rebuilding (this typically requires more time and consistent sending) If you want to plan a realistic ramp-up, use the free Email Warmup Planner: Email Warmup Planner How to start the trial (fast setup) Create your account: Start a free trial of InboxAlly In the app, open the Setup Wizard and follow the prompts to connect your sending method. Create a Sender Profile and add your Sender Email(s). Send a small test campaign and review results in the Dashboard. Use IA Assistant to confirm your next best actions based on what InboxAlly is seeing. Key features to try during the trial To get the most value in 10 days, focus on these tools: Setup Wizard: Ensures your configuration is correct so your tests are meaningful. IA Assistant: Helps interpret what you’re seeing and suggests concrete next steps. Placement Tester: Quickly checks inbox vs. spam placement across major providers. Dashboard + Reports: Tracks performance and trends (including your IA Score). Email Audit (if available in your trial): Flags deliverability risks in setup/content/sending patterns. Email List Verification: Validate a small sample of your list before sending to reduce bounces and protect reputation. Tip: If you suspect content is part of the problem, you can also use the free tools on inboxally.com: Email Spam Checker Email Content Tester What happens when the trial ends When the 10 days are up, trial access expires. If you upgrade, your existing setup (like Sender Profiles, configuration, and historical results) carries over so you can continue without starting from scratch. How to upgrade to a paid plan To upgrade, log in to your InboxAlly account and choose a plan from the billing/upgrade area. Your account will switch to paid immediately, and you can continue using the same sender setup and data. --- ## Which InboxAlly plan should I start with? - URL: https://www.inboxally.com/docs/getting-started/how-do-i-know-what-plan-to-start-with/ - Section: Getting Started - Last Modified: 2026-03-11 - Description: Match your daily send volume and sender profile count to the right InboxAlly plan using the seed-to-send ratio as your guide. - Keywords: InboxAlly pricing plans, which InboxAlly plan to choose, email deliverability plan comparison, InboxAlly seed email ratio, best plan for email warmup > To choose the right InboxAlly plan, match your daily send volume to a tier: **Starter** (100 seeds/day, up to 2K sends), **Plus** (500 seeds/day, up to 10K sends, 5 profiles), **Premium** (1,000 seeds/day, up to 20K sends, 10 profiles), or **Enterprise** (custom). The key is maintaining a healthy seed-to-send ratio — use the in-app Service Planner to confirm the right fit. Choosing the right InboxAlly plan comes down to two things: your average daily send volume and how many sender profiles/domains you need to manage. As a quick rule of thumb, pick the plan that gives you enough unique seed emails per day to maintain a healthy seed-to-send ratio for your volume—this is a key lever for improving and protecting sender reputation. If you want a fast recommendation, use the InboxAlly Service Planner (inside the app). If you don’t have an account yet, you can start a free trial of InboxAlly: https://app.inboxally.com/register What to consider before choosing a plan InboxAlly plans are primarily differentiated by: Average daily email volume (how many emails you send per day) Number of sender profiles (how many separate sending identities/domains you manage) Seed email capacity (how many total sends to how many unique seed emails per day) Support level (email-only vs. chat vs. strategy sessions) Current sending reputation and how quickly you want to scale Why seed emails matter: InboxAlly’s seed email network engages with your mail (opens, clicks, moves to inbox) to help train mailbox providers that your emails are wanted. To get consistent results, you need enough seed coverage relative to your daily volume. If you’re unsure what ratio you should be targeting, the free Email Warmup Planner can help you estimate an appropriate ramp-up and seed ratio: https://www.inboxally.com/email-warmup-tool#email-warmup-planner Recommended starting plan (by typical daily volume) Starter Plan ($149/month) A strong starting point if you’re new to InboxAlly or running smaller campaigns. Sender profiles: 1 Support: Email support Seed capacity: 100 total sends to 100 unique seed emails/day Best for: Typically 2,000 emails/day or fewer Choose Starter if you want a simple setup and foundational deliverability improvement without managing multiple sender profiles. Plus Plan ($645/month) Best for growing programs that need more coverage and multiple sender profiles. Sender profiles: Up to 5 Support: Live chat + email support Seed capacity: 500 total sends to 500 unique seed emails/day Best for: Typically up to 10,000 emails/day Choose Plus if you’re scaling volume, adding domains/senders, or want broader seed coverage to maintain consistent inbox placement. Premium Plan ($1,190/month) Designed for larger-scale sending and teams that want more hands-on guidance. Sender profiles: Up to 10 Support: Email + chat + Zoom (premium support) Seed capacity: 1,000 total sends to 1,000 unique seed emails/day Includes: 1-hour onboarding strategy session + bi-weekly 30-minute check-ins Best for: Typically up to 20,000 emails/day Choose Premium if you’re managing multiple sender domains and want strategic oversight while scaling. Are there other plans available? Enterprise Plan (custom) If you have complex requirements or high-volume sending, Enterprise is fully customizable. Sender profiles: Unlimited Seed capacity: Thousands of unique seed emails/day (tailored to your volume) Support: Dedicated access to InboxAlly’s strategic deliverability team Best for: Agencies, multi-brand operations, and advanced sending infrastructures How to confirm you picked the right plan Estimate your average daily send volume (not just peak days). Count how many sender profiles/domains you need to manage. Use the InboxAlly Service Planner (in-app) to match your needs to a plan. If you want to sanity-check deliverability before scaling, run: Placement Tester (in-app) to see inbox vs. spam placement Email Audit (in-app) for diagnostics and recommendations If you’re still unsure, book a live demo or reach out to support via chat for a tailored recommendation based on your volume, sender setup, and goals. --- ## What are seed emails and how do they improve deliverability? - URL: https://www.inboxally.com/docs/getting-started/understanding-and-utilizing-seed-emails-for-improved-email-deliverability/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Seed emails are InboxAlly-owned addresses that generate opens, clicks, and inbox moves on your campaigns — building sender reputation automatically. - Keywords: seed emails for email deliverability, what are seed emails, how seed emails improve inbox placement, InboxAlly seed email engagement, email deliverability seed list strategy > Seed emails are InboxAlly-owned email addresses that you include in your sends. InboxAlly's AI system interacts with your emails through real mailbox interfaces — opening, clicking, and moving them to inbox — which signals to providers like Gmail and Yahoo that your mail is wanted. This builds sender reputation and improves inbox placement over time. Seed emails are dedicated email addresses owned by InboxAlly that you add to your sends so our AI system can interact with your campaigns — opening, clicking, replying, and moving messages to the inbox through real mailbox interfaces. These engagement signals teach providers like Gmail and Yahoo that your mail is wanted, which builds sender reputation and improves inbox placement over time. What Are Seed Emails? Seed emails are InboxAlly's own email addresses, hosted across major providers like Gmail, Yahoo, and Microsoft. You include them in your sends alongside your regular subscriber list. When our system receives your messages, it interacts with each one through the native user interface of the email platform — not via an API or background script. This distinction matters. Email providers can tell the difference between real engagement and automated signals. By working through native interfaces, InboxAlly's AI generates opens, clicks, replies, stars, and inbox moves that providers interpret as genuine user behavior. Over time, these signals build your sender reputation and improve inbox placement across your entire send volume. How to Set Up Seed Emails Step 1: Download your seed list Navigate to the Seed Emails page in the InboxAlly app (left navigation bar) and download your full set of seed email addresses. You can send to your entire seed list or a portion of it — the full list gives you the most engagement data and strongest impact. Step 2: Create a Sender Profile Go to the Sender Profile page and create a new profile. This defines the engagement rules that InboxAlly applies to your emails — which actions (opens, clicks, replies, stars, inbox moves) our system performs on each send. Step 3: Choose an engagement preset On the Sender Profile page, select an engagement rule preset that matches your goal. Some presets maximize opens and clicks for engagement campaigns; others prioritize inbox moves for new or recovering domains. You can also adjust individual settings for more control. Engagements are applied randomly each night at 12:00 AM based on your profile's local time, so the interaction pattern looks natural to providers. Step 4: Add seed emails to your sends Import the downloaded seed addresses into your email sending platform and add them to the same list or segment you use for regular campaigns. Our system will interact with most seed emails within 4 hours of sending, with engagement starting within the first hour. No additional steps are needed — the system handles everything based on your Sender Profile. Monitoring Your Results Track seed email performance in two places: Broadcasts (left navigation bar) — engagement data for individual sends including open rates, click-through rates, and inbox placement Reports / Dashboard — trends over time across providers, helping you refine your sending strategy Frequently Asked Questions Can I send to only part of my seed list? Yes. The full list gives you the most data and broadest impact, but partial sends still generate valuable engagement signals. How quickly will I see results? Most users see initial improvement within one to two weeks. Full reputation building typically takes four to eight weeks of consistent sending. Do seed emails work with every type of email? Yes — promotional campaigns, newsletters, transactional messages, and re-engagement campaigns all benefit from seed email engagement. What happens if I stop using seed emails? Without the engagement signals seed emails provide, your sender reputation may gradually decline, especially if regular subscriber engagement is low. For best results, keep seed emails as a permanent part of your sending routine. Next Steps Check out the quick start tutorial and new account setup guide to get started with InboxAlly. For help interpreting your results, see Analyzing Engagement. --- ## How do I shuffle my InboxAlly seed emails? - URL: https://www.inboxally.com/docs/getting-started/how-to-shuffle-your-inboxally-seed-emails/ - Section: Getting Started - Last Modified: 2026-03-11 - Description: Swap current seed addresses for fresh ones from InboxAlly's pool to prevent pattern detection and keep placement data accurate. - Keywords: shuffle InboxAlly seed emails, rotate seed email addresses, InboxAlly seed management, refresh seed list deliverability, seed email provider distribution > Shuffling replaces some or all of your current seed email addresses with fresh ones from InboxAlly's pool while keeping your plan and seed count the same. Go to **Seed Emails → Manage Seed Emails** to shuffle. InboxAlly recommends shuffling at least once a month for the most accurate placement data. Shuffling replaces some or all of your current seed email addresses with fresh ones from InboxAlly's pool. Your seed count and plan stay the same — you just get different addresses. Think of it like rotating tires: same setup, fresh contact points. This article walks through how to shuffle using the InboxAlly UI and covers the key things to do after a shuffle. Why Shuffle Your Seeds Shuffling keeps things fresh. Benefits of regular shuffling: Gives you more accurate placement data — new seeds have no engagement history with your domain, so results better reflect how a real new subscriber experiences your emails Keeps your deliverability data meaningful over time InboxAlly recommends shuffling at least once a month. The system enforces a 30-day cooldown between shuffles to maintain seed stability. Your last shuffle date is shown in the right sidebar of the Seed Emails page so you always know when your seeds were last refreshed. How to Shuffle — Step by Step In the InboxAlly sidebar, click Seed Emails. Click the MANAGE SEED EMAILS tab (next to VIEW & DOWNLOAD). You will see the shuffle options with two methods to choose from. Option A: Keep Current Distribution (Recommended) This is the best choice for most users. It replaces seeds with fresh ones while keeping your current provider mix intact — if you have 60% Gmail and 20% Yahoo now, you will still have 60% Gmail and 20% Yahoo after the shuffle. Select Keep Current Distribution. Use the Shuffle % slider to choose how many seeds to replace. You can do a partial shuffle (for example, 80%) or a full shuffle (100%). Optionally, check Adjust by Email Provider if you want to tweak the shuffle percentage per provider (for example, shuffle 90% of Gmail seeds but only 50% of Gsuite seeds). Click Keep Same Distribution & Shuffle Seed Emails. When to use this: Most situations. Your provider distribution already matches your audience, and you just want fresh seed addresses. Option B: Custom Distribution This option lets you change the provider mix entirely. Use it when your audience skews toward specific providers and your current seed distribution does not match. Select Custom Distribution. Enter the desired percentage for each provider: Gmail, Yahoo, Gsuite, Hotmail, Outlook. The percentages must total 100%. Optionally, check Add more seed emails if you want to increase your total seed count (may require a plan upgrade). Click the button to execute the shuffle. When to use this: B2B senders: Increase Gsuite, Outlook, and MS365 percentages since business contacts are more likely on those providers. B2C senders: Keep Gmail and Yahoo higher to match consumer email usage. Regional senders: Adjust based on which providers your audience uses most. Partial vs. Full Shuffle Shuffle % Best for 10-50% (minor) Maintaining continuity while refreshing part of the seeds. Use when your overall inbox placement is below 80%. 50-80% (partial) Maintaining some continuity while refreshing most seeds. Good for ongoing monitoring where you want to compare old and new seed performance. Use when your overall inbox placement is above 80%. 100% (full) Getting completely fresh placement data with no carryover. Best when you want a clean baseline or suspect pattern detection is affecting your results. After Shuffling — Critical Steps After a shuffle completes, your old seed addresses are no longer active. You must update the seed list in your ESP or email platform so your campaigns go to the new addresses. If you use a native integration (Klaviyo, HubSpot): Seeds sync automatically. No manual update needed — InboxAlly handles it. If you manually manage seeds in your ESP: Go to the VIEW & DOWNLOAD tab on the Seed Emails page. Click Copy All or Export to get your updated seed list. In your ESP, remove the old seed contacts from your InboxAlly Seeds list. Import the new seed addresses. Verify that the new seeds are included in your next campaign. For platform-specific steps, see your integration guide: Integrate Mailchimp with InboxAlly Integrate Klaviyo with InboxAlly How to Use InboxAlly with Any Email Platform If you use the API: Fetch your updated seed list with GET /v3/seeds and sync programmatically. See InboxAlly API: Overview and Getting Started for details. Your historical data is preserved. Reports and placement data from old seeds remain in your account. Shuffling does not delete any past performance data. Shuffle Timing and Best Practices Cooldown: The system enforces a 30-day cooldown between shuffles. The Seed Emails page shows when your next shuffle is available. Frequency: Monthly shuffles strike the right balance between fresh data and seed stability. More frequent is not possible due to the cooldown. Start with partial shuffles if you are unsure. An 80% shuffle refreshes most of your seeds while keeping 20% for continuity. Use full shuffles when starting a new campaign strategy, moving to a new domain, or when you want a completely clean placement baseline. Shuffling via API Seed shuffling is also available through the InboxAlly API for users who want to automate the process. Key endpoints: POST /v3/seeds/shuffle/trigger — trigger a shuffle with your chosen method (in_place, in_place_by_provider, or custom) GET /v3/seeds/shuffle/status — check if a shuffle is allowed and when the next one is available GET /v3/seeds/shuffle/history — view past shuffles Common automation: Set up a monthly cron job that checks the cooldown status, triggers a shuffle, then fetches the updated seed list to sync to your ESP. For full API details, see InboxAlly API: Overview and Getting Started. Troubleshooting Issue Cause What to do Shuffle button is greyed out 30-day cooldown has not elapsed Check the sidebar for your last shuffle date and wait until the cooldown expires New seeds not receiving campaigns ESP still has old seed addresses Re-export seeds from VIEW & DOWNLOAD and update your ESP contact list Inboxing data looks different after shuffle Expected — new seeds have no engagement history with your domain Give it 3-5 sends for the new seeds to generate meaningful data Provider percentages do not match what I entered Rounding — seed count may not divide evenly across providers Small differences (1-2%) are normal due to rounding Related Articles Understanding and Utilizing Seed Emails InboxAlly API: Overview and Getting Started Quick Start Guide How to Use InboxAlly with Any Email Platform --- ## Does InboxAlly work with my email provider? - URL: https://www.inboxally.com/docs/getting-started/how-does-inboxally-work-with-custom-email-providers/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: InboxAlly is platform-agnostic — if you can add seed emails to your recipient list and send to them, your ESP or custom server is compatible. - Keywords: InboxAlly ESP compatibility, does InboxAlly work with my email provider, InboxAlly custom email server, email deliverability tool any platform, InboxAlly supported email platforms > Yes — InboxAlly works with any email provider, platform, or custom mail server. As long as you can add seed email addresses to your recipient list and send campaigns to them, InboxAlly is compatible with your setup. No provider switch or workflow changes required. Yes — InboxAlly works with any email provider or platform you can send email from, including custom email servers and in-house systems. If you can add InboxAlly seed emails to your sending list and send campaigns to them, you can use InboxAlly to improve deliverability. Quick compatibility checklist (what’s required) InboxAlly is compatible with your setup as long as you can: Add new contacts/recipients (the InboxAlly seed emails) to your email provider, list, CRM, or database Send emails to those seed emails as part of your normal sending (campaigns, broadcasts, sequences, or outreach) That’s it. There’s no requirement to switch providers or change your sending workflow. No account access or software sharing required You do not need to share login access to your email accounts, ESP, or internal tools. In most setups, you simply: Create a Sender Profile in InboxAlly Upload/add the provided seed emails to your system Send as you normally do (same schedule, same content) InboxAlly works alongside your existing process. Works for small lists through enterprise sending InboxAlly scales to match your needs: Small-volume senders (new domains, small lists, outreach) Growing teams with multiple domains/subdomains High-volume and enterprise sending with segmentation and multiple sender identities Next steps: set up InboxAlly with your provider Follow the guided onboarding in the Setup Wizard (inside the InboxAlly app). If you don’t have an account yet, you can start a free trial of InboxAlly. Use the relevant ESP integration guide for your platform (if available in our knowledge base) to connect your sending workflow and seed list setup. See the Integrations Guide. --- ## How do I verify my email list with InboxAlly? - URL: https://www.inboxally.com/docs/getting-started/email-list-verification/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Upload a CSV to InboxAlly's built-in list verification to remove invalid, inactive, and duplicate addresses — reducing bounces and protecting reputation. - Keywords: email list verification, verify email addresses, clean email list, remove invalid email addresses, InboxAlly list cleaning, reduce email bounce rate > Upload a CSV file of your contacts to InboxAlly's built-in list verification service. It identifies and removes invalid, inactive, and duplicate email addresses — reducing bounce rates and protecting sender reputation. After processing, download the cleaned list of valid emails and use it for your sends. Email list verification checks every address on your mailing list and flags invalid, risky, or duplicate contacts so you can remove them before sending. InboxAlly includes a built-in verification tool — upload a CSV, and it returns a cleaned list of valid addresses, reducing bounces and protecting your sender reputation. InboxAlly also offers a free Email List Verification tool on inboxally.com with 99%+ accuracy. How to verify your email list 1. Prepare your file Save your email list as a .CSV file with one email address per row. Most ESPs and CRMs can export contacts in this format. 2. Upload and run verification Log in to the InboxAlly app and open the Email List Verification tool. Click Upload and select your CSV file. Start the verification process. InboxAlly scans every address and categorizes it into one of several result types (see below). Processing time depends on list size — a list of 100,000 addresses typically takes less than 30 minutes. 3. Download and use the cleaned list Once processing finishes, download the results. The output separates addresses into categories so you can decide what to keep: Category What it means Recommendation Valid Address exists and can receive mail Send to these Invalid Address doesn't exist, bad syntax, or dead domain Remove immediately Catch-all Domain accepts all addresses — can't confirm the specific mailbox exists Send with caution; monitor bounces Disposable Temporary/throwaway address (e.g., Guerrilla Mail, Mailinator) Remove — these go inactive quickly Role-based Generic address like info@, support@, admin@ Remove or handle separately — high complaint risk Spam trap Address designed to catch senders with poor list hygiene Remove immediately — hitting these damages reputation Duplicate Same address appears more than once in your list Remove duplicates Best practice: Only send to Valid addresses. If you choose to keep catch-all addresses, watch your bounce rate closely after the first send and suppress any that bounce. When to verify your list Before your first send with InboxAlly — start with a clean list to get the best results from seed emails. Before any major campaign — especially if the list has been sitting idle. After importing new contacts — purchased lists, event signups, and scraped lists are high-risk for invalid addresses and spam traps. On a regular schedule — quarterly verification is a good baseline. Monthly is better for large or fast-growing lists, since roughly 2-3% of email addresses go invalid every month due to job changes, abandoned accounts, and domain expirations. Verification credits Each list upload uses one verification credit, regardless of list size. Credits are renewed monthly based on your InboxAlly plan. Unused credits do not carry over to the next month. Plan your verifications around your credit allocation — if you have multiple lists or segments, combine them into a single CSV to use one credit instead of several. For ongoing list hygiene alongside deliverability monitoring, start a free trial to access the in-app verification tool plus Domain Reports, Placement Tester, and InboxAlly's seed email network. --- ## How do I add users to my InboxAlly account? - URL: https://www.inboxally.com/docs/getting-started/can-i-add-another-user-to-my-account/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Invite team members via Access Management and assign Super User, Manager, Analyst, or Viewer roles to control account access. - Keywords: add users to InboxAlly, InboxAlly user roles, InboxAlly access management, team account permissions, multi-user email deliverability account > Yes — InboxAlly supports multiple users per account with role-based permissions. Go to **My Account → Access Management** to invite team members and assign roles like Super User, Manager, Analyst, or Viewer. Yes — InboxAlly allows you to add multiple users to your account, each with role-specific permissions. This feature is ideal for teams that divide responsibilities across operations, compliance, data analysis, or campaign management. You can manage user access by navigating to: My Account → Access Management From this section, you can invite new users, assign roles, and define the level of access each team member has. Below is a breakdown of the available user roles and their capabilities. 1. Super User Access Level: Full Permissions: Manage all settings in the account View and download invoices Perform account upgrades and billing-related actions Use Case: Designed for account owners or administrators responsible for full system access and billing. 2. Standard User Access Level: Broad (with limitations) Permissions: Full access to most areas of the account Limitations: Cannot view invoices Cannot perform upgrades or manage billing Use Case: Suitable for team members who handle operational aspects but should not have access to financial or billing features. 3. Seed Email Manager Access Level: Seed email operations Permissions: Access to the dashboard for seed email management View, replace, shuffle, and download seed emails Limitations: No access to reports, broadcasts, or billing settings Use Case: Appropriate for compliance teams or partners managing seed coverage and monitoring. 4. Analytics Manager Access Level: Reports and performance analysis Permissions: Access to dashboard, broadcasts, and reports Analyze campaign performance data Limitations: No access to seed email tools, billing, or account settings Use Case: Best for marketing analysts or external consultants focused solely on performance monitoring. 5. Selective Report Viewer Access Level: Limited reporting Permissions: View reports for specific sender profiles assigned to them Limitations: Cannot access other sender profiles, seed data, or account settings Use Case: Ideal for clients or junior team members who need access to specific reporting segments only. How to Add a New User Navigate to My Account → Access Management Click “Add User” Enter the user’s email address Assign the desired role The user will receive an invitation to activate their access Switching Between Multiple Accounts If a user is granted access to more than one InboxAlly account, they can easily switch between them using the workspace selector in the top-right corner of the application interface. The workspace selector will list all accounts the user is a part of. Selecting a different workspace will immediately switch the context to that account, allowing the user to manage settings, view reports, and perform actions based on the permissions assigned within that workspace. This ensures a seamless experience for consultants, agencies, or team members involved with multiple brands or business units. Security Recommendation For optimal security, assign the minimum level of access needed for a user to complete their tasks. This ensures both functionality and data protection. If you need help choosing the right role or require custom permissions, please contact our support team. --- ## What makes InboxAlly different from other deliverability tools? - URL: https://www.inboxally.com/docs/getting-started/who-are-our-competitors/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: GUI-based engagement, up to 8 actions per seed, no ESP access required — how InboxAlly outperforms other deliverability tools. - Keywords: InboxAlly vs competitors, best email deliverability tool, InboxAlly alternative comparison, email warmup tool features, GUI based email engagement, inbox placement tool comparison > InboxAlly performs engagement actions through real mailbox interfaces (GUI-based, not API), supports up to 8 randomized actions per seed email, works with any ESP without requiring platform access, and covers the full deliverability lifecycle — from warm-up through ongoing reputation management and recovery. InboxAlly is designed to improve inbox placement by generating consistent, human-like engagement on your emails and giving you clear, actionable deliverability reporting—without requiring access to your sending platform or your data. Below are the core capabilities that make InboxAlly different, and how they work in practice. What makes InboxAlly different? 1) End-to-end deliverability support (beyond warmup) InboxAlly supports deliverability work across the full lifecycle of a sender, including: Improving inbox placement for ongoing campaigns Supporting sender/domain recovery when reputation has been damaged Helping during ESP migrations (so deliverability doesn’t drop during the transition) Ongoing monitoring and optimization as your volume scales This matters because deliverability issues rarely have a single cause—InboxAlly is built to support the full set of steps required to stabilize and improve performance. 2) A large pool of seed emails that can scale with your volume InboxAlly uses a large set of seed emails to generate engagement signals at scale. This is especially important if you send high daily volume, because deliverability improvements need to remain consistent as your sending increases. In practice, this means InboxAlly can support senders ranging from smaller lists to very large, high-frequency programs. 3) Engagement is performed through real mailbox interfaces (GUI-based) InboxAlly engagement actions are performed through the graphical interface (GUI) of each mailbox provider (the same way a person would interact with an email), rather than relying on API/IMAP-based actions or browser extensions. Why this matters: Mailbox providers can evaluate how engagement happens, not just that it happened. GUI-based actions more closely resemble real user behavior and can carry more weight for reputation signals. 4) Multi-layered engagement actions, randomized like human behavior InboxAlly can perform up to 8 different engagement actions per seed email. Actions are: Performed in a randomized order (instead of a fixed sequence) Modeled after natural human behavior Repeated multiple times per day when appropriate This approach helps create more realistic engagement patterns and improves accuracy compared to a minimal, once-per-day interaction model. 5) You can use your own content for engagement InboxAlly supports sending your actual email content to seed emails. This helps mailbox providers become familiar with the: Keywords and phrases you commonly use Links and domains included in your campaigns Typical formatting and structure of your messages Using real content is especially helpful when your campaigns include specific brand terms, tracking links, or repeated CTAs. 6) Send and schedule using your real send-time InboxAlly lets you schedule and send emails to seed emails at times aligned with your real broadcasts. Benefits: Engagement occurs in a timeframe that matches your normal sending behavior Reporting reflects realistic conditions (instead of artificial “test-only” timing) Your deliverability signals are built around the same patterns mailbox providers see from your actual program 7) Human-like engagement windows after sends InboxAlly engages with emails within a window of time after your broadcasts, rather than all at once. This creates a more natural pattern such as: Some engagement soon after delivery Continued engagement over a realistic time window That spread helps model how real recipients behave and supports healthier engagement signals. 8) Works with any sending platform InboxAlly is platform-agnostic. You can use it whether you send from: Google Workspace or Microsoft/Outlook A dedicated ESP Your own sending infrastructure/servers This flexibility is useful if you operate multiple sending systems or plan to migrate platforms without rebuilding your deliverability process from scratch. 9) Secure by design: no access to your sending platform or data required InboxAlly is designed so you don’t have to grant access to your sending platform. That means: InboxAlly does not need to log into your ESP InboxAlly does not require access to your audience lists Your sending environment remains isolated from the InboxAlly platform This reduces risk and keeps your operational data under your control. 10) Built-in inbox placement testing and reporting InboxAlly includes inbox placement testing inside the platform, so you can measure results and track changes over time. To use this, look for: Placement Tester (to see inbox vs. spam placement across providers) Reports (to analyze performance by provider and over time) Email Audit (for deeper diagnostics when placement drops) If you don’t have access yet, you can start a free trial here: Start a free trial of InboxAlly. --- ## How do I cancel my InboxAlly subscription? - URL: https://www.inboxally.com/docs/getting-started/how-to-cancel-my-subscription/ - Section: Getting Started - Last Modified: 2026-03-10 - Description: Cancel via the link on your latest InboxAlly invoice (fastest) or through live chat — only the account owner or billing user can cancel. - Keywords: cancel InboxAlly subscription, how to cancel InboxAlly, InboxAlly cancellation, downgrade InboxAlly plan > To cancel, use the **cancellation link on your most recent InboxAlly invoice** — this is the fastest self-service option. You can also request cancellation through **live chat** in your dashboard. Only the account owner or a user with billing permissions can cancel. To cancel your InboxAlly subscription, use the cancellation link on your invoice (fastest self-service option). If you can’t access the invoice, you can also request cancellation via live chat in your dashboard or on our website. Who can cancel Only the account owner or a user with billing permissions can cancel a subscription. If you’re not sure who that is, check your account settings or contact us via live chat. How to cancel (recommended: from your invoice) Open your most recent InboxAlly invoice/receipt email. Select the cancellation link on the invoice. Follow the prompts to confirm cancellation. Alternative: cancel via live chat If you can’t find your invoice or the link isn’t available, message us using the live chat widget: on the InboxAlly website, or inside your InboxAlly dashboard Our team will confirm and process the cancellation. What happens after you cancel Access: You’ll keep access until the end of your current billing cycle. Billing: You won’t be charged again unless you reactivate. Your settings & data: Your account configuration (e.g., sender profiles and related settings) is kept, so if you resubscribe later you can typically pick up where you left off. Prefer a downgrade instead of canceling? If you want to keep the account active but reduce cost, ask about a downgrade (or other plan adjustment) via live chat. --- ## How do I use InboxAlly with any email platform? - URL: https://www.inboxally.com/docs/integrations/how-to-use-inboxally-with-any-email-platform-generic-setup-guide/ - Section: Integrations - Last Modified: 2026-03-10 - Description: Add InboxAlly seed addresses to any ESP or SMTP tool and include them in campaigns — no API, plugin, or special integration required. - Keywords: InboxAlly setup guide, connect InboxAlly to ESP, InboxAlly seed email setup, use InboxAlly with any email platform, InboxAlly generic integration, email deliverability tool setup > InboxAlly works with **every email platform** that can send to a list of addresses — no API integration required. Download your seed emails from InboxAlly, add them as contacts in your ESP or sending tool, and include them in your campaigns. InboxAlly handles the rest by engaging with those emails to strengthen your sender reputation. InboxAlly works with every email platform that can send to a list of addresses. There is no API integration required — you just add your seed email addresses to your sending platform and include them in your campaigns. If your platform can send an email, it can work with InboxAlly. This guide covers the universal setup process that applies to any ESP, email marketing tool, or SMTP-based sending system. How InboxAlly Works with Any Platform InboxAlly provides you with a set of seed email addresses. You add those addresses to your email platform as contacts or subscribers. When you send campaigns, the seeds receive your emails alongside your real subscribers. InboxAlly then engages with those emails — opening, scrolling, clicking, replying, and moving them from spam to inbox — which sends positive signals to mailbox providers and strengthens your sender reputation. No API key. No OAuth connection. No special plugin. Just add the email addresses and send. Prerequisites An active InboxAlly account with seed emails assigned An email platform account where you can add contacts and send campaigns Access to your InboxAlly Seed Emails page Step 1: Export Your Seed Email Addresses Log in to your InboxAlly account. Navigate to the Seed Emails page from the left sidebar. Click Copy All to copy all seed addresses to your clipboard, or click Export to download them as a CSV file. The CSV export works with virtually every email platform's import feature. Step 2: Create a Dedicated Group for Seeds In your email platform, create a separate list, segment, tag, or group for your InboxAlly seed contacts. The exact method depends on your platform: Platform type How to organize seeds List-based (Mailchimp, Brevo, Constant Contact, Moosend) Create a new list called "InboxAlly Seeds" Tag-based (ConvertKit/Kit, Drip) Create a tag called "InboxAlly Seeds" and apply it to seed contacts Segment-based (Omnisend, MailerLite) Create a segment based on a custom field or tag that identifies seeds SMTP relay (Amazon SES, Postmark, SparkPost, SendGrid) Add seeds to the recipient list of your actual campaign sends A dedicated group keeps seeds organized, makes them easy to include in every send, and protects them from automated list cleaning. Step 3: Import Seed Addresses Most platforms support CSV import: Go to your platform's contact import or subscriber import feature. Upload the CSV file or paste the email addresses. Map the email field (usually automatic). Assign the contacts to your InboxAlly Seeds group, list, or tag. If prompted about double opt-in or confirmation emails, skip it for seed addresses. Seeds are managed by InboxAlly and do not need to confirm. Complete the import. Step 4: Include Seeds in Every Send This is the most important step. For best results, seed addresses should receive your actual campaign emails. For marketing campaigns and broadcasts: When selecting recipients, include your InboxAlly Seeds group alongside your regular subscriber lists. If you use audience segments, make sure the segment does not exclude seed contacts. For automated sequences, drip campaigns, and workflows: Enroll seed contacts into your automations so they receive the same emails your subscribers get. Check that trigger conditions and filters do not prevent seeds from entering the workflow. For transactional email (SMTP): If you send transactional email through an SMTP relay (Amazon SES, Postmark, SparkPost, SendGrid), add seed addresses to the recipient list of your actual sends — not just test sends. Seeds need to receive the same emails your real users receive to generate meaningful deliverability data. Step 5: Verify in InboxAlly After your first send that includes seeds: Go to your InboxAlly Dashboard. Check the Emails Engaged chart — you should see activity within a few hours. Look at the Latest Engagements feed for opens, scrolls, and other actions. Confirm your campaign appears in the Latest Broadcasts Engaged table. If engagement is showing, you are all set. Common Pitfalls to Avoid These issues come up across all platforms. Watch for them regardless of which tool you use: Double opt-in blocking seeds Some platforms require new contacts to confirm their subscription. Disable confirmation for seed imports, or manually mark them as confirmed. Sending to only part of your seed list Make sure all seeds are included in every send. If your platform splits recipients by segment or list and you forget to add seeds to one of them, those seeds will not receive the email and your deliverability data will be incomplete. Platform-Specific Notes Quick tips for platforms that do not have a dedicated InboxAlly integration guide: Platform Notes Constant Contact Create a contact list for seeds. Add it to every campaign on the recipients step. Drip Use tags to label seeds. Include the tag in your workflow triggers or campaign audience. MailerLite Create a group for seeds. Add the group to campaigns alongside your subscriber groups. Moosend Create a mailing list for seeds. Include it in your campaign recipient settings. Omnisend Add seeds as subscribers with a custom property. Use that property to create a segment, then include it in campaigns. Amazon SES Seeds must be in the recipient list of actual sends. Use your application code or a bulk sending tool to include them. Postmark Include seeds in your broadcast sends. For transactional email, add them via your sending script. SparkPost Add seeds to your recipient list alongside real recipients. SendGrid Create a contact list for seeds. Include it in your Marketing Campaigns or add seeds to your transactional sends via API. Related Articles Understanding and Utilizing Seed Emails Integrate HubSpot with InboxAlly Integrate Klaviyo with InboxAlly Quick Start Guide How Does InboxAlly Work --- ## How do I get started with the InboxAlly API? - URL: https://www.inboxally.com/docs/integrations/inboxally-api-overview-and-getting-started/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Authenticate with your API key to manage seeds, sender profiles, and broadcast data programmatically. Full reference at apidocs.inboxally.com. - Keywords: InboxAlly API, InboxAlly REST API documentation, email deliverability API, InboxAlly API authentication, manage seeds programmatically, InboxAlly developer integration > To get started with the InboxAlly API, generate an API key in **My Account → API**, then pass it in the `X-API-KEY` header with every request to `https://api.inboxally.com`. Start with `GET /v3/seeds`, `GET /v3/senders`, or `GET /v3/broadcasts` to verify your connection. Full interactive reference at [apidocs.inboxally.com](https://apidocs.inboxally.com). InboxAlly provides a REST API that gives you programmatic access to your seeds, sender profiles, and broadcast data. If you manage multiple accounts, build custom dashboards, or want to automate tasks like seed shuffling or engagement rule changes, the API is how you do it. The full interactive API reference with request/response examples lives at apidocs.inboxally.com. This article explains what the API can do, how to authenticate, and how to get started. Who Should Use the API The API is built for: Agencies and resellers managing sender profiles across multiple client domains Developers building internal tools or custom integrations with InboxAlly Platforms integrating InboxAlly functionality natively into their own product Power users who want to automate seed shuffling, engagement tuning, or reporting If you just need to add seed emails to your ESP, you do not need the API — see How to Use InboxAlly with Any Email Platform for the simpler approach. For platforms with native integrations like Klaviyo or HubSpot, those handle connectivity automatically. Authentication All API requests require an API key sent in the request header. Where to find your API key: Log in to your InboxAlly account. Go to My Account → API. Copy your API key. How to authenticate: Include your key in the X-API-KEY header on every request: X-API-KEY: your-api-key-here All requests go to https://api.inboxally.com. API keys are account-scoped — they provide full access to your account's resources. Keep them secure and never embed them in client-side code or public repositories. API Capabilities The API is organized into three resource groups: Seeds, Senders, and Broadcasts. Seeds Manage your seed email addresses and control seed shuffling. Retrieve seeds: List all seeds with filtering by status (active, inactive, or all) Get details for a specific seed by email address Supports pagination for large seed lists Shuffle seeds: Trigger a shuffle to replace seed addresses with fresh ones from InboxAlly's pool Check shuffle status to see if a shuffle is currently allowed (there is a 30-day cooldown between shuffles) View your last shuffle details and full shuffle history Three shuffle methods are available via API: Method What it does in_place Shuffles a percentage of all seeds while keeping the same provider mix (e.g., 60% Gmail, 20% Yahoo stays the same) in_place_by_provider Shuffles different percentages per provider — for example, replace 75% of Gmail seeds but only 25% of Gsuite seeds custom Shuffles seeds and redistributes them to a completely new provider mix For a full walkthrough of seed shuffling (including the UI method), see How to Shuffle Your InboxAlly Seed Emails. Senders (Sender Profiles) Create, update, and manage your sender profiles and their engagement rules. Retrieve sender profiles: List all sender profiles with filtering by status, tag, domain, creation date, or recent activity Get sender profiles by domain or by tag for bulk operations Create and update: Create new sender profiles with engagement rules Update sender profile details Change sender status (active/inactive) individually, by domain, or by tag Engagement rules: The API lets you set and change engagement rules on sender profiles. Available engagement presets: Preset Use case default Standard engagement for healthy senders warmup Higher engagement signals for new or cold domains repair Aggressive engagement to recover damaged reputation boost Elevated engagement for a temporary push protect Maintenance-level engagement for established senders custom Set your own percentages for each engagement type With custom engagement, you control the percentage for each action: open, scroll down, spam-to-inbox, promo-to-inbox, mark important, reply, and click link. You can update engagement rules on individual sender profiles, or in bulk by domain or tag. Broadcasts Pull placement and deliverability data for your email campaigns. Retrieve broadcast data: List recent broadcasts with placement breakdowns: total emails, primary inbox, promotions, spam, and inboxing percentage Filter by email provider (Gmail, Yahoo, GSuite, Hotmail, Outlook, MS365) or by sender (from_email) Get detailed data for a specific broadcast by ID Broadcasts are auto-grouped by subject, sender, and arrival date. This is the same data you see on your InboxAlly Dashboard — the API lets you pull it into your own systems. Pagination The API uses cursor-based pagination for endpoints that return lists. Use the limit parameter to control page size and page_token to navigate through results. The response includes a next_page_token value when more results are available. Getting Started Generate your API key in the InboxAlly dashboard under My Account → API. Review the full API reference at apidocs.inboxally.com. The docs are interactive (Stoplight-powered) with request and response examples for every endpoint. Make a test request to verify your key works. Good starting points: GET /v3/seeds — list your seed email addresses GET /v3/senders — list your sender profiles GET /v3/broadcasts — list recent broadcasts with placement data Build from there based on your use case. Common Use Cases Agency and reseller management: Manage sender profiles across multiple client domains via API. Bulk-update engagement rules by domain or tag — for example, switch all senders on a client's domain from warmup to default once placement stabilizes. Custom reporting dashboards: Pull broadcast data (inboxing percentage, primary/promo/spam breakdown by provider) into your own reporting tools or client-facing dashboards. Automated seed shuffling: Schedule a monthly shuffle via a cron job using the shuffle trigger endpoint. Check cooldown status first, trigger the shuffle with your preferred method, then fetch the updated seed list to sync to your ESP. ESP integration: Fetch your seed list programmatically to sync into platforms that do not have a native InboxAlly integration. Automate the import process so seeds stay current without manual effort. Engagement tuning: Programmatically switch sender profiles between engagement presets based on performance. For example, if a sender's inboxing rate drops below a threshold, automatically switch from default to repair. Rate Limits The API enforces rate limits to ensure stability. If you hit a limit, the response will include a Retry-After header indicating when you can make your next request. For most use cases — checking broadcasts, syncing seeds, updating sender profiles — you will not encounter rate limits. Full API Reference The complete interactive documentation is at apidocs.inboxally.com. Every endpoint includes request parameters, example payloads, and response schemas. For API-specific questions, contact support@inboxally.com. Related Articles Understanding and Utilizing Seed Emails How to Shuffle Your InboxAlly Seed Emails Integrate Klaviyo with InboxAlly Integrate HubSpot with InboxAlly How to Use InboxAlly with Any Email Platform Email List Verification --- ## How do I connect AWeber to InboxAlly? - URL: https://www.inboxally.com/docs/integrations/integrate-aweber-with-inboxally/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Connect AWeber to InboxAlly for automatic list cleaning and seed balancing — sync contacts and validate addresses without manual CSV imports. - Keywords: AWeber InboxAlly integration, connect AWeber to InboxAlly, AWeber email deliverability, AWeber list cleaning, AWeber seed list setup > To connect AWeber to InboxAlly, go to **My Account → Integrations**, click **Enable** on the AWeber card, enter your AWeber credentials, and authorize the connection. Once enabled, InboxAlly can read your AWeber contacts, validate addresses, and sync seed emails into your lists automatically. The AWeber integration connects your AWeber account to InboxAlly so the platform can read your contact lists, validate email addresses, and automatically sync seed emails into your audiences — replacing manual CSV imports with a live connection. Once enabled, you get access to InboxAlly’s list cleaning and automatic seed balancing features for every AWeber list you manage. Before You Start Here are some things to know before you begin this process. This article is about how to allow InboxAlly to read your Aweber contacts. You must have a Aweber account to complete this process. To sign up, visit aweber.com. AWeber offers lots of documentation about integrations and the access they allow here. Connect InboxAlly with your Aweber account You'll need to authorize a connection between InboxAlly and Aweber. To connect your Aweber account follow these steps. Click Integrations option under the MyAccount section Click Enable on the Aweber card to setup the connection Enter your AWeber credentials Authorize the Integration You'll return to your InboxAlly account and see that the connection is now enabled. --- ## How do I connect GetResponse to InboxAlly? - URL: https://www.inboxally.com/docs/integrations/integrate-getresponse-with-inboxally/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Connect GetResponse to InboxAlly for automatic list cleaning and seed balancing — sync contacts and validate addresses without manual CSV imports. - Keywords: GetResponse InboxAlly integration, connect GetResponse to InboxAlly, GetResponse email deliverability, GetResponse list cleaning, GetResponse seed list setup > To connect GetResponse to InboxAlly, go to **My Account → Integrations**, click **Enable** on the GetResponse card, enter your GetResponse credentials, and authorize the connection. Once enabled, InboxAlly can read your GetResponse contacts, validate addresses, and sync seed emails into your lists automatically. The GetResponse integration connects your GetResponse account to InboxAlly so the platform can read your contact lists, validate email addresses, and automatically sync seed emails into your audiences — replacing manual CSV imports with a live connection. Once enabled, you get access to InboxAlly’s list cleaning and automatic seed balancing features for every GetResponse list you manage. Before You Start Here are some things to know before you begin this process. This article is about how to allow InboxAlly to read your GetResponse contacts. You must have a GetResponse account to complete this process. To sign up, visit getresponse.com. GetResponse offers lots of documentation about integrations and the access they allow here. Connect InboxAlly with your GetResponse account You'll need to authorize a connection between InboxAlly and GetResponse. To connect your GetResponse account follow these steps. Click Integrations option under the MyAccount section Click Enable on the GetResponse card to setup the connection Enter your GetResponse credentials Authorize the Integration You'll return to your InboxAlly account and see that the connection is now enabled. --- ## How do I connect HubSpot to InboxAlly? - URL: https://www.inboxally.com/docs/integrations/integrate-hubspot-with-inboxally/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Sync InboxAlly seeds into HubSpot lists, validate contacts in real time, and run recurring revalidation — all from your InboxAlly dashboard. - Keywords: HubSpot InboxAlly integration, connect HubSpot to InboxAlly, HubSpot email deliverability, HubSpot contact validation, HubSpot seed sync, HubSpot list hygiene > To connect HubSpot to InboxAlly, go to **My Account → Integrations → HubSpot**, click **Connect HubSpot**, and authorize via OAuth. Once connected, InboxAlly automatically syncs seeds into your HubSpot lists, validates new contacts in real time, and runs recurring revalidation to maintain list health. The InboxAlly + HubSpot integration enables automatic contact validation, seed syncing, and real-time contact hygiene within your HubSpot CRM. Once connected, InboxAlly can: Automatically sync InboxAlly seed emails into HubSpot lists Validate new or existing HubSpot contacts using your validation credits Perform recurring revalidation to maintain list health Provide real-time monitoring of sync and validation activity Prerequisites Before you begin: Active InboxAlly account with available validation credits Admin access in your HubSpot workspace Ability to install apps or manage integrations in HubSpot Step 1: Connect and Authorize HubSpot Log in to your InboxAlly account. Go to My Account → Integrations → HubSpot. Click Connect HubSpot. You’ll be redirected to HubSpot for authorization. Select your HubSpot account and click Connect App. After authorization, you’ll be redirected back to InboxAlly. The connection will initialize automatically and begin syncing data. Step 2: Review Integration Status Once connected, you’ll see your HubSpot integration dashboard: Metric Description Integration Status Shows if the integration is working normally Token Displays validity and expiration date Webhook Shows whether the webhook is active and last activity time Contacts Processed Displays number of HubSpot contacts synced in the last 7 days Validations Shows total validations and success rate Seed Sync Displays number of InboxAlly seeds successfully synced Step 3: Configure Integration Settings After connecting, customize the integration behavior using the settings below. Sync IA Seeds Toggle Yes to automatically sync InboxAlly seed addresses to HubSpot. Requires an active InboxAlly subscription. Max Seeds to Sync Set the maximum number of seeds to sync. Default: 100 Click Save after making changes. Validate New Contacts Enable this toggle to automatically validate new HubSpot contacts as they are added. This uses your InboxAlly validation credits. Regularly Revalidate All Contacts Turn Yes to enable recurring revalidation for all contacts. Choose your preferred Revalidation Interval (Monthly, Quarterly, etc.). Validation Rules Set the conditions InboxAlly uses to mark an email as valid. Example: “OK, Accept-All, and Unknown.” Manual Revalidation Click Revalidate now to trigger a full revalidation run. Contacts validated within the past 24 hours will be skipped. Monitoring & Logs The integration updates every few minutes to reflect sync and validation events. You can monitor: Webhook Activity: Timestamp of the last event received from HubSpot Sync Logs: Details of recent syncs and validations Available Credits: Your remaining InboxAlly validation credits These help ensure your integration is healthy and up to date. Troubleshooting Issue Cause Solution Token expired Authorization older than 30 days Click Reauthorize on the HubSpot integration page No contacts syncing Integration permissions missing or webhook inactive Reconnect integration and reauthorize access Validation not working No available credits Add credits under Billing → Add Credits Seeds not appearing Sync disabled or limit reached Enable “Sync IA Seeds” and increase “Max Seeds to Sync” Low validation success rate Invalid or inactive contacts in HubSpot Use InboxAlly filters to clean contact lists Uninstalling the Integration To disconnect InboxAlly from HubSpot: In HubSpot, go to Settings → Connected Apps. Locate InboxAlly and click Disconnect. In InboxAlly, go to Integrations → HubSpot → Disconnect. Confirm to remove webhook and API permissions. Frequently Asked Questions (FAQ) Q: How often does InboxAlly sync with HubSpot? A: The sync runs automatically every few minutes through the active webhook. Q: Does this affect existing HubSpot lists? A: No, InboxAlly only validates and adds seed addresses; it doesn’t modify unrelated HubSpot data. Q: What happens when I run out of validation credits? A: Validation pauses automatically. Refill credits to continue validating. Q: Can I choose which HubSpot lists are validated? A: Yes, you can configure contact lists or pipelines when setting up the integration. --- ## How do I connect Klaviyo to InboxAlly? - URL: https://www.inboxally.com/docs/integrations/integrate-klaviyo-with-inboxally/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Sync InboxAlly seeds into Klaviyo as profiles, validate new subscribers via webhooks, and reenroll seeds for fresh engagement data. - Keywords: Klaviyo InboxAlly integration, connect Klaviyo to InboxAlly, Klaviyo email deliverability, Klaviyo seed sync, Klaviyo contact validation, Klaviyo inbox placement > To connect Klaviyo to InboxAlly, go to **My Account → Integrations → Klaviyo**, click **Connect Klaviyo**, and authorize via OAuth. Once connected, InboxAlly automatically syncs seeds into Klaviyo as profiles, validates new subscribers via webhooks, and supports seed reenrollment for fresh engagement data. The InboxAlly + Klaviyo integration enables automatic seed synchronization, real-time contact validation, and advanced deliverability monitoring directly within your Klaviyo account. Once connected, InboxAlly can: Automatically sync InboxAlly seed emails into Klaviyo as profiles Validate new subscribers in real-time via webhooks Perform optional seed reenrollment for fresh engagement data Provide detailed metrics on sync and validation activity Prerequisites Before you begin: Active InboxAlly account with an active subscription Admin access in your Klaviyo account Ability to authorize third-party apps in Klaviyo For more integration options, see the Integrations Guide. Step 1: Connect and Authorize Klaviyo Log in to your InboxAlly account. Go to My Account → Integrations → Klaviyo. Click Connect Klaviyo. You'll be redirected to Klaviyo for authorization. Review the requested permissions and click Allow. After authorization, you'll see a success page and be automatically redirected back to InboxAlly. The integration will begin syncing your seed contacts within minutes. Permissions Requested InboxAlly requests the following Klaviyo permissions: Profiles: Read and write profile data for seed management Lists: Create and manage seed contact lists Webhooks: Receive real-time subscriber events Events: Track engagement and deliverability data Step 2: Review Integration Status Once connected, you'll see your Klaviyo integration dashboard with real-time metrics: Metric Description Integration Status Shows if the integration is healthy and working OAuth Token Displays token validity and expiration date Webhook Status Shows webhook activity and last event received Seeds Synced Number of InboxAlly seeds currently in Klaviyo Contacts Processed Weekly count of contacts validated or synced Validation Rate Success rate for email validations Step 3: Configure Integration Settings After connecting, customize the integration behavior using the settings below. Sync IA Seeds Toggle Yes to automatically sync InboxAlly seed addresses to Klaviyo. Seeds are synced every 10 minutes to keep your lists current. Max Seeds to Sync Set the maximum number of seeds to sync to Klaviyo. Default: 100 Increase this to match your testing volume needs. Validate New Contacts Enable this toggle to automatically validate new Klaviyo subscribers via webhooks. When someone subscribes, InboxAlly validates their email in real-time. This uses your InboxAlly validation credits. Enable Seed Reenrollment Enterprise feature that creates fresh engagement data for more accurate deliverability testing. Reenrollment Cycle (Days) Set how many days it takes to cycle through all seed profiles. Example: 10 days means ~10% of seeds are refreshed each day. Lower values = faster refresh, higher API usage. Validation Rules Configure which validation statuses are considered "valid." Options include: OK only, OK + Accept-All, or custom rules. Understanding Seed Management How Seeds Are Synced InboxAlly maintains your seed contacts in Klaviyo with special properties: Property Description ia_managed "yes" for active seeds, "no" for removed ia_managed_type Seed type (standard, placement_tester, auditor) ia_validation_status Current validation status (valid/invalid) ia_validation_details Detailed validation result (ok, invalid, etc.) ia_mailbox_provider Email provider (Gmail, Outlook, etc.) ia_last_sync Timestamp of last sync What Happens to Removed Seeds When seeds are removed from your InboxAlly allocation: The Klaviyo profile is NOT deleted Properties are updated to mark it as inactive Historical engagement data is preserved The profile can be reactivated if needed Monitoring & Logs The integration dashboard provides detailed insights: Weekly Metrics Contacts Processed: Total sync and validation operations Seeds Added: New seed profiles created this week Validation Success Rate: Percentage of successful validations Sync Performance Last Sync Time: When seeds were last synchronized Sync Duration: How long the sync took Jobs Completed: Number of sync jobs this week Performance Insights InboxAlly provides actionable insights based on your metrics: Sync performance recommendations Validation rate alerts Credit usage warnings Troubleshooting Issue Cause Solution Token expired OAuth authorization older than 6 months Click Reconnect on the Klaviyo integration page Webhook inactive Webhook subscription failed or disabled Click Setup Webhook to recreate the webhook Seeds not syncing Sync disabled or max seeds reached Enable "Sync IA Seeds" and check "Max Seeds" setting Validation not working No available credits or feature disabled Add credits and enable "Validate New Contacts" Low validation rate Poor quality contacts subscribing Review your signup sources and list hygiene Slow sync performance Large seed count or API rate limits Normal behavior—Klaviyo enforces rate limits Disconnecting the Integration To disconnect InboxAlly from Klaviyo: In InboxAlly, go to Integrations → Klaviyo. Click Disconnect Integration. Confirm the disconnection. This will: Remove all webhook subscriptions from Klaviyo Clear OAuth tokens from InboxAlly Stop all automatic syncing and validation Note: Your seed profiles remain in Klaviyo but will be marked as no longer managed by InboxAlly. Frequently Asked Questions (FAQ) Q: How often does InboxAlly sync seeds with Klaviyo? A: Seeds are synced automatically every 10 minutes to keep your lists current. Q: Does this affect my existing Klaviyo profiles? A: No, InboxAlly only manages profiles it creates. Your existing contacts are untouched. Q: What happens when I run out of validation credits? A: Validation pauses automatically. Seed syncing continues (it doesn't use credits). Refill credits to resume validation. Q: Can I control which seeds are synced to Klaviyo? A: Yes, use the "Max Seeds to Sync" setting to limit the number. Seeds are selected based on your InboxAlly allocation. Q: Will synced seeds appear in my Klaviyo segments and flows? A: Yes, seed profiles are regular Klaviyo profiles. You can filter them using the ia_managed property to include or exclude them from campaigns. Q: How do I know if the integration is working? A: Check the integration dashboard for: Green "Healthy" status indicator Recent "Last Sync" timestamp Active webhook status Non-zero "Seeds Synced" count Best Practices Start with default settings — The defaults work well for most users Monitor your first week — Check metrics daily to ensure everything is working Adjust max seeds as needed — Match this to your typical campaign volume Keep credits available — Validation pauses without credits Need Help? If you encounter issues not covered here: Contact support@inboxally.com --- ## How do I connect Mailchimp to InboxAlly? - URL: https://www.inboxally.com/docs/integrations/integrate-mailchimp-with-inboxally/ - Section: Integrations - Last Modified: 2026-03-11 - Description: Connect Mailchimp to InboxAlly for automatic list cleaning and seed balancing — sync contacts and validate addresses without manual CSV imports. - Keywords: Mailchimp InboxAlly integration, connect Mailchimp to InboxAlly, Mailchimp email deliverability, Mailchimp list cleaning, Mailchimp seed list setup > To connect Mailchimp to InboxAlly, go to **My Account → Integrations**, click **Enable** on the Mailchimp card, enter your Mailchimp credentials, and authorize the connection. Once enabled, InboxAlly can read your Mailchimp audiences, validate addresses, and sync seed emails automatically. The Mailchimp integration connects your Mailchimp account to InboxAlly so the platform can read your audiences, validate email addresses, and automatically sync seed emails — replacing manual CSV imports with a live connection. Once enabled, you get access to InboxAlly’s list cleaning and automatic seed balancing features for every Mailchimp audience you manage. Before You Start Here are some things to know before you begin this process. This article is about how to allow InboxAlly to read your Mailchimp contacts. You must have a Mailchimp account to complete this process. To sign up, visit mailchimp.com. Mailchimp offers lots of documentation about integrations and the access they allow here. For more details on setting up connections, see the Integrations Guide. Connect InboxAlly with your Mailchimp account You'll need to authorize a connection between InboxAlly and Mailchimp. To connect your Mailchimp account follow these steps. Click Integrations option under the MyAccount section Click Enable on the Mailchimp card to setup the connection Enter your Mailchimp credentials Authorize the Integration You'll return to your InboxAlly account and see that the connection is now enabled. --- ## How do I earn InboxAlly Platform Certification? - URL: https://www.inboxally.com/docs/programs-certification/inboxally-platform-certification/ - Section: Programs & Certification - Last Modified: 2026-03-11 - Description: Complete product training to earn your Platform Certified badge — covering seed campaigns, placement reports, and send optimization. - Keywords: InboxAlly platform certification, InboxAlly training, email deliverability certification, InboxAlly certified badge, seed campaign training > To earn InboxAlly Platform Certification, complete your product training and campaign walkthrough, demonstrate active platform use, then pass the certification review. To request certification, contact support@inboxally.com or speak with your onboarding manager. The badge is available to customers, agency partners, and team members. The InboxAlly Platform Certified badge is awarded to users who have demonstrated proficiency in using the InboxAlly platform to improve email deliverability and inbox placement performance. This certification signifies that the badge holder has completed product training and understands how to: Launch and manage seed-based deliverability campaigns Interpret inbox placement and detection reports Optimize send strategies based on platform insights Navigate and utilize InboxAlly’s core features effectively Who Earns This Certification? This badge is granted to: Internal teams at agencies using InboxAlly with multiple clients Advanced users who complete InboxAlly onboarding and training Deliverability professionals who demonstrate hands-on proficiency with the tool Earning this certification reflects a verified ability to confidently and effectively use the InboxAlly platform to improve inbox placement and monitor deliverability performance. Badge Authenticity Only individuals who meet the training criteria set by InboxAlly may display this badge on LinkedIn or their professional website. If you see this badge linked to this page, it means the individual has earned official recognition as a Platform Certified User. Want to Become Platform Certified? If you’re an InboxAlly user and want to earn this badge: Complete your training and campaign walkthrough Demonstrate active use of the platform Pass the InboxAlly Platform Certification review To request certification, please contact our team or speak with your InboxAlly onboarding manager. --- ## Does InboxAlly offer a white-label or agency solution? - URL: https://www.inboxally.com/docs/programs-certification/does-inboxally-have-a-white-labeled-version/ - Section: Programs & Certification - Last Modified: 2026-03-10 - Description: No white-label version, but three agency models: affiliate referrals (20% recurring), managed Sender Profiles, or agency-owned client accounts. - Keywords: InboxAlly white label, email deliverability tool for agencies, InboxAlly agency solution, white label inbox placement tool, InboxAlly affiliate program > InboxAlly does **not** offer a white-labeled version, but it's built to work well for agencies and deliverability consultants. Three common models: (1) **affiliate referrals** with 20% recurring commission, (2) **managed Sender Profiles** under one agency account, or (3) **agency-administered client accounts** for full control. InboxAlly does not offer a white-labeled version of the platform. That said, InboxAlly is built to work well for agencies and deliverability consultants. Below are three common ways partners use InboxAlly with clients—depending on how hands-on you want to be and who should own the account. Model 1: Affiliate program (client-owned accounts) What it is You refer clients to InboxAlly, and they create and manage their own InboxAlly account. You earn a 20% recurring commission for life on each referred customer (subscription-based, paid monthly as long as they remain a customer). Who it’s for Agencies/consultants who want a simple referral model Teams that don’t want to manage client logins, billing, or day-to-day execution Partners who want clients to choose the plan level that fits their needs Next steps Reach out to InboxAlly support to get set up with the Affiliate Program Have your client start a free trial and create their account: https://app.inboxally.com/register Model 2: Managed Sender Profiles (agency-managed under one account) What it is You manage multiple clients inside one InboxAlly account using Sender Profiles. Each client can have their own Sender Profile, and each profile can be assigned its own domain and/or IP address. You can also use InboxAlly’s Reports and Dashboard to pull performance and results per client (for example, by Sender Profile and by provider). Who it’s for Agencies/consultants who want to run deliverability improvements as a managed service Teams that prefer to keep execution centralized (no client onboarding into the app) Partners managing multiple domains/brands and needing clean separation per client Key details Plus plans and above support 5+ Sender Profiles Works with any email-sending service (ESP) you use to send campaigns Next steps Start a free trial (or log in) and set up client Sender Profiles using Sender Profiles and the Setup Wizard Use Reports to generate client-specific results and share them as part of your deliverability service Model 3: Agency admin model (separate client accounts, agency-administered) What it is InboxAlly can be structured so you (the agency) administer separate client accounts, while clients can still access the InboxAlly platform themselves. This is useful when clients want visibility (or to participate in setup and monitoring), but you still want to control configuration and ongoing management. Who it’s for Agencies/consultants working with clients who require their own account access Engagements where the client’s internal team needs to see reporting and status Partners who want clearer separation between clients for administration and permissions Next steps Contact InboxAlly support and ask about the agency account administration model Decide which responsibilities stay with your team vs. the client (setup, monitoring, reporting cadence, etc.) If you tell us how you prefer to work (referral-only, fully managed, or shared access), we can recommend the best model for your agency and client mix. --- ## How do I get my emails into Gmail's Primary inbox? - URL: https://www.inboxally.com/docs/provider-deliverability-guides/gmail-deliverability-reach-primary-avoid-promotions-and-spam/ - Section: Provider Deliverability Guides - Last Modified: 2026-03-11 - Description: Gmail routes mail by domain reputation and engagement signals. Meet the 2024 bulk sender requirements and land in Primary instead of Promotions or Spam. - Keywords: Gmail deliverability, how to reach Gmail Primary inbox, avoid Gmail Promotions tab, Gmail spam folder fix, Gmail bulk sender requirements 2024, Gmail domain reputation > To reach Gmail's Primary tab and avoid Promotions or Spam, build strong domain reputation through consistent engagement (opens, clicks, replies) and meet the 2024 bulk sender requirements — SPF, DKIM, DMARC, one-click unsubscribe, and spam rate under 0.3%. To move from Promotions to Primary, reduce promotional cues (heavy HTML, multiple CTAs, tracking links), write conversational copy, segment by intent, and encourage replies. Domain reputation is the single most important factor. Gmail deliverability means where your message lands inside Gmail—the Primary inbox, the Promotions tab, or Spam—not just whether it was “delivered.” For most senders, Gmail is the #1 mailbox provider because it consistently represents 30%+ of typical email lists, and its filtering decisions often predict how other providers will treat your mail. If Gmail is sending you to spam, it’s almost always because your domain’s reputation and recent engagement signals (opens, clicks, replies, deletes-without-reading, “Mark as spam”) indicate low trust. Gmail is reputation-first and engagement-driven: it learns from how real recipients interact with your mail over time, and it weights domain reputation more than IP reputation for long-term outcomes. The Promotions tab isn’t spam—it’s a classification. Promotions generally means Gmail believes your message is marketing-oriented (templates, links, images, tracking, promotional language, bulk patterns). Visibility can be lower than Primary, but placement in Promotions can still perform well when engagement is strong. For senders who send 5,000+ messages/day, Gmail’s 2024 bulk sender requirements include: SPF, DKIM, and DMARC authentication One-click unsubscribe support (per RFC 8058) and easy opt-out Keeping spam rates low in Google’s measurement systems On complaints, Gmail expects a spam complaint rate under 0.3%, and best practice is to target under 0.1% to protect inbox placement. Set your strategy around the asset Gmail actually rewards: your domain reputation. It compounds slowly, breaks quickly, and is the foundation for consistently reaching the Gmail inbox. How Gmail’s spam filtering actually works (reputation-first + engagement signals) Gmail doesn’t run a single “spam test.” It uses layered filtering that combines technical validation, sender reputation, and user behavior to decide Inbox vs. Promotions vs. Spam (and sometimes throttling/deferrals). Gmail’s layered filtering (from first gate to final placement) Authentication & identity alignment Checks SPF, DKIM, and DMARC and whether they align with the visible From domain (a core part of Gmail’s sender guidelines). Misalignment (e.g., DKIM signing a different domain than the From) increases risk even if “something passes.” Reputation scoring (the primary driver) Gmail assigns reputation to multiple entities: From domain, DKIM signing domain, sending IP, and sometimes subdomains. This reputation is updated continuously based on complaint rates, bounces, and engagement patterns. Content + URL + behavioral heuristics Not just “spammy words.” Gmail evaluates link reputation, redirect chains, URL shorteners, attachment types, and template patterns seen in abuse. User-level personalization Gmail learns per-recipient preferences: who they read, ignore, delete, or mark as spam. Two subscribers can receive the same campaign and see different placement. Final placement decision Gmail chooses Primary/Promotions/Updates/Spam, or applies rate limiting when trust is low. Reputation inputs: why domain reputation beats IP reputation For most modern senders, domain reputation matters more than IP reputation because Gmail wants a stable identity that persists across infrastructure changes. A shared IP or ESP can’t “wash” a bad domain. If your From domain has a history of low engagement or complaints, moving IPs rarely fixes placement. Conversely, a strong domain can often tolerate minor IP fluctuations—especially when authentication is aligned and engagement is consistent. This is why warm-up and remediation should focus on improving domain-level signals, not just rotating IPs. Engagement signals Gmail can infer (and what actually moves the needle) Gmail doesn’t rely on “opens” the way marketers do (image loads are noisy). Stronger signals include: Positive signals Replies (especially non-template replies) “Not spam” actions Moving a message to the inbox / dragging to Primary Starring, saving, or forwarding Adding the sender to contacts Negative signals Spam complaints (Gmail’s key suppression trigger) Deletes without reading / rapid archiving Low read time, low repeat opens, and long-term ignoring InboxAlly generates real Gmail engagement via seed emails, reinforcing the signals Gmail trusts most (see How Does InboxAlly Work). Common root causes of spam placement (mapped to Gmail’s model) Misaligned acquisition → low engagement + higher complaints → domain reputation drops. Sudden volume spikes → reputation can’t “keep up” → throttling or spam placement. Low-engagement cohorts (old, unresponsive segments) → negative engagement signals dominate. Poor authentication alignment → identity uncertainty → higher filtering sensitivity (review Gmail and Yahoo changes for bulk senders in 2024). Complaint-driven suppression → once spam rate rises, Gmail reduces inboxing broadly; monitor in Postmaster Tools (see Integrate Google Postmaster Tools with InboxAlly). Gmail’s 2024 bulk sender requirements (5,000+ messages/day): what to implement and how to verify Provider Email Authentication Requirements This comparison shows the bulk sender authentication requirements for Gmail, Microsoft Outlook, and Yahoo Mail — the three providers that collectively handle the majority of consumer and business email. Gmail, Microsoft, and Yahoo bulk sender requirements compared across authentication, spam rates, and enforcement. 1. All three providers require SPF authentication for bulk senders sending 5,000+ emails per day. 2. All three providers require DKIM authentication for bulk senders. 3. All three providers require DMARC with at least p=none policy. 4. Google enforces a two-tier spam rate: 0.1% target with 0.3% hard maximum. Microsoft and Yahoo enforce 0.3% maximum. 5. Google and Yahoo require RFC 8058 one-click unsubscribe. Microsoft strongly recommends it. 6. Non-compliant mail faces rejection or spam filtering depending on provider and violation. If you send 5,000+ messages/day to Gmail, Google treats you as a bulk sender and expects the following controls to pass consistently. Mandatory requirements (and what “pass” means) SPF authentication + alignment Pass in practice: Gmail can validate SPF for the sending infrastructure and the authenticated domain aligns with the visible From: domain (organizational domain match). DKIM authentication + alignment Pass in practice: DKIM signature verifies and the DKIM d= domain aligns with the visible From: domain (organizational domain match). Misalignment (e.g., From: brand.com but DKIM d= vendor-mail.com) fails alignment even if DKIM “passes.” DMARC published + alignment Pass in practice: A DMARC record exists at _dmarc.yourdomain.com, and either SPF or DKIM is aligned (DMARC “pass”). Gmail expects DMARC for bulk senders even if you start with a monitoring policy. TLS encryption Pass in practice: Messages are delivered over TLS (encrypted in transit). In Google Postmaster Tools, Encryption should show near-100% for outbound mail. One-click unsubscribe (RFC 8058) Pass in practice: Marketing mail includes a working List-Unsubscribe header with a one-click method (typically List-Unsubscribe-Post: List-Unsubscribe=One-Click) and the request succeeds without requiring login. Gmail spam complaint thresholds (why <0.1% is the real target) Google’s published threshold is < 0.3% spam complaint rate. Treat that as a hard ceiling, not an operating target. Aim for < 0.1% because: Complaint rate is complaints ÷ delivered volume. On small sends, a few complaints create big swings (e.g., 3 complaints on 1,000 delivered = 0.3%). Gmail reacts to spikes, not averages. A single campaign to a cold segment can push you over the line and depress domain reputation for days. Complaint rate is correlated with other negative signals (low engagement, high deletes-without-open), which can increase spam placement even before you hit 0.3%. Implementation checklist (what to configure and how to verify) DNS authentication Publish SPF for your sending sources (avoid multiple SPF records). Enable DKIM and confirm the selector records resolve. Publish DMARC at _dmarc with reporting addresses. Verify alignment Ensure From: uses your branded domain. Ensure DKIM d= matches the same organizational domain as From. Ensure SPF “Mail From/Return-Path” aligns where possible. DMARC policy progression Start with p=none (monitor) → move to p=quarantine → then p=reject once legitimate sources are aligned and stable. Unsubscribe UX Add header-based one-click unsubscribe (RFC 8058). Provide a fast landing page confirming the opt-out (no login, minimal steps), and honor requests promptly. Resources to execute (InboxAlly + internal guides) Follow Gmail and Yahoo Changes for Bulk Senders in 2024 for the full requirement breakdown and rollout notes. Implement one-click correctly using RFC 8058 Compliance. Monitor ongoing pass/fail status and alignment using InboxAlly Domain Reports (authentication visibility across SPF/DKIM/DMARC and trend monitoring). Primary vs Promotions vs Spam: how the Promotions tab works and whether you should fight it Promotions isn’t spam (but it is different) Gmail’s Promotions tab is a categorization choice, not a penalty. Messages in Promotions are typically: Less visible by default: users often open Gmail to the Primary tab first, and may only scan Promotions in batches. Handled differently by notifications: many users have notifications tuned for Primary (or “important”) messages, while Promotions may be silent. Consumed with a different mindset: Promotions is where people expect newsletters, product updates, and offers—so opens can be lower, but intent can be higher when they do engage. It’s acceptable (and often ideal) for newsletters, announcements, and discounts to land in Promotions—especially if conversions are strong and spam complaints stay low. What drives Gmail’s tab placement Gmail uses a mix of message-level, sender-level, and user-level signals. Common drivers include: Message structure: heavy HTML templates, multiple images, hero banners, buttons/CTAs, and “marketing-style” layouts. Commercial intent cues: pricing language, urgency (“limited time”), coupon codes, and repeated calls to buy. Link patterns: many links, tracking parameters, shorteners/redirect chains, or inconsistent domains between links and From domain. Sending domain history: consistent positive engagement improves trust; inconsistent volume or poor engagement can push mail away from Primary. User interactions: opens, replies, moving messages between tabs, starring, and “Not spam” actions are strong personalization signals. Practical levers (without “gaming” Gmail) To influence placement ethically, focus on alignment and engagement: Segment by intent: send lifecycle/relationship emails to engaged users; keep broad promos separate. Write more conversational copy: fewer graphics, fewer CTAs, more plain-text structure when appropriate. Reduce promotional cues: limit banners, excessive links, and sales-heavy subject lines for messages that should feel personal. Be consistent: stable From name, sending domain, and cadence help Gmail learn what you are. Encourage real engagement: ask for replies, and prompt subscribers to save your address/contact. InboxAlly helps by generating real Gmail engagement signals (opens, replies, inbox placement behaviors) via seed emails—supporting stronger Gmail domain reputation over time. See How Does InboxAlly Work and Integrate Google Postmaster Tools with InboxAlly. “How do I get out of Promotions?” A decision framework Optimize for Primary when the email is: High-value lifecycle/transactional (onboarding steps, account/security, receipts, critical updates) Time-sensitive and personal (1:1-style check-ins, support follow-ups) Measured on reply rate, task completion, retention Embrace Promotions when the email is: A newsletter, content round-up, or offer Measured on revenue per send, conversions, and long-term engagement Still meeting Gmail’s sender guidelines (low complaints, strong authentication) Measure outcomes by tab: track complaints, replies, conversions, and Postmaster reputation trends, not just “Primary vs Promotions.” Google Postmaster Tools: the Gmail metrics that matter (and how to act on them) Google Postmaster Tools (GPT) is Gmail’s “health dashboard” for bulk senders. It won’t explain every inbox vs. Promotions decision, but it will show whether Gmail trusts your domain, your IPs, and your mailing practices. Setup prerequisites (and how to read the data) To see meaningful metrics, you need: Domain verification: Add the DNS TXT record for the exact sending domain (or subdomain) you use in the From/Return-Path alignment. Sufficient volume: GPT only populates when Gmail sees enough traffic from your domain/IPs. Low volume can mean missing days or “no data.” Trend-first interpretation: Treat GPT as a 7–30 day trend tool, not a single-day scoreboard. One bad day can be noise; sustained movement usually reflects a real change in list quality, content, or sending patterns. Key metrics (what “good” looks like) Domain Reputation: Gmail’s trust in your domain (most important). Good: High/Medium and stable. Risk: sustained drop to Low/Bad. IP Reputation: Trust in the sending IP. Good: High/Medium. Risk: Low/Bad, especially after IP changes or new infrastructure. Spam Rate: % of mail marked spam by users (per Gmail). Good: consistently <0.1%; must stay <0.3% to meet Gmail bulk sender expectations. Authentication (pass rates): SPF, DKIM, and DMARC alignment/pass. Good: near-100% pass for the stream you’re measuring; dips indicate misalignment, forwarding issues, or config drift. Encryption: TLS usage between servers. Good: ~100%. Lower values can signal delivery path issues or outdated sending infrastructure. Turn metrics into actions (and isolate the culprit) Domain reputation drops Pause/slow the riskiest sends (cold segments, broad promos). Tighten targeting and remove unengaged recipients. Use InboxAlly to rebuild positive Gmail engagement signals; validate improvement against GPT trends. Spam rate rises Identify the campaign/segment spike (often acquisition or reactivation). Add clearer expectations, reduce frequency, and ensure one-click unsubscribe (see RFC 8058 Compliance). If you use Gmail’s complaint data, pair it with Gmail Complaint Feedback Loop Setup. Authentication dips Re-check SPF/DKIM/DMARC alignment for each sending domain/subdomain. Confirm recent ESP/infrastructure changes didn’t introduce a new, unauthenticated stream. Isolate marketing vs. lifecycle Separate by subdomain (e.g., marketing.example.com vs. notify.example.com) and/or dedicated IP pools so GPT trends map to a single stream. To connect GPT signals directly to InboxAlly outcomes, follow Integrate Google Postmaster Tools with InboxAlly and compare reputation/spam-rate trends with InboxAlly reporting. Gmail Complaint Feedback Loop (FBL): what it is, how to register, and how to use the data Gmail’s Complaint Feedback Loop (FBL) reports individual user spam-complaint events (when a recipient hits Report spam) for mail you send to Gmail. This is different from Google Postmaster Tools “spam rate,” which is an aggregate rate calculated across eligible traffic and shown as a trend. FBL is event-level and actionable; Postmaster is directional and diagnostic. Limitations (by design): Privacy constraints: complaint reports are minimized and may not include full recipient identity or message content. Coverage is not universal: not every message/recipient will generate a report, and reports can be delayed. Not a deliverability score: use it to drive suppression and root-cause analysis, not to “prove” inbox placement. Registration + technical requirements (high level) To receive FBL reports, you’ll need: Authenticated mail (SPF/DKIM aligned; DMARC recommended) and consistent sending domains. Correct headers so Gmail can map a complaint back to your stream (e.g., stable identifiers like campaign/message IDs). A processing endpoint (mailbox or webhook) to ingest reports and log them reliably. Follow the step-by-step guide in Gmail Complaint Feedback Loop Setup for exact prerequisites and validation. Operationalizing FBL data (what to do with it) Immediate suppression: on first complaint, add the address to a “do-not-email” list across all systems. No retries. Cohort analysis: group complaints by: acquisition source / lead magnet segment (new vs. long-term, engaged vs. cold) campaign + subject line + offer Adjust creative + frequency: reduce volume to high-complaint cohorts, tighten targeting, and rewrite misleading subject lines or overly aggressive CTAs. Reducing complaints is essential for Gmail’s bulk sender requirements: keep complaint rate <0.3% and aim for <0.1%. Pair FBL suppression with engagement improvements using InboxAlly (see How Does InboxAlly Work and Integrate Google Postmaster Tools with InboxAlly). Gmail-specific deliverability problems: greylisting, deferrals (421), and rate limiting Greylisting in Gmail terms is a temporary “not now” response where Gmail defers acceptance of mail to test sender behavior. Deferred delivery is the broader category: Gmail returns a temporary 4xx SMTP code and expects your server/ESP to retry. New senders—or “changed” senders (new domain, new IP, new From: pattern, sudden list growth, content shifts)—often see deferrals because Gmail is building confidence. Proper retries should be automatic, spaced out, and persistent (minutes to hours), not rapid-fire. Common SMTP symptoms (and what they usually mean) You’ll typically see temporary failures such as: 421 4.7.0 / 421 4.7.28 style deferrals “Try again later,” “rate limited,” “throttled,” or “temporary system problem” These usually indicate one (or more) of the following: Reputation uncertainty: Gmail isn’t sure how users will react yet. Volume spikes: Sending faster/higher than your recent baseline. Authentication inconsistencies: SPF/DKIM/DMARC alignment changes, rotating domains, or intermittent signing issues. Troubleshooting checklist Stabilize volume: Hold daily Gmail volume steady for several days; avoid campaign “bursts.” Ramp slowly: Increase in small, predictable steps (especially after domain/IP/content changes). Improve list quality: Remove inactive/unknown addresses; prioritize recent engagers. Keep authentication consistent: Ensure SPF, DKIM, and DMARC alignment stays stable across all streams (see Integrate Google Postmaster Tools with InboxAlly and Gmail and Yahoo Changes for Bulk Senders in 2024). Coordinate ESP retry logic: Confirm your ESP honors 4xx retries with exponential backoff and does not convert deferrals into bounces. Why Gmail does this Deferrals and rate limits are Gmail “buying time” to observe engagement signals (opens, replies, deletes, spam complaints). InboxAlly helps accelerate positive reputation signals so Gmail stops throttling and you consistently reach the inbox. Best practices to reach the Gmail inbox (and how warm-up impacts Gmail reputation) Gmail deliverability is reputation-first: Gmail weighs domain reputation and user engagement heavily, then uses those signals to decide inbox vs. spam (and sometimes Primary vs. Promotions). Use this Gmail-focused playbook to earn consistent positive signals. A Gmail-focused playbook Strong authentication + alignment Publish SPF and sign with DKIM for every stream. Enforce DMARC with alignment (the visible “From” domain should align with SPF/DKIM domains). This supports Gmail’s bulk sender requirements and reduces spoofing risk. Keep sending domains stable; avoid frequent “From” domain changes that reset reputation. List hygiene (protect reputation before you send) Remove hard bounces, role accounts, and chronically unengaged addresses. Verify new lists before importing to your ESP to prevent bounce spikes and spam complaints. Segmentation by engagement Prioritize recent open/click/reply segments and suppress long-term inactive recipients. Re-introduce older segments slowly (and only after inbox placement stabilizes). Consistent cadence Gmail dislikes erratic patterns. Keep volume and frequency predictable by day and by stream (newsletter vs. transactional vs. outreach). Content that earns positive Gmail signals Write for actions Gmail can observe: replies, “Not spam”, move-to-inbox, and contact adds. Keep formatting clean (balanced text-to-link ratio, minimal tracking clutter) and make the unsubscribe experience frictionless. Warm-up for Gmail: what matters most Warm-up is how you teach Gmail that your domain generates wanted mail. Done wrong, it looks like a compromised sender. Ramp volume gradually Increase daily Gmail volume in small steps; avoid doubling overnight. Maintain steady sending windows (time-of-day consistency helps). Start with highest-intent recipients Begin with people most likely to engage (recent customers, active subscribers, warm leads). Early engagement is a major reputation accelerator. Avoid sudden list imports Uploading a large, unverified list and blasting immediately is one of the fastest paths to spam placement and throttling. Protect reputation during changes Treat a new domain, new ESP, or new sending stream as a fresh warm-up. Even if your brand is known, Gmail evaluates the new sending identity and patterns. How InboxAlly helps Gmail reputation InboxAlly includes Gmail seed emails that generate real engagement signals—opens, clicks, and move-to-inbox actions—helping train Gmail’s filters and strengthen domain reputation over time. Pair this with InboxAlly’s platform tools: Placement Tester to measure Gmail inbox vs. spam placement before scaling. Email Audit to catch authentication, content, and sending-pattern issues that suppress Gmail inboxing. IA Assistant — open it in the InboxAlly app for guided help with Gmail deliverability issues, authentication checks, and warm-up recommendations. For the full mechanism, see How Does InboxAlly Work. Action checklist + recommended tools Verify new or aging lists with InboxAlly Email List Verification. Build a Gmail-safe ramp using the Email Warmup Planner. Run Placement Tester + Email Audit, then iterate based on Gmail results. Start improving inbox placement today with a free InboxAlly trial. --- ## How do I set up the Gmail complaint feedback loop? - URL: https://www.inboxally.com/docs/provider-deliverability-guides/gmail-complaint-feedback-loop-setup/ - Section: Provider Deliverability Guides - Last Modified: 2026-03-12 - Description: Register your domain in Google Postmaster Tools to access aggregate spam complaint data and domain reputation trends via Gmail's FBL. - Keywords: Gmail feedback loop setup, Google Postmaster Tools setup, Gmail complaint feedback loop, Gmail FBL registration, Gmail spam complaint data, Google Postmaster domain verification > To set up Gmail's complaint feedback loop, verify that SPF, DKIM, and reverse DNS are configured, then register and verify your domain in [Google Postmaster Tools](https://postmaster.google.com/). Add a `Feedback-ID` header to your outgoing emails with a 5–15 character sender identifier — without it, Gmail will not report campaign-level complaint data. The FBL provides aggregate spam rate and reputation trends, not individual complaint messages. Gmail's Feedback Loop (FBL) is a reporting feature in Google Postmaster Tools that surfaces aggregate reputation data for your sending domain — including spam complaint rates, domain reputation scores, and authentication status. Unlike traditional FBLs, it does not forward individual complaint messages or identify specific problematic sends; instead, it provides high-level trend data to help you monitor sending health over time. How Providers Report Complaints Gmail, Yahoo, and Microsoft each handle spam complaints differently. This diagram compares all three feedback mechanisms side by side. Cross-provider comparison of spam complaint feedback loops — Gmail (aggregate), Yahoo (individual), Microsoft (both). 1. Recipient clicks Report Spam. 2. Provider records complaint internally. 3. Reputation impact calculated against total inbox-delivered volume. 4. Signal routed to sender via feedback loop if configured. Gmail provides aggregate spam rate and reputation dashboards through Postmaster Tools. Yahoo forwards individual complaint messages in ARF format via its CFL program. Microsoft offers both individual complaints via JMRP and IP-level dashboards via SNDS, managed through one portal. Who is this relevant for? Postmaster data is useful for any sender targeting Gmail, but it is not essential for lower-volume mailers. Google requires senders to exceed an undisclosed volume and spam complaint threshold before data becomes available. How does Gmail Feedback Loop Help? The Gmail FBL gives insight into your campaigns that might receive an extremely high number of spam reports from Gmail users. Setup Requirements In order to setup the Gmail FBL there are a few steps involved. Pre-Check Before you start, ensure you have setup and validated SPF, DKIM, and ReverseDNS settings. If these are not configured correctly, you will not be able to complete the FBL setup. First, sign up with Gmail's Postmaster tools. You can follow Google's help to create your postmaster account. You will be asked to validate domain ownership so be sure to have the ability to add a TXT record to your DNS settings. Google also has a list of best practices for described in their Gmail Bulk Sender guidelines. Second, to implement the feedback loop, Gmail requires that you insert a special header called the Feedback-ID. It is necessary to add this Feedback-ID line in your email header and the method varies depending on what ESP or SMTP provider you are using for sending. If you don't know how to set this, you will need to find the instructions from your vendor. The header format should look as follows. You will always use the same SenderID and can vary the first three identifiers to align with your campaign. FBL data will be aggregated on each Identifier independently. This format also allows for the use of less than the 3 Identifiers, if needed. Feedback-ID: a:b:c:SenderID Field Description a, b, c Optional fields that can be used by the sender to embed up to 3 Identifiers (campaign/customer/other). These identifiers may change based on the attributes you wish to track. SenderID Mandatory unique Identifier (5–15 characters) chosen by the sender. It should be consistent across the mail stream. Examples of identifiers could be: campaign names or IDs segment names or IDs (new customer, etc) mail type names (newsletter, DRIP, notification, transactional, etc) customer types Example cid-2343:sid-3454::example-co holiday33::new-customers:example-co Data will not display if the SenderID is missing Postmaster Dashboards The most important indicators that Gmail’s Postmaster tool offers is the opportunity to track the percentage of spam complaints by domain name or sub-domain on a daily basis. The full list of reports are described in the table below. Report Description Spam Rate This is one of the most important indicators that Gmail’s Postmaster tool offers. It gives you the opportunity to track the percentage of spam complaints by domain name or sub-domain on a daily basis. IP Reputation The reputation of IPs on Gmail is: Bad, Low, Medium and High. Domain Reputation The reputation of domains on Gmail is: Bad, Low, Medium and High. Feedback Loop If you have correctly configured your Feedback-IDs, you can see the segments broken out to easily detect the sources of complaints in relation to your sending. Authentication This dashboard shows the percentage of emails that have been validated through the different authentication technologies like SPF or DKIM. --- ## How do I set up the Yahoo complaint feedback loop? - URL: https://www.inboxally.com/docs/provider-deliverability-guides/yahoo-complaint-feedback-loop-setup/ - Section: Provider Deliverability Guides - Last Modified: 2026-03-12 - Description: Create postmaster@ and abuse@ mailboxes, then register with Yahoo Mail Postmaster to receive spam rate reports when users mark your email as junk. - Keywords: Yahoo feedback loop setup, Yahoo complaint feedback loop, Yahoo Mail Postmaster registration, Yahoo CFL setup, Yahoo spam complaint reports, Yahoo email deliverability > Yahoo's Complaint Feedback Loop (CFL) sends you spam rate reports when Yahoo users mark your email as junk. To set it up, create `postmaster@` and `abuse@` mailboxes on your sending domain, then register through Yahoo Mail Postmaster. It's a useful monitoring tool, though not essential for lower-volume senders. Yahoo's Complaint Feedback Loop (CFL) is a reporting service through Yahoo Mail Postmaster that notifies you when Yahoo users mark your email as junk, providing spam rate data you can use to identify problem campaigns and suppress complainers. It is a useful monitoring tool for any sender targeting Yahoo domains, though not essential for lower-volume mailers. How Providers Report Complaints Gmail, Yahoo, and Microsoft each handle spam complaints differently. This diagram compares all three feedback mechanisms side by side. Cross-provider comparison of spam complaint feedback loops — Gmail (aggregate), Yahoo (individual), Microsoft (both). 1. Recipient clicks Report Spam. 2. Provider records complaint internally. 3. Reputation impact calculated against total inbox-delivered volume. 4. Signal routed to sender via feedback loop if configured. Gmail provides aggregate spam rate and reputation dashboards through Postmaster Tools. Yahoo forwards individual complaint messages in ARF format via its CFL program. Microsoft offers both individual complaints via JMRP and IP-level dashboards via SNDS, managed through one portal. How to Create the CFL There are a few steps required to get the CFL setup for Yahoo. Create your mailboxes The following two addresses need to be created for your sending domain. postmaster@ abuse@ Important These are standard email addresses that should always be setup on all sending domains. They are one of the most important methods used by mailbox providers, customers and others to ask questions, report abuse, and send notifications back to senders. These inboxes should be regularly monitored so that you can process complaints and unsubscribe requests. Register with Yahoo FBL First, navigate to the Yahoo Complaint Feedback Loop subscription form. The form will look like this. Next, complete all fields on the page. Make sure your reporting email and domain are entered correctly as you will get a verification code sent to postmaster@ after clicking submit. Field Name Field Description Example Company Name Your company name ExampleCo Contact Name Your deliverability manager's name Sam Smith Contact Email Your deliverability manager's email ssmith@example.co Reporting Email The abuse email address abuse@example.co Selector Enter * here for all * Domain Your sending domain example.co Last step, after submitting the form check your postmaster inbox and look for the validation code email from Yahoo. After you enter the code, you should see the success message. --- ## How do I set up Microsoft's JMRP and SNDS feedback programs? - URL: https://www.inboxally.com/docs/provider-deliverability-guides/microsoft-complaint-feedback-programs-jmrp-and-snds/ - Section: Provider Deliverability Guides - Last Modified: 2026-03-12 - Description: SNDS reveals how Microsoft scores your sending IPs; JMRP forwards junk-marked emails so you can suppress complainers. Setup steps for both programs. - Keywords: Microsoft JMRP setup, Microsoft SNDS setup, Outlook complaint feedback loop, Microsoft junk email reporting program, SNDS IP reputation check, Outlook deliverability tools > To set up Microsoft's SNDS and JMRP feedback programs, sign in at the [SNDS portal](https://sendersupport.olc.protection.outlook.com/snds), register your sending IPs, and verify ownership to see how Microsoft scores your reputation. Then enroll in [JMRP](https://sendersupport.olc.protection.outlook.com/snds/JMRP.aspx) with the same account and provide a complaint feedback address to receive forwarded junk-marked emails. Both are free. SNDS (Smart Network Data Services) shows how Microsoft scores your sending IPs — reporting reputation levels, spam complaint rates, and traffic volume per IP. JMRP (Junk Email Reporting Program) forwards copies of emails that Outlook.com users mark as junk, so you can identify and suppress complainers. Both programs are free and cover all Microsoft consumer mailboxes (Outlook.com, Hotmail, Live, and MSN). How Providers Report Complaints Gmail, Yahoo, and Microsoft each handle spam complaints differently. This diagram compares all three feedback mechanisms side by side. Cross-provider comparison of spam complaint feedback loops — Gmail (aggregate), Yahoo (individual), Microsoft (both). 1. Recipient clicks Report Spam. 2. Provider records complaint internally. 3. Reputation impact calculated against total inbox-delivered volume. 4. Signal routed to sender via feedback loop if configured. Gmail provides aggregate spam rate and reputation dashboards through Postmaster Tools. Yahoo forwards individual complaint messages in ARF format via its CFL program. Microsoft offers both individual complaints via JMRP and IP-level dashboards via SNDS, managed through one portal. What is SNDS? Smart Network Data Services (SNDS) offers insights into how Microsoft perceives your outbound email traffic. It provides metrics that help you troubleshoot and optimize your sending practices, including: IP address reputation scores Spam complaint rates Traffic volume by IP Junk mail filtering indicators Access to this data allows you to proactively monitor sender reputation and avoid being filtered or blocked. For ongoing monitoring, consider using InboxAlly's Domain Reports. What is JMRP? The Junk Email Reporting Program (JMRP) is Microsoft’s complaint feedback loop system. When a user marks your email as junk, JMRP forwards a copy of that message to a designated reporting address. JMRP helps you: Identify messages that trigger spam complaints Remove complainers from your lists Improve audience targeting and content strategy Reducing complaint rates is key to maintaining long-term deliverability. Use InboxAlly's Email Content Tester to optimize your email content for better inbox delivery. How to Set Up SNDS Access the SNDS Portal Visit the SNDS Portal. Sign in with a Microsoft Account Use any Microsoft account (e.g., Outlook.com or Hotmail) to access the dashboard. Register Your Sending IPs Add your IP addresses or CIDR blocks. Microsoft uses WHOIS or DNS records to verify that you control them. Validate Ownership Microsoft will send verification messages to standard administrative contacts such as abuse@yourdomain.com or postmaster@yourdomain.com. Confirm these to gain access. Review Data Once confirmed, SNDS will show daily summaries of email volume, complaint metrics, and filtering status for each registered IP. How to Set Up JMRP Access the JMRP Registration Page Visit the JMRP Registration Page. Log in with Your Microsoft Account Use the same account as for SNDS to manage both from a single profile. Submit IP Addresses Enter the IPs from which you send email. Provide a Complaint Feedback Address Use a monitored inbox such as abuse@yourdomain.com where complaint messages can be reviewed and triaged. Verify Email Ownership Microsoft sends a confirmation to the specified address. Once verified, you’ll begin receiving forwarded spam complaint messages. Best Practices After Enrollment Monitor SNDS data regularly to catch early signs of deliverability issues. Set up automated workflows to process and react to JMRP complaint emails. Ensure your complaint feedback address is actively monitored by your compliance or deliverability team. Use SPF, DKIM, and DMARC authentication — Microsoft considers these signals when evaluating sender trustworthiness. Investigate any spikes in complaint rates or junk mail classification quickly to avoid deliverability degradation. Troubleshooting Tips Didn’t receive confirmation emails? Check that your abuse@ or postmaster@ addresses are live and have valid MX records. Not seeing any data? Your traffic volume to Microsoft domains may be too low, or your mail stream is currently clean and unflagged. Blocked IPs? Use the Microsoft Sender Support Form to request a delisting and provide remediation details. For additional support, you can check your blacklist status using InboxAlly's Spam Database Lookup tool. Start a free trial of InboxAlly to improve your inbox placement and manage your email deliverability effectively. --- ## How does SpamAssassin scoring work? - URL: https://www.inboxally.com/docs/provider-deliverability-guides/how-spamassassin-scoring-works/ - Section: Provider Deliverability Guides - Last Modified: 2026-03-11 - Description: SpamAssassin runs hundreds of rule-based tests per email. Understand the scoring threshold, common triggers, and how to reduce your spam score. - Keywords: SpamAssassin scoring, how SpamAssassin works, SpamAssassin spam score threshold, reduce SpamAssassin score, SpamAssassin rules and tests, email spam score check > SpamAssassin runs hundreds of rule-based tests against each email and assigns a numeric score — negative points for legitimacy signals, positive points for spam-like characteristics. Messages scoring **5.0 or higher** (the default threshold) are typically flagged as spam. It's widely used in business and self-hosted mail environments alongside proprietary filters from Gmail and Microsoft. SpamAssassin is an open-source spam filtering engine used by many hosting providers, corporate mail servers, and security gateways. It analyzes incoming email and assigns a numeric score indicating how likely a message is to be spam. While major mailbox providers like Google and Microsoft use proprietary filtering systems, SpamAssassin is still widely deployed in business and self-hosted environments. Understanding how it scores messages helps identify content and configuration issues before sending. How the Scoring System Works SpamAssassin runs hundreds of rule-based tests against an email. Each triggered rule adds or subtracts points. The total score is the sum of all triggered rules. Negative score → legitimacy signals detected 0 → neutral Positive score → spam-like characteristics 5.0+ → commonly marked as spam (default threshold) Mail server administrators can change the threshold. Some use 3.0 or lower. For safety, aim for a score below 3–4, with 0–2 being ideal. What SpamAssassin Evaluates SpamAssassin analyzes five primary areas: 1. Headers Authentication results (SPF, DKIM), sending patterns, routing integrity. 2. Body Content Spam phrases, excessive capitalization, poor HTML structure. 3. Raw Message Structure Encoding issues, malformed MIME parts, obfuscation tricks. 4. Links (URIs) Blocklisted domains, URL shorteners, mismatched anchor text. 5. External Reputation DNS blocklists and other reputation databases. SpamAssassin can also use Bayesian filtering, which evaluates word patterns statistically based on previously classified spam and legitimate mail. Understanding Negative Scores Some tests subtract points when legitimacy signals are present. Examples include valid DKIM signatures and trusted authentication results. Large negative scores usually indicate that the recipient server has explicitly allowlisted the sender. This is configured by the receiving administrator and cannot be controlled by the sender. Important Context SpamAssassin primarily evaluates message-level signals: structure, content, and authentication. Modern consumer mailbox providers evaluate far more: Sender reputation Engagement behavior Sending consistency Historical complaint patterns Passing SpamAssassin does not guarantee inbox placement, but failing it can cause delivery problems — especially in corporate environments. Best Practices To maintain a strong SpamAssassin profile: Ensure SPF, DKIM, and DMARC are correctly configured Use clean, well-structured HTML Avoid URL shorteners Monitor domain and IP reputation Avoid spam-trigger language Maintain list hygiene SpamAssassin is a diagnostic layer, not a full deliverability system. It helps identify technical and content risks before campaigns are sent. --- ## What is my IA Score and what does it mean? - URL: https://www.inboxally.com/docs/reports-metrics/understanding-your-ia-score/ - Section: Reports & Metrics - Last Modified: 2026-03-11 - Description: IA Score is a 0–100% prediction of your inbox placement rate, weighted toward recent sends. See what each range means and how to improve. - Keywords: IA Score meaning, inbox placement rate prediction, InboxAlly score explained, email deliverability score, how to improve inbox placement > IA Score is a percentage (0–100%) that predicts your expected inbox placement rate, weighting recent performance more heavily than older data. **95–100%** is excellent, **85–94%** is good, **70–84%** means some issues worth investigating, and **below 70%** signals significant deliverability problems that need attention. Your IA Score is a predictive metric that estimates your expected inbox placement rate. It uses a model that weighs your historical performance along with recent results. What is IA Score? IA Score is a percentage from 0-100% that represents your expected inbox placement rate. Unlike a simple average, it accounts for how much data we have and weights recent performance more heavily. In simple terms: A higher IA Score means your emails are more likely to reach the inbox. The Score Ranges Score Rating What It Means 🟢 95-100% Excellent Your emails are landing in the inbox consistently 🟢 85-94% Good Strong performance with minor room for improvement 🟡 70-84% Fair Some deliverability issues—worth investigating 🔴 Below 70% Needs Attention Significant issues affecting inbox placement Where Do I Find My IA Score? Your IA Score appears on the Sender Profile page: Log in to your InboxAlly account Go to Sender Profile View your IA Score along with other performance metrics IA Score vs. Inbox Placement — What's the Difference? Metric What It Shows Inbox Placement What happened today (raw percentage) IA Score What to expect going forward (predicted rate) Why does this matter? Bad day, good score: If your placement drops to 60% one day but your IA Score is still 88%, don't panic—it's probably a one-time issue. Good day, low score: If placement is 95% today but your IA Score is only 65%, you're still recovering from past issues. Your IA Score gives you the bigger picture, not just a snapshot. What Affects My IA Score? Things That Improve Your Score ✅ Consistent inbox placement across email providers ✅ Sending regularly so we have fresh data ✅ Good authentication (SPF, DKIM, DMARC) ✅ Clean email lists with engaged subscribers Things That Hurt Your Score ❌ Emails landing in spam at any major provider ❌ Inconsistent placement (good one day, bad the next) ❌ Long periods of inactivity (old data becomes less relevant over time) ❌ Sudden spikes in volume without proper warm-up Understanding the Trend Indicator Along with your score, you'll see a trend: Trend What It Means ↑ Improving Your recent performance is better than your history → Stable Your performance is consistent ↓ Declining Your recent performance is worse than before Frequently Asked Questions Why is my IA Score different from today's placement? Your IA Score reflects your overall track record, not just today's results. One bad day won't destroy your score, and one good day won't instantly fix a damaged reputation. It takes consistent performance over time. How long does it take to improve my score? It depends on how much you're sending and how consistently you perform. Generally, with steady good performance, you'll see meaningful improvement within a few weeks. The more you send (to engaged recipients), the faster your score can update. My placement improved but my score dropped—why? Your IA Score looks at multiple factors beyond just inbox vs. spam. It considers: Performance across different email providers (Gmail, Yahoo, Outlook, etc.) How much data we have (more sends = more confidence) Your historical patterns A single good day doesn't instantly offset past issues. Per-Provider Scores Your IA Score is calculated separately for each major email provider The Overall Score you see is a weighted combination that accounts for how much data we have from each provider. If you're performing well at Gmail but poorly at Yahoo, your overall score will reflect both—problems won't be hidden. Tips to Improve Your IA Score Send consistently — Regular sending gives us fresh data to update your score Monitor all providers — A problem at one provider can drag down your overall score Warm up properly — If you're new or returning from inactivity, increase volume gradually Keep lists clean — Remove bounces and unengaged subscribers Fix authentication issues — Ensure SPF, DKIM, and DMARC are properly configured Need Help? If your IA Score is below 70% and you're not sure why: Check your per-provider breakdown to identify which providers are struggling Review your recent sending patterns for any changes Contact support for a detailed deliverability review IA Score is updated daily based on your seed placement data. It represents your expected inbox rate, not a guarantee of future performance. --- ## What is my IA Reputation and how does it affect deliverability? - URL: https://www.inboxally.com/docs/reports-metrics/understanding-your-ia-reputation-score/ - Section: Reports & Metrics - Last Modified: 2026-03-11 - Description: IA Reputation predicts how Gmail, Yahoo, and Outlook view your domain — rated HIGH to BAD. A higher score means better inbox placement. - Keywords: IA Reputation score, email sender reputation, domain reputation email, InboxAlly reputation rating, how mailbox providers rate senders, improve email reputation > IA Reputation (IAR) is InboxAlly's proprietary score that predicts how email providers like Gmail, Yahoo, and Outlook view your sending domain — like a credit score for email. It ranges from **HIGH** (providers trust you) to **BAD** (emails likely going to spam). A higher IAR means better inbox placement and more emails reaching subscribers. Your IA Reputation tells you how email providers (like Gmail, Yahoo, and Outlook) view your sending domain. A higher reputation means better inbox placement and more of your emails reaching your subscribers. What is IA Reputation? IA Reputation (IAR) is InboxAlly's proprietary algorithm that predicts your domain's email reputation. Think of it as a "credit score" for your email sending—it tells you how trustworthy email providers think you are. The Four Reputation Levels IAR What It Means 🟢 HIGH Excellent! Email providers trust your domain 🟡 MEDIUM Good, but there's room for improvement 🟠 LOW Warning: you may be experiencing deliverability issues 🔴 BAD Critical: your emails are likely going to spam Where Do I Find My IAR? Your IA Reputation appears on the Domain Reports page: Log in to your InboxAlly account Go to Domain Reports Select the domain you want to check View your IA Reputation score along with other domain metrics What Affects My IAR? Positive engagement signals strengthen sender reputation while complaints and bounces weaken it. 1. Positive signals evaluated: opens, reads, replies, forwards, spam folder rescues, consistent sending patterns, and clean list hygiene with low bounce rates. 2. Negative signals evaluated: spam reports, hard bounces, spam trap hits, blocklist appearances, and consistently low engagement rates. 3. Positive and negative signals weighed against each other to produce cumulative sender reputation score. 4. Reputation score influences inbox, promotions, or spam placement. 5. After delivery, opens, replies, and rescues strengthen reputation while spam complaints weaken it — continuous feedback cycle. Your IA Reputation is based on several factors: ✅ Things That Help Your IAR Consistent sending patterns — Sending similar volumes regularly Good authentication — Proper SPF, DKIM, and DMARC setup High engagement — Subscribers opening and clicking your emails Clean lists — Removing bounces and inactive subscribers Gradual warm-up — Slowly increasing volume on new domains ❌ Things That Hurt Your IAR Sudden volume spikes — Sending 10x your normal volume overnight High spam complaints — Subscribers marking you as spam Authentication failures — Missing or broken SPF/DKIM Blacklist appearances — Your IPs listed on spam blacklists Poor engagement — Low open rates, high bounce rates How to Improve Your IAR If Your IAR is LOW or BAD Check your authentication — Make sure SPF, DKIM, and DMARC are properly configured Review your sending patterns — Look for sudden changes in volume or frequency Clean your email list — Remove hard bounces, spam traps, and inactive subscribers Reduce volume temporarily — Send to your most engaged subscribers first Use InboxAlly's warm-up tools — Gradually rebuild trust with email providers If Your IAR is MEDIUM Focus on engagement — Send to subscribers who actually want your emails Improve your content — Write subject lines that encourage opens (not spam triggers) Segment your list — Send more relevant content to different groups Monitor regularly — Catch problems before they become serious If Your IAR is HIGH Great job! Keep doing what you're doing: Maintain consistent sending patterns Keep authentication healthy Monitor for any changes Frequently Asked Questions How often is my IAR updated? Your IAR is updated daily. Check back regularly to spot trends. Why did my IAR drop? Common reasons include: A spike in spam complaints Authentication issues (SPF/DKIM failures) Sending to a purchased or old email list Being listed on a blacklist Sudden increase in sending volume How long does it take to improve my IAR? It depends on how severe the issue is and how consistently you follow best practices. Generally, the lower your IAR, the longer it takes to recover. Email providers need to see sustained good behavior over time before trusting your domain again—there are no quick fixes. Is this the same as Google Postmaster Tools? No. IA Reputation is InboxAlly's own algorithm that uses multiple data sources to give you a more complete picture of your domain's reputation. Does everyone see the same IAR for my domain? Your IA Reputation is unique to InboxAlly and based on data we collect. Email providers (Gmail, Yahoo, etc.) have their own internal metrics that aren't public. Need Help? If your IAR is LOW or BAD and you're not sure why: Contact support — We can review your specific situation Book a deliverability consultation — Our experts can help you recover IA Reputation is updated daily and reflects InboxAlly's best prediction of how email providers view your domain. Individual provider experiences may vary. --- ## How do I read my InboxAlly metrics and fix what's wrong? - URL: https://www.inboxally.com/docs/reports-metrics/analyzing-engagement/ - Section: Reports & Metrics - Last Modified: 2026-03-11 - Description: Pair InboxAlly inboxing rate with ESP engagement data to pinpoint deliverability, content, or list quality issues — and fix them fast. - Keywords: email engagement metrics, InboxAlly inboxing rate, email deliverability analysis, inbox vs spam placement, how to read email metrics, improve email engagement > To read your InboxAlly metrics and diagnose what's wrong, focus on **inboxing rate** — above 80% is good, below 70% needs action. Cross-reference with your ESP data: low opens + high inboxing means a content or targeting problem; low opens + low inboxing means a deliverability problem (check auth and blocklists); good opens + rising complaints means a frequency or expectation mismatch. Look at trends across 5–10 sends, not single broadcasts. InboxAlly shows deliverability data your ESP can’t: where your emails actually land (inbox vs. spam) across mailbox providers. When you pair InboxAlly placement metrics with your ESP’s engagement metrics, you can quickly tell whether a performance issue is deliverability (messages aren’t reaching the inbox) or content/targeting (messages reach the inbox but aren’t resonating). The metric that matters most: inboxing rate InboxAlly’s inboxing rate is the percentage of your emails that landed in the inbox (vs. spam) across InboxAlly seed inboxes. This is the fastest way to answer: “Are providers accepting and placing my mail correctly?” Important clarification (Broadcasts): In the Broadcasts view, inboxing rate is calculated from detected seed emails. It measures inbox vs. spam placement for the emails InboxAlly detected—it does not reliably report “missing” or undelivered emails, because InboxAlly can’t always know whether your send included every seed address. What good looks like Consistently high inboxing (80%+) across major providers Small day-to-day dips are normal The key is consistency and provider balance (no single provider lagging far behind) What bad looks like Sustained inboxing below ~70% One provider consistently underperforming (for example, Gmail low while Outlook is fine) A sharp drop that persists across multiple sends (often indicates a reputation or policy issue) Where to find it (Broadcasts) InboxAlly groups similar sends into Broadcasts based on Sender Profile, subject, from-address, and date. Each broadcast shows its inboxing rate so you can compare placement across sends. To view your detected broadcasts: Open the Broadcasts tab in your InboxAlly dashboard. Review the list of detected broadcasts and their inboxing rate and detected mail counts. How to read ESP metrics alongside InboxAlly Use InboxAlly to confirm placement, then use your ESP to interpret engagement. These combinations are the quickest way to diagnose what’s actually wrong. Low open rate + HIGH inboxing rate Your emails are reaching the inbox, but people aren’t opening. What it usually means Subject line isn’t compelling (or doesn’t match audience intent) Targeting/segmentation is off Send time/frequency isn’t aligned with the audience What to do next A/B test subject lines and preview text Tighten segmentation (recent engagers vs. cold segments) Adjust send timing and cadence before changing deliverability settings Low open rate + LOW inboxing rate Your emails are going to spam. Low opens are a symptom, not the cause. What to do next (deliverability-first) Check authentication and domain health in Domain Reports (SPF/DKIM/DMARC status) Check for blocklisting with the free Spam Database Lookup Follow the Email Reputation Repair guide If you recently increased volume, tighten targeting and consider adjusting your seed ratio strategy (more seeds and/or lower daily volume) until placement stabilizes If you suspect emails aren’t being delivered at all (not just landing in spam): run the Placement Tester. It sends to a controlled set of test inboxes and can detect missing/undelivered emails across providers, giving you a complete picture of delivery and placement. Good open rate + rising complaints/unsubscribes People are receiving and opening, but they don’t like what they’re getting (or how often). What it usually means Frequency is too high for that segment Content doesn’t match expectations set at signup You’re mailing too many low-intent contacts What to do next Reduce frequency for colder segments Improve targeting (send fewer, more relevant emails) Make preference management and unsubscribe frictionless (this reduces spam complaints) High bounce rate This is almost always a list quality problem, and it can quickly damage sender reputation. What to do next Run list hygiene before your next campaign using free Email List Verification Remove hard bounces immediately Be cautious with old, purchased, or unverified lists (they tend to create bounces and complaints) Inboxing varies by provider If one provider’s inboxing rate is consistently lower than others, you likely have a provider-specific reputation issue. What to do next Check Domain Reports for authentication or alignment issues that may affect certain providers more than others For Gmail-specific placement problems, use the Gmail Deliverability Deep Dive to troubleshoot common causes (reputation, content signals, and sending patterns) Using Broadcasts to spot trends Broadcasts are most useful when you treat them like a trend report—not a single pass/fail score. Don’t judge deliverability from one send. Look across 5–10 broadcasts. Compare inboxing rates across: Different subject lines Different segments (engaged vs. cold) Different content types (plain text vs. heavy HTML, promotional vs. informational) A sudden inboxing drop right after a specific send often points to: A risky segment (older/unverified contacts) A content shift (more links, different formatting, more “salesy” language) A volume change (sending more than usual) Stable inboxing that gradually declines often indicates reputation erosion: Tighten targeting Improve list hygiene Reduce sends to low-engagement segments until placement recovers When to dig deeper Use this quick decision guide to choose the next step: Inboxing dropped suddenly → run Placement Tester to confirm placement across providers, then use Email Audit to identify the likely cause Authentication concerns → check Domain Reports for SPF/DKIM/DMARC status Suspect blocklisting → run the free Spam Database Lookup Not sure what’s wrong → open the IA Assistant in the InboxAlly app for situation-specific recommendations Already using InboxAlly? Check your Broadcasts tab now and compare your last 5–10 sends. Not yet? Start a free InboxAlly trial: https://app.inboxally.com/register --- ## How do I connect Google Postmaster Tools to InboxAlly? - URL: https://www.inboxally.com/docs/reports-metrics/integrate-google-postmaster-tools-with-inboxally/ - Section: Reports & Metrics - Last Modified: 2026-03-11 - Description: See Gmail domain reputation, spam rates, and authentication status directly in your InboxAlly dashboard with real-time alerts. - Keywords: Google Postmaster Tools integration, Gmail domain reputation monitoring, email spam rate tracking, InboxAlly Google Postmaster setup, Gmail deliverability dashboard, email authentication status > To connect Google Postmaster Tools to InboxAlly, verify your domain in GPT, then share viewer access with the InboxAlly monitoring email address found in **My Account**. GPT data — spam rate, compliance status, authentication, and delivery errors — will appear in your InboxAlly Domain Reports within 24 hours. The Google Postmaster Tools integration connects your GPT account to InboxAlly, pulling Gmail-specific metrics — domain reputation, spam rates, and authentication status — directly into your InboxAlly dashboard. Once connected, InboxAlly monitors this data continuously and sends real-time alerts when Gmail reputation shifts, along with actionable recommendations to resolve issues before they affect inbox placement. Key Benefits of the Integration 1. Unified Dashboard for Comprehensive Insights Track Gmail-specific metrics such as domain reputation, spam rates, and authentication status all directly within InboxAlly. This eliminates the need to switch between tools and allows for faster, more informed decisions. 2. Real-Time Alerts and Recommendations InboxAlly monitors changes in your GPT data and notifies you of emerging issues. You’ll receive actionable guidance to help resolve problems before they impact your inbox placement. 3. Smarter Issue Response with Contextual Data Use GPT trends to understand exactly when and why deliverability shifts occur. InboxAlly surfaces these insights in context, enabling you to act quickly and effectively without guessing. 4. Data-Driven Optimization Leverage Google’s reputation signals to validate your sending practices, troubleshoot dips in performance, and improve long-term inbox placement. How to Set Up the Integration Configuring Google Postmaster Tools will provide visibility into your domain and IP reputation with Gmail. Here’s how to set it up: Follow Google's Setup Guide Visit the official Google support article and follow the instructions to verify your domain: https://support.google.com/a/answer/9981691?hl=en Verify Your Domain in Google Postmaster Tools Use DNS verification to prove ownership of the domain(s) you want to monitor. Share Access with InboxAlly’s Monitoring Account Once GPT is configured, grant InboxAlly read access so it can pull your metrics: In InboxAlly, go to My Account. Your assigned GPT monitoring email address is displayed in the Google Postmaster Tools section. Copy that monitoring email address. In Google Postmaster Tools, open your verified domain, click the three-dot menu, and select Manage users. Add the InboxAlly monitoring email as a viewer. View Reports in InboxAlly Within 24 hours of granting access, GPT data will appear in your Domain Reports section in InboxAlly. Google Postmaster Tools Decoded Once connected, the GPT metrics that appear in your InboxAlly dashboard come from eight underlying dashboards — each showing a different dimension of how Gmail evaluates your email. This reference covers what each dashboard measures, which version it appears in, what healthy metrics look like, and what to do when something is off. All eight Google Postmaster Tools dashboards with version badges, thresholds, and action guidance. 1. Compliance Status (v2 only): binary pass/fail checklist for SPF/DKIM, DNS, formatting, encryption, spam rate, DMARC, one-click unsubscribe. 2. Spam Rate (v1+v2): percentage of inbox-delivered messages marked spam — target below 0.1%, maximum below 0.3%. 3. Feedback Loop (v1+v2): campaign-level spam reports by Feedback-ID header. 4. Domain Reputation (v1 only): quality rating High/Medium/Low/Bad, follows you across ESPs. 5. IP Reputation (v1 only): quality rating for sending IPs, resets when switching ESPs. 6. Authentication (v1+v2): SPF, DKIM, DMARC pass rates — target 100%. 7. Encryption (v1+v2): TLS percentage — target 100%. 8. Delivery Errors (v1+v2): rejection and temporary failure rates with error codes. Frequently Asked Questions (FAQs) Q: Do I need technical expertise to set this up? A: Not necessarily. Google’s instructions are straightforward, and InboxAlly provides a guided process for sharing access. Our support team is also available to help. Q: When will GPT data appear in InboxAlly? A: You’ll typically start seeing data in the Domain Reports section within 24 hours of sharing access with the designated monitoring account. Q: Can I connect multiple domains? A: Yes. As long as each domain is verified in GPT and access is granted to InboxAlly, you can monitor multiple domains from your unified dashboard. Related Articles Gmail Deliverability: Reach Primary, Avoid Promotions and Spam How to Set Up the Gmail Complaint Feedback Loop How to Set Up SPF, DKIM, and DMARC Understanding Your InboxAlly Reputation Score --- ## How long does it take for InboxAlly dashboard data to appear? - URL: https://www.inboxally.com/docs/reports-metrics/how-long-does-it-take-for-dashboard-data-to-appear/ - Section: Reports & Metrics - Last Modified: 2026-03-10 - Description: Most InboxAlly dashboard data appears within 2–6 hours, with full engagement completing in 72 hours. Here's what to expect after each send. - Keywords: InboxAlly dashboard data timing, how long for email results to show, seed list engagement delay, InboxAlly reporting timeline, email deliverability data > Most dashboard data appears within **2–6 hours** after sending to InboxAlly's seed list, and full engagement activity typically completes within **72 hours**. InboxAlly engages with up to ~80% of seed emails per send — this is by design to maintain natural-looking engagement patterns, not a tracking issue. InboxAlly starts detecting your emails shortly after you send a campaign to our seed list. Most dashboard data appears within 2–6 hours, and full engagement activity typically completes within 72 hours. What to expect in the first 72 hours First 2–6 hours: Most emails sent to seed addresses are detected and show up in the Dashboard. You’ll see early inboxing and initial delivery stats. 6–12 hours: More detections and early engagement data may appear due to inbox refresh cycles and possible ESP sending delays. 12–72 hours: Remaining engagement activity completes. This longer window reflects normal user behavior and helps avoid engagement patterns that could look artificial to mailbox providers. Why your report may not match your full send volume (the 80% model) InboxAlly typically engages with up to ~80% of the emails sent to our seed addresses. This is expected behavior, not a tracking issue. This happens because our system is designed to: Balance load across all users (so engagement actions run reliably at scale) Use cooling periods (to avoid unnatural engagement spikes) Maintain deliverability-safe patterns that look like real recipient behavior So if you sent 1,000 emails to seeds, it’s normal to see engagement on roughly 800 of them. If you’re seeing much less than expected If detected emails or engagement are significantly below ~80%, it may indicate a delivery or placement issue (not just timing). To confirm where your emails are landing, run an inbox placement test using Placement Tester (in the InboxAlly app). This helps you determine whether messages are reaching the inbox, going to spam, or being dropped. Still have questions? Contact InboxAlly support via live chat for help interpreting your campaign timeline and results. --- ## Why are my emails going to spam? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/why-are-my-emails-going-to-spam/ - Section: Troubleshooting & Recovery - Last Modified: 2026-03-11 - Description: Spam filters predict risk, not intent. Diagnose the root cause across four pillars: reputation, authentication, content, and engagement. - Keywords: why are my emails going to spam, emails landing in spam folder, how to stop emails going to junk, spam filter triggers, email spam placement, inbox deliverability problems > If your emails are going to spam, check four things in this order: (1) **authentication** — verify SPF, DKIM, and DMARC are passing, (2) **blocklists** — check your IP and domain against Spamhaus, Barracuda, and others, (3) **engagement and list hygiene** — remove unengaged subscribers and verify your list, (4) **content** — fix risky links, heavy HTML, or spam-trigger phrases. Common causes include new domains, sudden volume spikes, and missing authentication. Legitimate emails land in spam because spam filters predict risk, not intent. A brand-new domain, a sudden volume spike, a missing authentication record, or a history of low engagement can look statistically similar to abusive sending — so the safest placement is often the junk folder. The good news: most spam placement problems have identifiable root causes, and InboxAlly gives you tools to find and fix them fast. Start here: use the IA Assistant for guided diagnosis The fastest way to diagnose why your emails are going to spam is to use the IA Assistant inside the InboxAlly app. It's powered by AI and built on the expertise of InboxAlly's in-house deliverability team. What the IA Assistant can do: Analyze your specific sending situation and identify the most likely cause Walk you through the right checks in the right order (so you're not guessing) Recommend the exact next steps based on what it finds — authentication fixes, list hygiene actions, content changes, or engagement recovery Reference your account data (reputation score, placement results, DMARC reports) to give targeted advice How to use it: Open the InboxAlly app and look for the IA Assistant. Describe your problem (e.g., "my emails are going to spam at Gmail" or "I switched ESPs and now I'm landing in junk") and it will guide you from there. The rest of this article explains the underlying framework — useful if you want to understand why things work the way they do, or if you prefer to investigate manually. Understanding spam placement: the 4 pillars How mailbox providers evaluate incoming emails using five parallel filtering signals. 1. Five signal categories evaluated simultaneously: authentication alignment, content analysis, link reputation, sender reputation, and infrastructure signals (IP reputation, volume patterns, bounce rate). 2. All signal categories combine into a composite spam score. 3. Based on spam score, message routed to inbox, promotions, or spam. 4. After delivery, opens, clicks, and spam complaints generate engagement signals. 5. Engagement signals feed back into spam score for future messages, creating a continuous feedback cycle. Mailbox providers don't use one "spam test." They combine multiple signals into a placement decision. Think of it as four pillars — if any one is weak enough, it can outweigh the others. Pillar 1: Sender reputation (domain/IP) Your track record as a sender, based on how recipients and providers have responded to your mail over time. Key inputs: Complaint rate — "This is spam" clicks are one of the fastest ways to lose inbox placement Bounce rate — high hard bounces signal poor list hygiene Spam traps — hitting recycled/pristine traps suggests scraping or stale lists Sending consistency — sudden volume spikes or long gaps followed by blasts look risky Shared vs dedicated IP — on shared IPs, another sender's behavior can affect you; domain reputation matters either way Pillar 2: Authentication (SPF, DKIM, DMARC) Proof that you're authorized to send and that the message wasn't altered — plus alignment between the visible "From" domain and authenticated domains. Common failure points: SPF passes but uses a different domain than your "From" address → DMARC fails due to misalignment DKIM breaks when an intermediary modifies the message body Multiple SPF records or exceeding the 10-lookup limit For current enforcement expectations, see Gmail and Yahoo changes for bulk senders in 2024. Pillar 3: Content signals (format, links, HTML) What the message looks like to filters — structure, wording patterns, link behavior, and technical composition. Common triggers: Image-only emails, heavy HTML, or mismatched "From" name vs domain Multiple shortened/tracking links (can resemble phishing) Attachments or unusual file types Test your content with the free Email Spam Checker or Email Content Tester. Pillar 4: Engagement history (opens, clicks, replies, complaints) How recipients historically interact with your emails — especially positive actions. What matters: Low opens + low clicks + no replies over weeks teaches providers your mail isn't wanted A small segment that consistently opens/replies can help stabilize placement Deletes-without-reading and "Report spam" are strong negative signals These pillars interact. Perfect content can still go to spam if engagement is weak; strong engagement can't fully overcome broken authentication; and a reputation dip can make content filters harsher. That's why fixing only one pillar often isn't enough. Common patterns: what your symptoms tell you Use these patterns to quickly narrow the most likely cause — or share them with the IA Assistant for faster, targeted guidance. Symptom Most likely cause What to check first Sudden spam placement after a change (new ESP, new domain, new template) Volume spike, reputation reset, or authentication break Compare send volume week-over-week; re-verify SPF/DKIM/DMARC Only Gmail puts you in spam (others OK) Low engagement signals, high "ignore" behavior Review engagement trends; segment by engaged vs cold recipients Only Microsoft (Outlook/Hotmail) puts you in junk IP/domain reputation, SmartScreen filtering, blocklist exposure Check blocklist status and sending IP reputation Only new subscribers land in spam Acquisition/list quality issues, mismatched expectations Audit signup sources, double opt-in, first-email timing All providers spam you Authentication failure or severe reputation issue Check SPF/DKIM/DMARC first, then blocklists Triage order (avoid wasted effort) Authentication first — if SPF/DKIM/DMARC fail, nothing else matters Blocklists next — resolve reputation flags before tweaking copy Engagement + list hygiene — segment, suppress unengaged, fix expectations Content last — optimize once trust signals are stable Self-diagnosis reference (manual checks) The IA Assistant walks you through these checks automatically. If you prefer to investigate manually, here's a summary of what to look at in order. 1) Authentication (SPF, DKIM, DMARC) The most common root cause — especially after switching ESPs or changing DNS. SPF: One TXT record per domain, includes all sending systems, under the 10-lookup limit DKIM: Signing on the correct domain, selector matches DNS, passes in message headers DMARC: Exists at _dmarc.yourdomain.com, visible From domain aligns with SPF and/or DKIM Use Domain Reports (in the InboxAlly app) to review authentication status and alignment. 2) Blocklist and reputation checks Check your sending domain and IP(s) with the free Spam Database Lookup Focus on widely used, high-signal lists first If listed, remediate the underlying cause — see Blocklist Impact and Remediation 3) Engagement and list health Pull these metrics from your ESP (last 30–60 days): open rate, click rate, reply rate, complaint rate, bounce rate. Red flags: Rising complaints after a list import or volume increase High hard bounce rate (list decay, purchased lists) Large segments with no recent engagement Actions: Segment by recency (engaged in last 30/60/90 days) Pause or re-permission cold segments Verify addresses with the free Email List Verification tool 4) Content and technical checks Test with the free Email Content Tester or Email Spam Checker Watch for: mismatched branded domains, too many links, image-heavy layouts, URL shorteners, inconsistent From/Reply-To Use the Placement Tester (in the InboxAlly app) to validate inbox vs spam across providers Fix content issues before increasing volume — otherwise you reinforce negative signals. Provider-specific differences Each mailbox provider weights the four pillars differently. This matters when you see spam placement at one provider but not others. Gmail: engagement-first Gmail heavily prioritizes recipient behavior and consistency. Rewards: opens, clicks, replies, "Not spam," adding to contacts, consistent sending patterns Penalizes: sudden spikes, large sends to cold lists, deletes-without-reading, "Report spam" If Gmail is the problem, prioritize engagement repair and segmentation. InboxAlly seed emails can help rebuild positive signals after you've confirmed authentication and list quality. Microsoft (Outlook/Hotmail): reputation-sensitive Microsoft is strongly influenced by SmartScreen and external reputation signals (including Spamhaus-related indicators). Common triggers: new/weak IP reputation, high complaints, URL/domain reputation issues, volume spikes Common throttling: sudden increases to Outlook recipients, high bounces, rapid retries after deferrals If Outlook is the problem, check reputation and blocklist exposure, then stabilize volume. Yahoo/AOL: strict on authentication and complaints Yahoo blends reputation with engagement but is less forgiving about authentication alignment and complaint spikes. Watch: SPF/DKIM/DMARC alignment, consistent "From" identity, complaint rate (even small increases matter) If placement differs across providers, it's usually a weighting difference — not purely a content problem. Fix framework: quick wins vs long-term repairs Quick wins (hours–days) Fix SPF/DKIM/DMARC alignment — use the Email Audit (in the InboxAlly app) to find misconfigurations Pause risky sends — stop large campaigns or cold outreach while diagnosing Remove problematic links — strip redirects, shorteners, or links to low-reputation domains Reduce volume — step down from spikes and ramp back gradually Verify lists — remove purchased, scraped, or old addresses; prioritize recent engagers Test before sending — use the Placement Tester and free Email Content Tester to validate Long-term fixes (weeks) Rebuild reputation — send on a predictable schedule, keep complaints and bounces low Improve segmentation — send fewer emails to more relevant groups Sunset unengaged contacts — stop mailing recipients who haven't engaged in 60–180 days Add preference management — frequency options, topic preferences, easy unsubscribes Reduce complaints at the source — align signup expectations with what you actually send When InboxAlly seed emails help most If authentication is correct, content tests clean, and blocklists are clear — but you still land in spam (especially at Gmail/Yahoo) — the issue is often weak engagement signals. InboxAlly seed emails can rebuild positive engagement patterns that mailbox providers use to reassess sender reputation over time. Track progress with your IA Reputation Score (see Understanding Your IA Reputation Score). Warm-up: when it helps and when it doesn't When warm-up is appropriate New domain or new dedicated IP (no reputation history) Long sending pause (reputation decays) Post-blocklist recovery (after delisting and fixing the cause) Major volume ramp (hundreds to tens of thousands/day) When warm-up won't fix it Fix these before warming: Broken authentication (SPF/DKIM/DMARC missing or misaligned) Active blocklist listings Poor list quality (purchased/old lists, high unknown-user rates) High complaint rates Spammy content patterns Safe warm-up plan Ramp schedule: Start at 20–50 emails/day, increase 20–40% every 2–3 days (only if metrics stay clean) Seed ratio: 30–50% during early ramp → 10–25% mid ramp → 5–10% at stable volume Monitor daily: inbox vs spam placement, complaints, bounces Tools: Plan your ramp with the free Email Warmup Planner. For a typical timeline, see how long it takes to warm up a domain. Track progress with the IA Reputation Score and Dashboard (in the InboxAlly app). Frequently Asked Questions How long does it take to get out of spam? It depends on the root cause. Authentication fixes (SPF, DKIM, DMARC) can take effect within hours once DNS propagates. Reputation recovery typically takes two to six weeks of consistent, clean sending — longer if you're coming off a blocklist or rebuilding from a severe reputation drop. Why do my emails go to spam at Gmail but not Outlook? Gmail weights engagement signals more heavily than other providers — opens, clicks, replies, and "Report spam" clicks all factor into placement decisions. Outlook relies more on IP and domain reputation plus SmartScreen filtering. If only Gmail is filtering you, the issue is usually weak engagement rather than authentication or content. Can I fix spam placement by switching ESPs? Not on its own. Domain reputation follows you regardless of which ESP you use, and a new ESP means re-authenticating SPF, DKIM, and DMARC from scratch. If the underlying cause is list quality, engagement, or content, a new ESP won't change the outcome. Fix the root cause first, then migrate if needed. Do I need to warm up my domain after fixing authentication? If your domain has existing sending history and the authentication fix was the only issue, you may not need a full warm-up — placement can recover within days. If the domain is new, was inactive for an extended period, or had reputation damage beyond authentication, a gradual warm-up is recommended. Will InboxAlly seed emails fix my spam problem? Seed emails fix engagement-related spam placement — they rebuild the positive signals (opens, clicks, inbox moves) that providers use to assess sender reputation. They won't fix broken authentication, active blocklist listings, or poor list quality. Resolve those issues first, then use seed emails to accelerate reputation recovery. If you don't have an InboxAlly account yet, start a free trial to access the IA Assistant, Placement Tester, and seed emails. --- ## How do I get removed from the Spamhaus blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/spamhaus/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: Spamhaus is the most widely used blocklist — a listing can cause 50%+ bounce rates. Check your status, fix the cause, and request removal. - Keywords: Spamhaus blocklist removal, Spamhaus delisting, how to get off Spamhaus, Spamhaus SBL XBL DBL, Spamhaus blacklist, listed on Spamhaus > Spamhaus is the most widely used email blocklist in the world — a listing can cause bounce rates over 50% and severe delivery failures across most major ISPs. Check your IP and domain status, identify and fix the underlying cause (spam traps, compromised infrastructure, poor list hygiene), then submit a removal request through Spamhaus's self-service delisting portal. Spamhaus is a widely used email blocklist and reputation data source. If your IP or domain is listed, many receiving mail servers may reject your mail or route it to spam—so you’ll want to confirm the listing and fix the underlying cause before requesting removal. To quickly check your status, use InboxAlly’s free Spam Database Lookup. What is Spamhaus? Spamhaus is an anti-abuse organization that publishes several blocklists (and related reputation data) used by mailbox providers, ISPs, and corporate mail systems to identify spam, malware, and suspicious sending infrastructure. Spamhaus listings can apply to: IP addresses (the server sending the email) Domains (the website/domain referenced in mail, including links and tracking domains) How does Spamhaus affect email deliverability? A Spamhaus listing can cause: Hard bounces / rejections (mail refused during SMTP) Spam folder placement (mail accepted but filtered) Rate limiting or temporary deferrals (slower delivery and reduced throughput) Impact depends on the receiving system and which Spamhaus list you’re on. Some lists are treated as “block immediately,” while others are more informational. To confirm whether a listing is contributing to delivery issues, check your IP/domain with the free Spam Database Lookup and compare results with your bounce logs (look for “Spamhaus,” “ZEN,” “SBL,” “XBL,” “PBL,” or “DBL” in rejection messages). Why am I listed on Spamhaus? Spamhaus listings typically happen when their systems (and/or downstream data sources) detect patterns associated with abuse or compromised infrastructure. Common causes include: Spam trap hits (sending to addresses that should not be on a permission-based list) High complaint rates or consistent negative engagement signals Compromised accounts or servers sending unwanted mail Open relay / open proxy behavior, or malware activity from your IP Policy issues (for example, sending from an IP range not intended for direct email) Common Spamhaus lists (what they usually mean) SBL (Spamhaus Block List): IPs suspected of sending spam or supporting spam operations. XBL (Exploits Block List): IPs associated with malware, botnets, or exploited systems. PBL (Policy Block List): IP ranges not meant to send email directly (often residential/dynamic IP space). This is not necessarily an accusation of spam—often it’s a routing/policy issue. DBL (Domain Block List): Domains found in spam messages (including linked domains and tracking domains). ZEN: A combined query zone that includes SBL, XBL, PBL (and related datasets) for fast lookups. DROP/EDROP: Netblocks associated with known spam operations (typically a serious infrastructure-level issue). How do I get removed from Spamhaus? Removal is usually straightforward once the root cause is fixed. Use this process: Confirm the exact listing Check whether it’s an IP listing (SBL/XBL/PBL/Zen) or a domain listing (DBL). Use Spamhaus’s public checker at check.spamhaus.org to see the listing details and guidance. Fix the underlying issue (before requesting delisting) If XBL/malware-related: scan and remediate compromised hosts, rotate credentials, patch vulnerable services, and stop unauthorized sending. If SBL/spam-related: pause or reduce sending, tighten list hygiene, remove risky segments, and ensure you’re only mailing opted-in recipients. If PBL/policy-related: send through a proper outbound mail server/ESP or a suitable static/business IP range intended for mail. If DBL/domain-related: remove abusive content/links, verify your tracking domains, and ensure your sending practices are permission-based. Submit the delisting request Follow the instructions provided in the Spamhaus listing record. Some listings expire automatically after issues stop; others require a request. Monitor after removal Re-check your status with the free Spam Database Lookup. In the InboxAlly app, use Domain Reports for ongoing monitoring of domain reputation and authentication status. Frequently asked questions Does Spamhaus block my emails directly? Spamhaus itself doesn’t “block” mail. Receiving mail servers choose to use Spamhaus data to accept, reject, or filter messages. How do I check if I’m listed on Spamhaus ZEN? Run an IP lookup using Spamhaus’s checker (check.spamhaus.org). If ZEN is involved, the results will indicate which underlying list (SBL/XBL/PBL) triggered the ZEN response. Does a Spamhaus PBL listing mean I’m a spammer? Not necessarily. PBL often indicates the IP range is not intended for direct-to-MX sending (common with residential or dynamic IPs). The fix is usually to route mail through appropriate sending infrastructure. Does Google use Spamhaus? Google doesn’t publicly confirm specific blocklists used in Gmail filtering. However, Spamhaus data is widely used across the industry, and a listing can correlate with deliverability problems at many providers. For broader context and step-by-step remediation across blocklists, see Blocklist Impact and Remediation. --- ## What do SMTP response codes mean for email deliverability? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/smtp-response-codes/ - Section: Troubleshooting & Recovery - Last Modified: 2026-03-24 - Description: SMTP response codes tell you exactly why email was accepted, deferred, or rejected. Look up any code — including Gmail, Microsoft, and Yahoo enforcement codes — and see what to fix. - Keywords: SMTP response codes, SMTP error codes, email bounce codes, 550 5.7.26, 550 5.7.1, Gmail SMTP error codes, Yahoo SMTP error codes, what does 550 mean in email, SMTP 421 vs 550 > SMTP response codes are three-digit status codes returned by mail servers during email delivery. **2xx** means success, **3xx** means the server needs more input, **4xx** is a temporary failure (your server retries automatically), and **5xx** is a permanent rejection. Since 2024, Gmail, Microsoft, and Yahoo use additional enforcement codes — like **550 5.7.26** (unauthenticated mail) and **550 5.7.515** (missing SPF/DKIM/DMARC) — to reject messages from senders who don't meet bulk sender requirements. SMTP response codes are the status messages that mail servers return during an email transaction. Every time you send an email, the receiving server replies with a three-digit code that tells your sending server exactly what happened: accepted, try again later, or permanently rejected. Understanding these codes is essential for diagnosing delivery failures and maintaining sender compliance. The first digit tells you the severity — 2xx is success, 4xx is a temporary failure where your server retries, and 5xx is a permanent rejection. Enhanced status codes (like 550 5.7.26) add a second layer of detail: the class, subject category, and specific issue. The reference below covers the codes most relevant to email deliverability, including the provider-specific enforcement codes that Gmail, Microsoft, and Yahoo introduced with the 2024–2025 bulk sender requirements. SMTP codes most relevant to email deliverability and sender compliance. Gmail enforcement codes are shown as paired warning → rejection escalations. For the complete protocol specification, see IETF RFC 5321. 1. Read the three-digit code structure: first digit is severity (2=success, 4=temporary, 5=permanent), second digit is category, third is detail. 2. 2xx success codes confirm the connection and delivery were accepted. 3. 4xx temporary failures mean your server retries automatically — fix the issue before providers escalate to 5xx. 4. 5xx permanent failures mean the message was rejected — fix the compliance issue for future messages. 5. Gmail enforcement codes (4.7.26 through 4.7.32) start as 421 warnings and escalate to 550 rejections if not fixed. 6. Yahoo and Microsoft have their own enforcement codes for authentication and policy violations. 7. Recipient-side codes (like 550 5.1.1 account not found) are the recipient's problem, not yours. How to read SMTP codes Every SMTP response has a three-digit base reply code and, for modern systems, an enhanced status code that gives more detail. Base reply code (e.g., 550): First digit — severity: 2 = success, 3 = intermediate (needs more input), 4 = temporary failure, 5 = permanent failure Second digit — category: 0 = syntax, 1 = information, 2 = connection, 3 = unspecified, 5 = mail system Third digit — specific condition within that category Enhanced status code (e.g., 5.7.26): Follows class.subject.detail format x.7.x = security or policy issue (the most common category for deliverability problems) x.1.x = addressing issue x.2.x = mailbox issue When you see 550 5.7.26 in your bounce logs, the 550 is the base reply (permanent failure) and 5.7.26 is the enhanced code (permanent + security/policy + specific detail 26, which Gmail uses for unauthenticated mail). Gmail enforcement codes (2024–2025) Gmail's bulk sender enforcement introduced paired codes — the same compliance issue appears first as a 421 temporary warning and escalates to a 550 permanent rejection if you don't fix it. Since November 2025, Gmail actively converts warnings to rejections for persistent non-compliance. Warning Rejection Issue Fix 421 4.7.26 550 5.7.26 Unauthenticated — SPF or DKIM missing Configure SPF and DKIM 421 4.7.27 550 5.7.27 SPF did not pass Fix SPF record, verify sending IPs 421 4.7.28 550 5.7.28 Unusual sending rate or high spam rate Reduce volume, lower spam complaint rate 421 4.7.29 550 5.7.29 No TLS encryption Enable TLS on your sending server 421 4.7.30 550 5.7.30 DKIM did not pass Fix DKIM signing and DNS key 421 4.7.32 550 5.7.26* No DMARC alignment Align your From: domain with SPF or DKIM 421 4.7.23 550 5.7.25 No PTR record / reverse DNS mismatch Add a valid PTR record for your sending IP * No documented 550 5.7.32 — alignment failures escalate to 550 5.7.26 (unauthenticated) or 550 5.7.1 (general block). Two Gmail codes go straight to permanent rejection with no warning period: 550 5.7.1 — Blocked for spam, low reputation, DMARC policy failure, or invalid From: header. This is Gmail's catch-all rejection. 550 5.7.23 — DMARC policy failure with p=quarantine or p=reject applied. Your DMARC record told Gmail to reject unauthenticated mail, and it did. Microsoft Outlook enforcement (May 2025) Microsoft introduced a single enforcement code: 550 5.7.515 — Required authentication level not met. Outlook now requires SPF + DKIM + DMARC (p=none minimum) for bulk senders. Configure all three to resolve. Yahoo / AOL enforcement (February 2024) Yahoo's enforcement codes use internal reference tags in brackets: Code Issue Fix 421 4.7.0 [TSS04] Temporarily deferred — unusual volume or user complaints Slow down sending, review complaint sources 553 5.7.1 [BL21/BL23] IP blocked — listed on Spamhaus (SBL or XBL) Request delisting at spamhaus.org 553 5.7.2 [TSS11] All messages permanently deferred — retrying will NOT succeed Fix authentication and reputation, then wait for re-evaluation 554 5.7.9 Policy rejection — unauthenticated or content violation Configure SPF + DKIM + DMARC Common recipient-side codes These codes mean the problem is on the recipient's side — you can't fix them, but you need to handle them correctly in your bounce management process: Code Meaning Action 450 4.2.1 Recipient receiving too fast — rate limited Retry later 452 4.2.2 Recipient over quota (temporary) Retry later 550 5.1.1 Account does not exist Suppress immediately — hard bounce 550 5.2.1 Account disabled or suspended Suppress — account is inactive 552 5.2.2 Recipient over quota (permanent) Suppress after repeated failures 552 5.2.3 Message too large Reduce message size (Gmail limit: 25MB) 552 5.7.0 Illegal attachment detected Remove blocked attachment type 4xx vs 5xx: what to do 4xx (temporary failure): Your sending server retries automatically. These are warnings — the server will keep trying for a period (typically 24–72 hours). But if you're seeing Gmail 4xx enforcement codes (like 421 4.7.26), treat them as urgent: fix the underlying authentication or compliance issue before Gmail escalates to a permanent 550 rejection. 5xx (permanent failure): The message is permanently rejected and your server stops trying. For standard codes like 550 5.1.1 (account doesn't exist), suppress the address. For enforcement codes like 550 5.7.26, fix the compliance issue so future messages from your domain are accepted. For detailed bounce handling rules — when to suppress, when to retry, and how to keep your bounce rate under 2% — see What is the difference between soft and hard email bounces? Related resources Email Authentication & DNS — Set up the SPF, DKIM, and DMARC authentication that Gmail, Microsoft, and Yahoo now require Email bounce management — Suppression rules, retry logic, and bounce rate targets Blocklist impact and remediation — What to do when you're blocked Email Ramp Up Schedule — Controlled volume increases to build reputation --- ## How do I repair my email sender reputation? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/how-to-repair-email-sender-reputation-after-deliverability-issues/ - Section: Troubleshooting & Recovery - Last Modified: 2026-03-10 - Description: A 3-phase playbook to stop the bleeding, rebuild trust with engaged recipients, and safely ramp volume back up over 2-12 weeks. - Keywords: repair email sender reputation, domain reputation recovery, fix sender reputation, email deliverability issues, IP reputation repair, how long to recover email reputation > Follow a 3-phase playbook: (1) **stop the bleeding** by pausing harmful sends and checking Google Postmaster, Microsoft SNDS, and blocklists, (2) **rebuild trust** by sending only to highly engaged recipients while InboxAlly generates positive engagement signals, and (3) **ramp volume back up** safely. Most recoveries take 2–12+ weeks depending on severity. Email reputation repair is the process of restoring trust in your sending domain and/or IP so mailbox providers place your messages in the inbox again. If you’re seeing deliverability problems like sudden spam-folder placement, “missing” emails that never show up, throttling (slow or partial delivery), or outright blocks/bounces, you’re in the right place—those are classic signs your sender reputation has dropped. Here’s what you need to know immediately: How long repairs take: most recoveries take 2–12+ weeks, depending on severity. Minor damage can improve in 2–4 weeks, moderate issues often need 4–8 weeks, and severe reputation hits commonly require 8–12+ weeks of disciplined sending. What to check first: confirm the scope of the damage in Google Postmaster Tools, Microsoft SNDS, and your bounce/complaint rates, and check whether you’re on any blocklists. (We’ll walk through each in the next section.) What the 3-phase playbook does: it stops the bleeding, rebuilds trust with high-engagement recipients, then ramps volume back up safely—so you recover email deliverability without triggering new filters. Why this works: deliverability failures often follow a “reputation death spiral.” When engagement drops (low opens/clicks, deletes, complaints), mailbox providers start placing you in spam or limiting delivery. That reduces visibility, which lowers engagement even more—further damaging reputation. The fastest way to break the cycle is to reverse engagement signals by sending only to people most likely to interact positively, then expanding carefully. Set expectations: you can often fix sender reputation and complete domain reputation recovery (and, when relevant, IP reputation repair) without changing domains. But it only works if you pause harmful sends, remove or suppress risky segments, and rebuild using highly engaged recipients. InboxAlly accelerates Phase 2 by generating consistent positive engagement from seed emails, and your IA Reputation Score helps you track recovery progress week over week. If you're not sure where to start, open the IA Assistant inside the InboxAlly app — it can analyze your specific situation and recommend the right recovery path. Diagnosing the damage: what to check (and what “bad” looks like) When deliverability drops, don’t guess. Confirm whether the issue is provider reputation, list/sending health, or filtering/blocklists—then track changes week-over-week (WoW) so you can tell if you’re stabilizing or sliding. Provider diagnostics (Gmail + Microsoft) Google Postmaster Tools (GPT) — focus on trends, not single-day spikes: Domain reputation: “High/Medium/Low/Bad.” Bad looks like: falling from Medium → Low → Bad over 1–2 weeks, or stuck at Low/Bad despite reduced volume. Spam rate: percentage of users marking mail as spam. Bad looks like: sustained elevation WoW (even if daily numbers fluctuate). Any consistent rise alongside lower opens is a red flag. Delivery errors: temporary failures and throttling. Bad looks like: increasing errors WoW, especially after volume increases—often signals reputation or content filtering pressure. Microsoft SNDS/JMRP (Outlook/Hotmail): SNDS IP health: complaint rate indicators and traffic patterns. Bad looks like: worsening status over multiple days, or sharp degradation immediately after a campaign. JMRP complaints: user-reported spam complaints. Bad looks like: complaints rising WoW even when you’re mailing “engaged” segments—usually points to list quality or expectation mismatch. What trends matter WoW: reputation tier movement, complaint/spam-rate direction, and whether errors/throttling correlate with volume changes. List and sending health (what your metrics are telling you) Watch these in your ESP logs and compare last 7 days vs prior 7 days: Hard bounces: permanent failures (invalid/nonexistent). Bad looks like: sudden spike after importing a list or changing acquisition sources (list hygiene issue). Soft bounces: temporary failures (mailbox full, throttling). Bad looks like: gradual climb as volume increases (rate limiting/reputation pressure). Spam complaint rate: Bad looks like: sudden jump after a specific send (content/targeting problem) vs gradual creep (list fatigue). Unsubscribe spikes: Bad looks like: sharp increase tied to one campaign (expectation mismatch) or steady rise (over-mailing). Engagement drop-offs (opens/clicks/replies): Bad looks like: abrupt collapse (placement shifted to spam/promotions) vs slow decline (audience saturation or stale list). Blocklists and filtering (cause vs symptom) Check domain and IP against major blocklists. Confirm it’s the cause: blocklist hits plus immediate widespread bounces/deferrals at multiple providers. Confirm it’s a symptom: blocklist listing appears after weeks of rising complaints/bounces—fix root causes first or you’ll relist. When delisting is urgent: if you’re on a high-impact list and seeing hard blocks/deferrals that prevent delivery entirely. Validate placement with InboxAlly Use the Placement Tester and Email Audit (in the InboxAlly app) to verify inbox vs spam placement across providers and identify whether reputation or content is driving filtering. Run the free Spam Database Lookup for quick visibility into blacklist status before you start ramping volume. Cross-check results with your provider dashboards to ensure your email reputation repair plan is improving WoW, not just “looking better” in one tool. Want guided help? Open the IA Assistant in the InboxAlly app and describe your situation (e.g., “my domain reputation dropped at Gmail” or “I'm getting blocked at Outlook”). It can walk you through the right diagnostic checks and recommend next steps based on your account data. Domain reputation vs IP reputation: what matters most (and when) Domain reputation has become the primary deliverability signal, while IP reputation carries declining weight. 1. IP reputation evaluated based on complaint rates, spam trap hits, volume patterns, and blocklist status — shared across senders on same IP, resets when switching ESPs. 2. Domain reputation evaluated based on engagement rate, authentication alignment, content quality, complaint ratio, and domain age — unique to sender, portable across ESPs. 3. Both signals combine with domain reputation weighted more heavily in modern filtering. 4. Combined reputation score determines inbox, promotions, or spam placement. The difference (and how mailbox providers weigh them) Domain reputation = your brand identity to mailbox providers: the sending domain in the From/Return-Path, authentication alignment (SPF/DKIM/DMARC), historical engagement, complaint rates, and list hygiene tied to that domain. IP reputation = your infrastructure identity: the sending IP’s history (volume patterns, spam traps, blocks, error rates), often influenced by your ESP and whether the IP is shared. In most real-world recoveries, domain reputation is the primary lever—especially for Gmail, which tends to behave “domain-first.” A clean IP won’t reliably overcome a domain that’s generating low engagement or high complaints. Outlook/Microsoft also considers both, but IP-level throttling and filtering can be more visible during incidents. Common scenarios (and what they mean for recovery) Shared IP: Your mail rides alongside other senders. A “good” domain can still perform well, but sudden inbox drops may be IP-neighbor related. You’ll see inconsistent placement across campaigns. Dedicated IP: More control, more responsibility. If you spike volume or send to cold lists, the IP can tank quickly—but Gmail spam placement may persist if the domain is the real problem. New IP + old domain: Often recovers faster than the reverse. If the domain has strong engagement history, warming the new IP is usually straightforward. Old IP + new domain: Risky. Even with a reputable IP, a brand-new domain lacks trust signals; mailbox providers may treat it cautiously until engagement proves otherwise. Why “IP reputation repair” alone may not fix Gmail: if your domain has a complaint/engagement problem, Gmail can continue routing you to spam even after IP blocks clear. How to check domain reputation in practice Use multiple signals—no single dashboard tells the whole story: Gmail: Review Google Postmaster Tools (domain reputation, spam rate, delivery errors). Correlate dips with campaign changes. Microsoft (Outlook/Hotmail): Monitor SNDS/JMRP signals (complaints, traffic patterns, filtering). Corroborate with your metrics: Engagement: opens/clicks (directional), replies, saves/moves-to-inbox List health: hard bounces, unknown users, spam complaints, unsubscribes Action implications: what to fix first Focus on domain cleanup when you see: high complaints, low engagement, poor Postmaster domain reputation. Tighten targeting, remove unengaged segments, improve content/expectations. Use InboxAlly to inject consistent positive engagement and break the spam-placement → low-engagement spiral (see How Does InboxAlly Work and Email Reputation Repair vs Email Warm Up). Track progress with Understanding Your IA Reputation Score. Focus on IP remediation when you see: IP blocks, throttling, or erratic delivery tied to infrastructure. Throttle/ramp volume, stabilize cadence, fix authentication alignment, and address blocks (see Blocklist Impact and Remediation and the Email Ramp Up Schedule). Recovery Phase 1 — Stop the bleeding (first 48–72 hours) Your goal in the first 2–3 days is simple: prevent additional negative signals (complaints, bounces, spam-trap hits, low engagement) while you stabilize authentication and list quality. Don’t “send your way out” of a reputation dip. 1) Pause or sharply reduce non-essential sends (what to stop first) Stop the campaigns most likely to generate complaints or low engagement: Cold or recently imported segments (including partners/leads you haven’t emailed in weeks/months) Re-engagement blasts to long-unengaged users (these often spike complaints and spam placement) Low-intent promotions (broad discounts, affiliate-style offers, “last chance” urgency sends) High-frequency automations that hit many users quickly (daily digests, aggressive nurture steps) Keep only what’s essential and safest: Transactional mail (receipts, password resets) and critical account notices If you must send marketing, limit to your most recently engaged cohort (e.g., opened/clicked in the last 7–14 days) and reduce volume dramatically. Avoid making reputation worse: Don’t change content + volume + infrastructure all at once. Reduce volume first, then fix fundamentals. Don’t “test” by blasting small random batches—send only to known engagers. 2) Fix fundamentals fast (authentication + consistency) In parallel, lock down the basics that mailbox providers use to trust you: SPF, DKIM, and DMARC alignment Ensure the visible From domain aligns with authenticated domains. Start/confirm DMARC policy and reporting (even p=none is better than missing DMARC while you collect data). From-domain consistency Stop rotating From domains/addresses to “escape” filtering—this usually worsens domain reputation recovery. Dedicated tracking domains (where appropriate) Use a branded tracking domain aligned to your From domain to reduce mismatches and improve trust signals. Remove risky sending patterns Eliminate sudden volume spikes, irregular schedules, and multiple new templates at once. Pause link shorteners and overly aggressive subject lines that trigger filtering. 3) List hygiene triage (immediate suppressions) Before the next marketing send, apply emergency suppression rules: Suppress hard bounces and repeated soft bounces Suppress role accounts (e.g., admin@, info@, support@) unless explicitly opted-in and engaged Suppress recent complainers (from feedback loops where available) Suppress unengaged cohorts (start with 30–90+ days no opens/clicks, depending on your normal cadence) Run email list verification and remove obvious bad addresses: Invalids, known spam traps (where detectable), and high-risk catch-alls when possible 4) Blocklist remediation (stop active blocking first) If you’re blocklisted, prioritize remediation by impact: Identify lists that actively block delivery (not just “monitoring” lists). Request delisting only after you’ve reduced volume and fixed authentication/hygiene. Provide evidence: what changed (suppression rules, opt-in sources, authentication fixes), and how you’ll prevent recurrence. Document every change and date—this helps with provider escalation and supports later analysis. For deeper guidance, see Blocklist Impact and Remediation. Recovery Phase 2 — Rebuild with engaged subscribers (break the death spiral) When deliverability is actively failing, your fastest lever is engagement. Mailbox providers use recent recipient behavior (opens, clicks, replies, “not spam,” time spent reading) as a real-time proxy for whether your mail deserves inbox placement. If you keep blasting unresponsive segments, you reinforce the death spiral: low engagement → spam/junk placement → even lower engagement → worse reputation. Phase 2 is about reversing that loop with the people most likely to respond. 1) Segment to your most engaged recipients (your “reputation rehab” list) Prioritize recipients who have shown recent, positive intent. This concentrates engagement signals and reduces negative ones (ignores, complaints, bounces). Build a segment using the last 7–30 days (adjust based on your send frequency): Recent openers/clickers (highest priority) Recent buyers/users (transactions, logins, product activity) Recent repliers (support threads, sales replies) “Not spam” / moved-to-inbox actions (if you can track them) Exclude: Unengaged for 60–90+ days Role accounts (info@, admin@) where possible Known complainers, hard bounces, and risky sources Why this works: engaged recipients are more likely to generate the exact signals mailbox providers reward, which helps fix sender reputation and recover email deliverability faster than trying to “win back” cold segments mid-crisis. 2) Reduce volume and increase quality (make every send count) In Phase 2, you’re not trying to maximize reach—you’re trying to maximize positive feedback per email. Targeting and cadence Send only to the rehab segment until placement stabilizes. Keep a consistent cadence (e.g., 2–3x/week) rather than bursts. If you must email broader lists, do it in small, controlled waves (see the internal Email Ramp Up Schedule). Message design One clear goal per email (avoid mixed CTAs). Fewer links (ideally 1–2 primary links). Excessive linking can look promotional and dilute clicks. Keep copy specific and value-forward: what’s in it for them today. Avoid “spammy” patterns: Overuse of ALL CAPS, excessive punctuation, misleading subject lines Image-only emails or heavy image-to-text imbalance URL shorteners and mismatched link domains Run content checks before sending (formatting, broken links, unsubscribe visibility, and consistent “From” identity). 3) Use InboxAlly to accelerate Phase 2 (not shortcut it) InboxAlly is designed to break the negative placement loop by generating reliable, positive mailbox signals through seed email engagement. When your emails land in seed inboxes, InboxAlly performs actions that mailbox providers interpret as healthy engagement—such as opens, clicks, and moving messages to the inbox—which helps counteract the “ignored in spam” feedback that drags reputation down. Use it as a Phase 2 accelerator alongside your engaged-subscriber segment: Your real audience provides authentic engagement. InboxAlly adds consistent positive placement signals to help stabilize inboxing while you rebuild. For a deeper explanation, see How Does InboxAlly Work and Email Reputation Repair vs Email Warm Up. 4) Operational checklist (daily until stable) Before you scale volume back up, confirm the fundamentals and track trendlines: Authentication alignment SPF passes and aligns with your visible domain DKIM passes and aligns DMARC is present and enforcing (at least p=none during diagnosis; tighten when stable) Monitor placement daily Inbox vs spam placement by provider Bounce rate, complaint rate, and engagement rate on the rehab segment Watch for sudden provider-specific drops (often a filtering change) Track recovery with InboxAlly Monitor your IA Reputation Score to confirm reputation is trending up week-over-week before increasing volume Use Understanding Your IA Reputation Score as your reference for what “improving” looks like in practice Only when placement and IA Reputation Score are consistently improving should you begin Phase 3 scaling. Recovery Phase 3 — Scale back up gradually (ramp-up + re-engagement without relapsing) Once inbox placement stabilizes with your most engaged segment, the goal is to increase volume without re-triggering filtering. Think “controlled expansion,” not “back to normal overnight.” Progressive volume increase (ramp safely by provider + segment) Ramp by mailbox provider (Gmail, Microsoft, Yahoo/AOL) and by engagement tier. Increase only where signals are healthy. Start with your best segment: opened/clicked in the last 7–14 days, recent purchasers, or users who explicitly opted in. Add volume in small steps: a common safe pattern is +15–30% per send (or per day) per provider, holding steady for 24–72 hours between increases. Expand tiers gradually: 0–14 days → 15–30 → 31–60 → 61–90. Treat anything older as re-engagement (below). What “too fast” looks like Deferrals / temp failures spike (4xx responses), especially at Gmail/Microsoft Sudden spam placement increase in one provider while others look fine Engagement drops (opens/clicks) immediately after a volume jump How to respond Stop increasing volume for the affected provider (keep others steady). Roll back 20–40% to the last “clean” level. Tighten segmentation (send only to the most active tier for 2–3 sends). Use InboxAlly to reinforce positive engagement signals during the plateau so you don’t slide back into the reputation death spiral. Track progress with Understanding Your IA Reputation Score. For a step-by-step plan, follow the Email Ramp Up Schedule. Re-engagement campaigns (win-back without blasting) Re-engagement is where many recoveries relapse. Do not “blast the whole list” to test deliverability—large sends to inactive users generate low engagement, higher complaints, and spam placement that can undo weeks of domain reputation recovery. Safer approach: Win-back messaging: short, clear, benefit-led (“Still want updates?”), with a single primary CTA. Preference center: let subscribers reduce frequency or choose topics instead of only “unsubscribe.” Sunsetting rules: if no open/click after 2–3 re-engagement attempts, suppress (or fully remove) those addresses for 60–90+ days. Throttle by provider: re-engage Gmail and Microsoft separately; keep volumes conservative. Monitoring during scale (leading indicators by provider) Watch metrics by mailbox provider, not just overall: Inbox placement (primary KPI) Spam complaints (leading indicator; act fast) Bounces/deferrals (signals throttling or reputation stress) Engagement rate (opens/clicks trending down = risk) If any provider deteriorates, reduce cadence, narrow to higher-engagement tiers, and hold volume until stable. Set up ongoing control loops: Gmail Complaint Feedback Loop Setup Microsoft JMRP and SNDS Timeline expectations, weekly monitoring, and when to choose the nuclear option How long email reputation repair takes (and what slows it down) Most senders see measurable movement within a few weeks, but full recovery depends on how “deep” the negative signals are and how consistently you send improved signals. Typical timelines Minor damage (2–4 weeks): Small dip in inbox placement, mild engagement decline, no major blocklists, complaints under control. Moderate damage (4–8 weeks): Noticeable spam placement at major mailbox providers, elevated bounces/deferrals, reputation warnings in provider dashboards. Severe damage (8–12+ weeks): Heavy spam placement, repeated throttling, persistent blocklisting, or long-term poor engagement history. Factors that extend timelines List quality issues: Old, purchased, or unverified lists; high unknown-user bounces; low recent engagement. High complaint rate: Even “small” complaint spikes can reset progress, especially at Gmail and Microsoft. Blocklists and filtering events: Ongoing listings, slow delisting cycles, or re-listing after a volume spike. Inconsistent sending patterns: Big volume swings, long pauses followed by blasts, or frequent template/domain changes that confuse reputation models. Authentication gaps or misalignment: SPF/DKIM/DMARC problems can prevent positive signals from “sticking.” Week-over-week recovery dashboard (what to track and what “good” looks like) Track recovery in weekly snapshots (not hour-by-hour). Daily fluctuations are normal; trends are what matter. Core metrics to monitor Inbox placement (by provider): Inbox vs spam vs missing. Use consistent tests and compare week-over-week. Domain/IP reputation signals: Gmail: Google Postmaster Tools (domain reputation, spam rate, delivery errors) Microsoft: SNDS/JMRP signals (complaints, data quality, throttling) InboxAlly: IA Reputation Score for a consolidated view of momentum (see Understanding Your IA Reputation Score). Complaint rate: Overall and by provider; watch for spikes tied to specific segments or campaigns. Bounce rate: Separate hard bounces (unknown user) from soft bounces (mailbox full, temporary issues). Engagement: Opens/clicks (directionally), replies, and “positive actions” (moves to inbox, not spam, adds to contacts where applicable). Deferrals/throttling: Temporary rejections, rate limits, and “try again later” responses—often the first sign you’re scaling too fast. What good progress looks like Week 1–2: Deferrals stabilize or decrease; hard bounces drop after list cleanup; spam placement stops worsening. Week 3–4: Inbox placement improves for your most engaged segments; complaint rate trends down and stays down. Week 5–8: Broader segments recover; throttling becomes rare; reputation dashboards move from “bad” to “low/medium,” then upward. Any week: A single blast that triggers complaints or throttling can erase gains—treat volume increases as tests, not milestones. InboxAlly fits here as a Phase 2 accelerator: by generating consistent positive engagement signals from seed emails, you can break the spam-placement → low-engagement loop faster (see How Does InboxAlly Work). When reputation repair won’t work (decision framework) Sometimes “fix sender reputation” isn’t the right goal because the sender identity is no longer trustworthy to mailbox providers. Consider the nuclear option if you have: A compromised domain (phishing/malware history, unauthorized sending, repeated security incidents). Persistent blocklisting that returns quickly after delisting and remediation (see Blocklist Impact and Remediation). Chronic high complaints that don’t improve after list pruning and segmentation. Irreparable brand/domain history: Long-term spam placement, extremely low engagement, or a domain that’s been abused for years. Decision framework: repair vs switch Choose domain reputation recovery if: authentication is solid, complaints are controllable, and you can reliably send only to engaged recipients for several weeks. Choose switching domains if: you can’t stop complaints, you’re repeatedly blocked/throttled despite remediation, or the domain is compromised. For a deeper comparison, see Email Reputation Repair vs Email Warm Up. If you must switch: migrate responsibly (without repeating the problem) Switching domains is not a reset button—it’s a chance to rebuild correctly. Responsible migration checklist Set up a new sending domain/subdomain (aligned with your brand, but clean). Implement authentication (SPF, DKIM, DMARC) before sending any volume. Start with your most engaged recipients only and suppress risky segments. Follow a controlled ramp plan (see the Email Ramp Up Schedule): small, consistent daily sends; gradual increases; no sudden blasts. Use InboxAlly warm-up during the ramp to establish stable engagement signals early and support inbox placement while you scale. Monitor weekly using the dashboard above; pause increases if deferrals or complaints rise. For the email warm-up timeline, see how long does it take to warm up a domain. --- ## How do I get removed from the SpamCop blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/spamcop/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: SpamCop listings are temporary and clear within 24-48 hours after spam reports stop. Fix the root cause and the listing resolves itself. - Keywords: SpamCop blocklist, SpamCop delisting, how to get off SpamCop, SpamCop blacklist removal, SpamCop IP listed > SpamCop is an IP-based, real-time blocklist that can impact B2B email delivery. Listings are usually temporary and **clear automatically within 24–48 hours** after spam reports stop. There's no manual delisting — focus on fixing the root cause (spam trap hits, complaints, compromised server) and the listing will resolve on its own. SpamCop is an IP-based, real-time blocklist that can affect email deliverability—especially for B2B sending—though it is not widely used by major North American ISPs as a primary blocking signal. If your sending IP is listed, it’s usually temporary and often clears automatically within 24–48 hours after reports stop. To confirm whether you’re listed, run a check with InboxAlly’s free Spam Database Lookup. For ongoing monitoring, use Domain Reports in the InboxAlly app. What is SpamCop? SpamCop is a dynamic email blocklist that tracks sending IP addresses (not domains) associated with spam or unwanted email. It updates frequently based on: Spam trap hits User spam reports (complaints) SpamCop listings are typically short-lived and designed to reflect recent behavior from an IP. Why am I listed on SpamCop? SpamCop lists IPs for one of two main reasons: A message was delivered to a SpamCop spam trap address Many SpamCop spam traps are previously valid addresses that have been inactive for 12+ months. A SpamCop user reported your email as unwanted (spam complaint) Common underlying causes include: Compromised accounts or an infected server sending unauthorized mail Misconfigured mail server or open relay behavior Poor list hygiene (old, unengaged, or improperly collected addresses) Sending to outdated or purchased lists How does this affect deliverability? A SpamCop listing can lead to: Bounces or blocks from systems that consult SpamCop Reduced inbox placement (more mail landing in spam) for some recipients Reputation drag if the same IP is repeatedly listed Because SpamCop is IP-based, the impact is tied to the specific sending IP. If you send through shared infrastructure, other senders’ behavior can also contribute to risk. How to get removed from the SpamCop blacklist SpamCop is a dynamic blocklist and typically delists automatically within 24–48 hours after no new spam reports or spam trap hits occur. There is no public manual delist form. To reduce downtime and prevent repeat listings: Pause sending from the listed IP Stop campaigns and any automated flows temporarily. Identify the source of the listing Review mail server logs for unusual volume, unknown accounts, or unexpected outbound traffic. Check for compromised credentials, malware, or unauthorized SMTP activity. Fix the root cause Remove or secure compromised accounts. Tighten authentication and access controls. Improve list hygiene (remove old/unengaged segments; avoid questionable sources). Confirm delisting Re-check your IP status using the Spam Database Lookup. Resume sending gradually Ramp volume back up in steps and watch bounce/complaint signals closely. For ongoing visibility into reputation and related issues, monitor with Domain Reports in the InboxAlly app. Can I dispute a SpamCop listing? If you believe the listing is an error, you can request review via SpamCop’s contact options (typically their website contact form and community forum). When disputing, include: The complete subject line or reference from the SpamCop report (if provided) A clear explanation of why you believe the listing is incorrect Supporting evidence (for example, relevant server logs or message samples) How do I contact SpamCop? SpamCop does not provide a general direct support email. Mail administrators and ISPs typically use the contact form on the SpamCop website, and other users can ask questions in the SpamCop forum. For broader guidance on how blocklists affect sending and what to do next, see Blocklist Impact and Remediation. --- ## What is the difference between soft and hard email bounces? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/email-bounce-management-soft-vs-hard-bounces/ - Section: Troubleshooting & Recovery - Last Modified: 2026-03-10 - Description: Hard, soft, and block bounces each need different handling. Read SMTP codes, set suppression rules, and keep bounce rates under 2%. - Keywords: email bounce management, hard bounce vs soft bounce, what is a hard bounce in email, how to reduce email bounces, email bounce rate, SMTP bounce codes > **Hard bounces** are permanent failures (invalid address, non-existent domain) — remove them immediately. **Soft bounces** are temporary failures (mailbox full, server busy) — suppress after 2–3 consecutive failures. **Block bounces** mean a provider rejected you due to reputation or policy. Aim for a total bounce rate under 2% with hard bounces under 0.5%. Email bounce management is the process of monitoring, classifying, and acting on “bounce back email” responses so you stop sending to addresses that can’t (or won’t) accept mail. It’s a deliverability must-have—not optional cleanup—because mailbox providers treat bounces as a direct signal of list quality. If you keep mailing bad addresses, your sender reputation drops, inbox placement suffers, and even careful warm-up efforts can stall or reverse. Here’s what you need to know upfront. Hard bounces are permanent delivery failures (invalid address, non-existent domain) and should be removed immediately. Soft bounces are temporary failures (mailbox full, server busy, message too large) and usually warrant limited retries. Block bounces happen when a provider rejects you due to policy or reputation (often tied to spam complaints, authentication gaps, or blocklisting). What’s “good”? Aim for an overall email bounce rate under 2%, with hard bounces under 0.5%. Higher rates are a red flag that you’re sending to stale, risky, or unverified contacts. Should you remove soft bounces? Not instantly—but you should suppress after 2–3 consecutive soft bounces and investigate patterns. To reduce email bounces before you send, start with InboxAlly’s Email List Verification, then warm up using a clean list (see email warm-up timeline and Email Ramp Up Schedule). Hard bounce vs soft bounce vs block bounce: what they mean (and how to read SMTP codes) Keep total bounce rate below 2% — hard bounces require immediate suppression, soft bounces get limited retries, block bounces need investigation. 1. Classify the bounce by SMTP response code: 5xx = hard (permanent), 4xx = soft (temporary), policy/reputation rejections = block bounces. 2. Hard bounces (550, 551, 552, 553) are permanent failures — suppress the address immediately, do not retry. 3. Soft bounces (452, 421, 450, 451) — retry up to 3 times over 72 hours, then suppress if still failing. 4. Block bounces require specific investigation: content rejection, IP/domain blocklisting, DMARC policy rejection, rate throttling. 5. All bounce types affect sender reputation — keep total bounce rate below 2%. In email bounce management, “bounce” is the receiving mail system telling you why a message couldn’t be delivered. The most useful way to interpret bounces is by failure type (permanent, temporary, or policy/reputation), then confirm with the SMTP status code. Hard bounce (permanent failure) A hard bounce means the address (or destination) is not deliverable and will not succeed on retry. Common examples user@domain.com doesn’t exist (typo, deleted mailbox) Domain has no valid mail routing (bad MX) Recipient server rejects the address as invalid Action: Suppress immediately. Also run InboxAlly’s Email List Verification before future sends to catch invalid addresses early and reduce email bounces. Soft bounce (temporary failure) A soft bounce indicates a transient condition where delivery may succeed later. Common examples Mailbox is full Recipient server is temporarily unavailable or rate-limiting Message is too large (sometimes temporary, sometimes policy) Action: Retry with backoff (typically 2–3 attempts across 24–72 hours). If it persists, suppress to protect your email bounce rate and sender reputation. Block bounce (policy/reputation rejection) A block bounce is a rejection based on policy, authentication, content, or reputation—not because the mailbox is invalid. Common examples IP/domain reputation is poor Missing/failed SPF, DKIM, or DMARC alignment Content triggers filtering or the recipient requires TLS/auth Action: Treat as urgent. Review authentication, complaint signals, and sending patterns. See Blocklist Impact and Remediation and Understanding Your IA Reputation Score. High bounces also undermine warm-up—clean lists first, then follow Email Ramp Up Schedule. Common SMTP enhanced status codes (and what to do) Enhanced code Typical meaning Bounce type Recommended action 5.1.1 Bad destination mailbox address Hard Suppress immediately; verify list source 5.1.0 Invalid address / recipient unknown Hard Suppress; run list verification 5.2.2 Mailbox full Soft Retry 2–3 times; suppress if persistent 4.2.2 Mailbox full / over quota (temporary) Soft Retry with backoff; monitor recurrence 4.4.1 Connection timed out / no response Soft Retry; check sending infrastructure 5.7.1 Delivery not authorized / blocked Block Investigate reputation/auth/content; remediate before scaling Why ESP “bounce categories” differ (and how to normalize) Email platforms often label bounces differently because they: Parse different parts of the SMTP reply (enhanced code vs text) Map provider-specific messages into generic buckets Treat some 5.x.x codes as “blocked” while others call them “hard” Normalize with your own decision rules If 5.1.x → Hard: suppress immediately. If 4.x.x → Soft: retry 2–3 times, then suppress. If 5.7.x (or explicit “blocked”) → Block: pause scaling, fix reputation/auth, then resume. What is an acceptable email bounce rate (and when it becomes a deliverability problem)? For healthy email bounce management, most programs should target: Total bounce rate: < 2% (hard + soft combined) Hard bounce rate: < 0.5% If you’re a high-volume sender (large daily/weekly sends), mailbox providers typically expect even tighter control because your reputation signals accumulate faster. In practice, treat 1% total as a “watch closely” line and 2% as “fix immediately.” How to calculate bounce rate (correctly) Use attempted deliveries as the denominator (not opens/clicks, and not “sent” after suppressions). Formula: Bounce rate = (Total bounces ÷ Total delivery attempts) × 100 Also calculate: Hard bounce rate: Hard bounces ÷ Attempts Soft bounce rate: Soft bounces ÷ Attempts To find the real source of issues, segment bounce rates by: Mailbox provider (e.g., provider A vs provider B) Campaign/message type (newsletter vs promo vs transactional) List source (lead magnet, event upload, partner import, older segments) Before ramping volume, run InboxAlly’s Email List Verification to remove invalid addresses—high bounces can undermine warm-up and reputation gains. Red flags that require escalation Investigate immediately when you see: Sudden spikes (e.g., 0.6% → 3% overnight): often list quality, authentication, or routing changes. Provider-specific bounces: one provider rejecting while others deliver suggests reputation or policy filtering. Rising hard-bounce share: indicates list decay, typos, or risky acquisition sources. Repeated soft bounces for the same addresses across multiple sends: suppress after 2–3 retries to prevent reputation drag. If bounces coincide with blocks, review Blocklist Impact and Remediation and your Understanding Your IA Reputation Score. How bounces damage sender reputation (and why ISPs penalize high-bounce senders) Mailbox providers treat bounces—especially hard bounces (“unknown user,” “no such mailbox”)—as a high-confidence signal that your list acquisition and maintenance are weak. When bounce patterns suggest you’re sending to people who never asked for your email, ISPs protect their users by reducing your inbox access. The signals ISPs infer from bounce patterns High bounce rates don’t just indicate delivery failure; they imply risk: List acquisition quality: Large spikes in “unknown user” bounces often correlate with scraped, purchased, or poorly validated lists. User intent mismatch: If many recipients don’t exist (or were never real subscribers), ISPs assume low consent—an environment where spam complaints are more likely. “Unknown user” patterns at scale: Repeated invalid-recipient errors across multiple domains look like automated list generation or stale data. Trap correlation: The same behaviors that create bounces (typos, old lists, role accounts) also increase the odds of hitting typo and recycled spam traps—both strong negative reputation signals. Downstream deliverability impacts Once bounce-driven risk rises, providers may apply escalating penalties: Throttling and deferrals: Slower acceptance rates, more temporary failures, and longer queues. Increased spam placement: Even accepted mail is filtered more aggressively. Hard blocks (e.g., 5.7.1): Policy-based rejections tied to reputation and suspected abuse. Longer recovery time: Reputation rebuilds slowly; a few bad sends can outweigh weeks of “normal” performance. For remediation workflows, see Blocklist Impact and Remediation and Understanding Your IA Reputation Score. Why bounces undermine warm-up and ramp-up Warm-up relies on consistent positive engagement signals. If your ramp-up includes high bounces, engagement can’t compensate because ISPs may limit delivery before users can open, read, or reply. Best practice sequence: Clean first: Run InboxAlly’s Email List Verification to remove invalid and risky addresses. Then ramp: Follow a controlled Email Ramp Up Schedule so engagement signals build on a healthy list. Root causes of bounces: diagnose what’s really happening to your list and infrastructure High bounce rates don’t just waste sends—they signal poor list hygiene or infrastructure issues that can drag down reputation and undermine email bounce management. Start by separating list-quality problems from mailbox/provider problems, then validate with evidence. List-quality causes (your data is the problem) These typically show up as hard bounces and repeat across many domains: Stale lists: old subscribers, abandoned inboxes, recycled addresses. Purchased/rented lists: high invalid rates, spam traps, and role accounts; expect rapid reputation damage. Typo traps: misspellings like gmial.com or yaho.com leading to “user unknown.” Role-based addresses: info@, support@, sales@ often reject or filter aggressively. Disposable/catch-all domains: temporary inbox providers or domains that accept-all but later reject; can look like soft bounces first. Bad signup sources: low-intent lead gen, unvalidated forms, incentivized signups, or missing double opt-in. Use InboxAlly’s Email List Verification before sending—clean lists first, then warm up. High bounces can distort progress in Email Ramp Up Schedule plans. Mailbox/provider causes (their side or your configuration) These often appear as soft bounces or intermittent failures: Full mailboxes: recipient storage exceeded. Temporary server issues: provider downtime or throttling. Greylisting: “try again later” behavior for new/unknown senders. DNS/authentication misconfigurations: missing/incorrect SPF, DKIM, DMARC alignment. Routing problems: bad MX records, TLS negotiation failures, or upstream network issues. If bounces coincide with blocks, review Blocklist Impact and Remediation and your Understanding Your IA Reputation Score. Map causes to evidence (what to look at) Use a structured triage: Bounce message + SMTP code (most reliable signal). Provider patterns (one domain vs. many). Time-based trends (new vs. old subscribers; sudden spike vs. gradual creep). Signal Common SMTP code Likely cause “User unknown / no such user” 550 / 5.1.1 Invalid/stale/typo address “Mailbox full” 552 / 5.2.2 Full recipient inbox (soft) “Try again later / deferred” 421 / 4.7.x Greylisting/throttling “Authentication required/failed” 550 / 5.7.x SPF/DKIM/DMARC or policy issue “Host not found / no MX” 550 / 5.1.2 DNS/routing problem Bounce handling best practices: suppression rules that reduce email bounces without losing good subscribers Strong email bounce management protects sender reputation and keeps your list usable. The goal is simple: suppress addresses that will never deliver, while giving temporary failures a short, controlled chance to recover. Hard bounces: suppress immediately (permanent failures) Hard bounces indicate a mailbox or domain that doesn’t exist. Continuing to send will inflate your email bounce rate and damage reputation. Best practice rules Suppress/remove on first occurrence for permanent 5xx failures. Treat these as permanent: “Unknown user” / “user does not exist” (typically 550 5.1.1) “Domain not found” / NXDOMAIN (often 550/553 variants) Keep an audit trail: store timestamp, SMTP code, bounce reason, campaign/message ID, and source list. Prevent re-imports: maintain a global suppression table and block uploads that contain suppressed addresses (or auto-suppress on import). Soft bounces: retry briefly, then suppress (temporary failures) Soft bounces are usually transient (mailbox full, temporary routing issues). But repeated soft bounces become a deliverability liability. Retry strategy Retry 2–3 attempts across separate sends (not rapid-fire retries). If the address soft-bounces on all attempts, suppress (or move to a “needs reconfirmation” segment). Differentiate transient vs persistent 4xx Pattern Typical SMTP signal Action Transient issue (temporary) 421/450/451 Retry on next send (up to 2–3 total) Persistent 4xx (repeated) Same 4xx over multiple sends Suppress after threshold; investigate list quality Block bounces: treat as a deliverability incident Blocks (often policy/reputation-related) can spike quickly and affect your entire program. Response playbook Pause or rate-limit sending to the affected domain/provider. Investigate reputation, authentication (SPF/DKIM/DMARC), content patterns, and complaint signals. Cross-reference: Blocklist Impact and Remediation and Understanding Your IA Reputation Score. Prevention: reduce bounces before you send Use double opt-in to confirm ownership and reduce typos. Add typo correction at capture (common domains, missing “.com”, etc.). Run Email List Verification before campaigns to catch invalid/risky addresses. For warming: clean lists first, then warm up—high bounce rates undermine ramp-up. See Email Ramp Up Schedule. List hygiene, spam traps, and ongoing monitoring: build a repeatable bounce management process Build a list hygiene system (cadence + re-engagement + sunset policy) A consistent hygiene routine is the fastest way to reduce email bounces and protect sender reputation. Verification cadence Verify before any new import and before major sends (promotions, seasonal spikes). For ongoing programs, re-verify the full list every 30–60 days (more often if acquisition volume is high). Use Email List Verification to catch invalid, risky, and typo-prone addresses before they become hard bounces. Re-engagement before purging Run a 2–3 email sequence to inactive subscribers (value reminder → preference update → “still want emails?”). If there’s no engagement, suppress rather than repeatedly retrying—continued sends to non-responders increases bounce risk over time. Clear sunset policy Define inactivity by your cycle (example: no opens/clicks in 90–180 days). After the re-engagement window, move contacts to a sunset segment (no regular campaigns; optional quarterly check-in). Immediately suppress any address that hard bounces, and suppress repeated soft bounces per your retry rules. Spam traps: what they are and how bounces connect Spam traps are addresses used to identify poor list practices. Common types: Pristine traps: never opted in; usually come from scraping, purchased lists, or bad form practices. Recycled traps: old, abandoned addresses repurposed by providers—often hit when you keep mailing stale lists. Typo traps: misspellings (e.g., gmial.com) that slip through without verification. Why bounce management matters: high bounce rates and weak acquisition controls correlate with trap hits (stale data, typos, and low-quality sources). Avoidance steps: Use double opt-in where possible. Verify at capture/import; block obvious typos and role accounts when appropriate. Remove hard bounces immediately; sunset inactives on schedule. Audit + monitoring workflow (weekly, segmented, documented) Weekly dashboard checks Track total bounce rate, hard bounce rate, and trends by campaign. Segment by provider (Gmail, Yahoo, Microsoft) to spot localized delivery failure. Alert thresholds Investigate at >2% total bounces or >0.5% hard bounces; pause scaling if rising week-over-week. Document changes Log list sources, verification dates, suppression rules, and send volume changes. Use InboxAlly monitoring Review IA Reputation Score and Domain Reports for ongoing visibility; see Understanding Your IA Reputation Score and align volume changes with Email Ramp Up Schedule. Need help diagnosing bounce issues? Open the IA Assistant in the InboxAlly app for guidance, or start a free trial to verify your list and monitor deliverability. --- ## How do I get removed from the Barracuda blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/barracuda/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: The Barracuda BRBL is widely used by enterprise mail filters. Fix spam traps, open relays, or list hygiene issues, then request delisting. - Keywords: Barracuda blocklist removal, Barracuda BRBL delisting, how to get off Barracuda blacklist, Barracuda reputation block list, Barracuda email blocked > The Barracuda Reputation BlockList (BRBL) flags sending IPs associated with spam, open relays, or spam trap hits. It's widely used by enterprise email security appliances and can significantly impact B2B email delivery. Fix the root cause (list hygiene, authentication, compromised server), then submit a removal request through Barracuda's delisting portal. The Barracuda Reputation BlockList (BRBL) is a real-time database of IP addresses that Barracuda products may treat as untrusted due to spam-like behavior or risky server configurations. If your sending IP is listed, recipients using Barracuda filtering may reject or quarantine your emails. To check whether your IP or domain appears on Barracuda (and other major lists), use InboxAlly’s free Spam Database Lookup. What is the Barracuda Reputation BlockList? The Barracuda Reputation BlockList is a reputation-based list of sending IP addresses that have been associated with: Spam or virus distribution Open relay behavior (mail servers that allow unauthorized sending) Compromised systems (e.g., botnet-like sending patterns) Spam trap hits (emails sent to addresses used to identify unsolicited mail) Barracuda’s filtering products can use this list to decide whether to accept, block, or route mail from a given IP. Why am I listed on the Barracuda Reputation BlockList? Common reasons an IP ends up listed include: A compromised mailbox or server sending unexpected volumes or patterns Poor list hygiene, leading to spam complaints, bounces, or spam trap hits Misconfigured mail server settings, such as an open relay Shared IP risk (if you send from a shared IP, another sender’s behavior can impact the IP reputation) Tip: If you’re not sure whether the issue is your domain, your IP, or both, run a scan with the Spam Database Lookup and document what’s listed before making changes. How do I get removed from the Barracuda Reputation BlockList? Barracuda typically requires a delisting request after you’ve addressed the underlying cause. A practical removal workflow is: Confirm the listing (IP address and any related sending infrastructure). Fix the root cause: Close any open relay configuration. Secure compromised accounts (password resets, MFA, access review). Pause or reduce sending volume if you see abnormal spikes. Clean your list to remove invalid addresses and high-risk segments. Request removal through Barracuda’s delisting process (their removal request page). Monitor after delisting to ensure the issue doesn’t recur. If you’re listed again shortly after removal, it usually means the underlying sending behavior or configuration problem is still present. How does Barracuda listing affect deliverability? If your IP is on the Barracuda Reputation BlockList, you may see: Hard blocks (messages rejected at connection time) Quarantining (messages accepted but held for review) Lower inbox placement for recipients behind Barracuda filtering (common in B2B environments) Because Barracuda decisions are often made at the IP reputation level, the impact can be immediate—especially if you send to corporate domains that use Barracuda appliances or services. InboxAlly tools to help you monitor and prevent repeat listings Use the free Spam Database Lookup to check your domain and IP against major blocklists. Use Domain Reports (in the InboxAlly app) for ongoing monitoring of domain reputation and authentication status. For a broader remediation workflow, see: Blocklist Impact and Remediation. --- ## Is the SORBS blocklist still active? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/sorbs/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: SORBS was decommissioned in June 2024. If you still see a SORBS listing, it is a legacy reference — remove it from your filtering config. - Keywords: SORBS blocklist, is SORBS still active, SORBS decommissioned, SORBS blacklist removal, SORBS DNSBL shutdown > No — SORBS was officially **decommissioned in June 2024**. It no longer accepts spam reports, publishes active blocklist data, or processes delisting requests. If you still see a SORBS listing in a tool or mail server config, it's a legacy reference that should be removed from your filtering configuration. SORBS was officially decommissioned in June 2024. It no longer accepts spam reports, publishes active blocklist data, or processes delisting requests—so any "SORBS listing" you see today is a legacy reference and should be removed from filtering configurations. To check whether your domain or IP is currently flagged on active blocklists, use InboxAlly’s free Spam Database Lookup. For ongoing monitoring, use Domain Reports in the InboxAlly app. What is SORBS? SORBS (Spam and Open Relay Blocking System) was a DNS-based blocklist (DNSBL) that historically listed IPs/domains suspected of sending spam or operating insecure mail infrastructure (like open relays). As of June 2024, SORBS is offline and no longer maintained, so it should not be relied on for modern filtering decisions. Why am I listed on SORBS? If you’re seeing references to a SORBS "listing," it’s typically due to one of these situations: Outdated documentation or tooling still checking SORBS zones Legacy logs from older deliverability incidents Mail server or gateway configurations that still reference SORBS for blocking decisions Historically (before decommissioning), SORBS used signals such as: Spam traps (addresses used to identify unsolicited mail) User complaints and direct reports received by administrators Behavioral patterns associated with bulk spam activity Dynamic IP ranges (often flagged to discourage running mail servers on consumer/residential connections) How to get removed from SORBS You can’t. Since SORBS is decommissioned, there is no active delisting process and no authoritative listing data to remove. What you should do instead: Remove SORBS from any filtering or monitoring configuration Check mail gateways, anti-spam appliances, and any custom DNSBL checks. Verify your real blocklist status on active lists Run a scan with InboxAlly’s free Spam Database Lookup. Set up ongoing monitoring Use Domain Reports in the InboxAlly app to track reputation and authentication signals over time. How does this affect deliverability? A SORBS "listing" should have minimal to no impact on deliverability today because the service is decommissioned and no longer provides active data. However, deliverability problems can still happen if: A receiving system is misconfigured and still attempts to use SORBS (this can cause false blocks or lookup failures). You’re listed on other active blocklists (which can directly affect acceptance, throttling, or spam placement). If you’re troubleshooting delivery issues, start by confirming your current status with the Spam Database Lookup, then address any active listings and underlying causes (list hygiene, authentication, complaint rates, sending patterns). Frequently Asked Questions What was the purpose of the SORBS spam list? SORBS aimed to reduce spam and abuse by listing sources associated with spam sending, open relays, compromised systems, and other risky email infrastructure. What happened to the SORBS spam blocklist? It was officially decommissioned in June 2024. SORBS is no longer maintained, and its reporting, lookup, and delisting functions are shut down. Can I do a SORBS blacklist check? Not in a meaningful, current way—SORBS is decommissioned. Instead, check your domain/IP against active blocklists using InboxAlly’s Spam Database Lookup. How did SORBS collect spam data (historically)? Before shutdown, SORBS relied on spam traps, user/admin complaints, and analysis of sending/network behavior patterns. Why did SORBS target dynamically allocated IP addresses? Dynamic/residential IPs are more likely to be associated with compromised devices and are generally not intended for running mail servers. SORBS historically listed many of these ranges to reduce abuse. For a step-by-step process to assess impact and fix active listings, see Blocklist Impact and Remediation. --- ## What are email blocklists and how do they affect deliverability? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklist-impact-and-remediation/ - Section: Troubleshooting & Recovery - Last Modified: 2026-03-12 - Description: Not all blocklists matter equally. See which ones ISPs actually use, their impact on delivery, and how to prioritize remediation. - Keywords: email blocklist, DNSBL impact on deliverability, how do email blacklists work, blocklist remediation, which blocklists matter most, email blocklist removal > Email blocklists (DNSBLs) are databases of IPs and domains flagged for spam-like behavior that ISPs and mailbox providers use to filter incoming mail. **High-impact lists** like Spamhaus and Barracuda can cause bounce rates over 50% and severe delivery failures. **Lower-impact lists** may only affect scoring or B2B delivery. Not all blocklists matter equally — focus on the ones your recipients' providers actually use. An email blocklist (also called a DNSBL or RBL) is a database of IPs or domains flagged for spam-like behavior. ISPs and mailbox providers query these lists in real time to filter incoming mail. Not all blocklists matter equally. High-impact lists like Spamhaus and Barracuda can push bounce rates above 50%. Lower-impact lists may only affect spam scoring or niche B2B delivery. The key is knowing which ones your recipients' providers actually use. Understanding Blacklist Impact High Impact Blocklists These are the most critical lists that can cause significant delivery problems: Spamhaus — the most widely used blocklist. A listing can cause bounce rates over 50%. Most major North American ISPs use Spamhaus for blocking decisions. Barracuda — widely used by enterprise email security appliances. Significant impact on B2B delivery. SpamCop — significant B2B impact, though less widely used by major consumer ISPs. Medium Impact Blocklists These lists can impact delivery but are less widely used: SORBS — uses spam traps, user complaints, and admin reports to identify spammers. Multiple specialized lists. UCEPROTECT — three levels of blocklists. Level 1 (individual IPs) is the most commonly used. Abusix — commercial blocklist used by many European ISPs and enterprises. Low Impact Blocklists These lists are unlikely to significantly impact delivery but may be used by smaller providers: Many of these are regional or specialized lists that focus on specific types of abuse or geographic areas. Some are community-maintained lists that may not have the same level of accuracy as major commercial lists. How Email Blacklists Work Never request removal until the root cause is fixed — premature delisting leads to relisting cycles. 1. Detect deliverability drop — identify symptoms: inbox placement drops, SMTP blocks increase, bounce rates spike. 2. Check blocklists using MXToolbox or multirbl.valli.org to check if your IP or domain is listed. 3. Identify which blocklist and assess severity — Spamhaus SBL/DBL are severe, Spamcop and Barracuda are moderate. 4. Investigate root cause: spam traps, high complaints, compromised account, or purchased list. 5. Fix root cause first — resolve the issue before requesting removal, as premature removal leads to relisting. 6. Request removal via auto-expire (24-48h) or manual request with evidence. 7. Verify delisting and monitor for relisting. Blacklists maintain databases of IPs and domains flagged for spam or abuse. When a mail server receives a message, it queries these lists to decide whether to accept, filter, or reject it. Types of Blacklists IP-based Blacklists (DNSBL) Check the IP address of the sending mail server Most commonly used by major ISPs and email providers Examples: Spamhaus ZEN, Barracuda, SpamCop Domain-based Blacklists (RHSBL) Check the domain name in email headers or content Used to identify spam domains and phishing sites Examples: Spamhaus DBL, SURBL, URIBL Specialty Blacklists Focus on specific types of abuse (TOR nodes, open proxies, etc.) Used by security-conscious organizations Examples: DroneBL, Backscatterer, CYMRU Bogons How to Check Your Blacklist Status Check your IP or domain against all major blocklists using our Spam Database Lookup Tool. What to Look For When checking your blacklist status, pay attention to: High-impact listings - These require immediate attention Listing reasons - Understanding why you were listed helps prevent future issues Delisting procedures - Each blacklist has different removal processes Prevention strategies - Learn from listings to improve your email practices Getting Delisted from Blacklists If you're listed, fix the root cause first — premature delisting leads to relisting. 1. Identify the listing reason Common causes: Spam or unsolicited bulk email Open relay or proxy Malware infection Missing email authentication High bounce rates or complaints 2. Fix the underlying issue Set up SPF, DKIM, and DMARC Clean your list — remove invalid addresses Secure your sending infrastructure 3. Request delisting Most blocklists have online delisting forms Provide evidence the issue is resolved Allow 24–48 hours for processing 4. Monitor going forward Check your blocklist status regularly Track bounces, complaints, and engagement Maintain good sending practices For a detailed walkthrough, see How to Get Off of Email Blacklists. Complete Blacklist Reference Every blocklist we monitor, organized by impact level. Each entry includes the DNS lookup zone and a link to check your status. High Impact Blocklists Major IP Blacklists Spamhaus ZEN - Combined IP blacklist (SBL, XBL, PBL) for spam, botnets, infected IPs Lookup Zone: zen.spamhaus.org Check Now Barracuda - IP reputation blacklist by Barracuda Networks Lookup Zone: b.barracudacentral.org Check Now SpamCop - Blacklist of IPs sending to spam traps or reported as spammers Lookup Zone: bl.spamcop.net Check Now Abusix Mail Intelligence (IP) - Trap-based IP blacklist for spam, exploits, botnets Lookup Zone: ip.mail.abusix.zone Check Now UCEPROTECT L1 - Abusive IPs detected by UCEPROTECT Lookup Zone: dnsbl-1.uceprotect.net Check Now 0SPAM - Free DNSBL for IPs sending spam to spam traps Lookup Zone: 0spam.fusionzero.com Check Now 0SPAM RBL - 0SPAM's real-time DNSBL for IPs detected sending spam Lookup Zone: rbl.0spam.org Check Now SWINOG - Swiss Network Operators Group DNSBL for spam and abuse Lookup Zone: dnsbl.swinog.ch Check Now TRIUMF - TRIUMF DNSBL for spam and open relay detection Lookup Zone: dnsbl.triumf.ca Check Now NoSolicitado - Spanish-language DNSBL for spam and abuse sources Lookup Zone: bl.nosolicitado.org Check Now Abusix Exploit - Abusix DNSBL for IPs involved in exploits, malware, and abuse Lookup Zone: exploit.mail.abusix.zone Check Now Major Domain/URI Blacklists Spamhaus DBL - DNSBL for domains seen in spam, phishing, and malware Lookup Zone: dbl.spamhaus.org Check Now SURBL multi - Aggregated DNSBL for domains/URLs found in spam messages Lookup Zone: multi.surbl.org Check Now URIBL - Blacklist for domains appearing in unsolicited or bulk email Lookup Zone: multi.uribl.com Check Now ivmURI - Invaluement's DNSBL for domains and URIs found in spam and phishing emails Lookup Zone: dnsbl.ivmURI.com Check Now Abusix Mail Intelligence Blacklist - Trap-based blacklist of domains in spam, phishing, and malware Lookup Zone: dblack.mail.abusix.zone Check Now IBM DNS Blacklist - IBM X-Force Threat Intelligence DNSBL for malicious and suspicious domains Lookup Zone: dnsbl.cobion.com Check Now Lashback - Unsubscribe/opt-out abuse list for domains violating CAN-SPAM rules Lookup Zone: ubl.unsubscore.com Check Now SEM URI - SEM Labs' DNSBL for URIs found in spam and phishing emails Lookup Zone: uribl.semeon.com Check Now SEM URIRED - SEM Labs' DNSBL for high-risk URIs and domains Lookup Zone: urired.semeon.com Check Now SEM FRESH - SEM Labs' DNSBL for newly observed domains and URIs Lookup Zone: fresh.semeon.com Check Now Anonmails DNSBL (Domain) - Community-maintained domain blacklist for abuse and phishing Lookup Zone: rhsbl.anonmails.de Check Now Nordspam DBL - Nordic-focused domain blacklist for spam and abuse Lookup Zone: dbl.nordspam.com Check Now SORBS RHSBL BADCONF - SORBS DNSBL for domains with bad configuration or setup issues Lookup Zone: badconf.rhsbl.sorbs.net Check Now Medium Impact Blocklists Specialty IP Blacklists Backscatterer - Detects mail servers that send non-delivery bounces to forged email addresses Lookup Zone: ips.backscatterer.org Check Now CYMRU Bogons - Lists bogon (unallocated/reserved) IP ranges never used for legitimate email Lookup Zone: v4.fullbogons.cymru.com Check Now DroneBL - IPs detected as bots, drones, or open proxies often used for abuse Lookup Zone: dnsbl.dronebl.org Check Now DAN TOR - Lists known TOR exit node IPs Lookup Zone: tor.dnsbl.sectoor.de Check Now DAN TOREXIT - DNSBL for active TOR exit IPs Lookup Zone: toreexit.dan.me.uk Check Now SEM BACKSCATTER - SEM Labs' backscatter detection list Lookup Zone: backscatter.semeon.com Check Now SEM BLACK - SEM Labs' IP blacklist for spam sources Lookup Zone: black.semeon.com Check Now FABELSOURCES - Lists IPs detected as sources of spam, malware, or abuse Lookup Zone: blackholes.fabel.dk Check Now IMP SPAM - IMP SPAM tracks IPs associated with spam and abusive activity Lookup Zone: dnsbl.imp.ch Check Now IMP WORM - IPs involved in worm and virus propagation Lookup Zone: wormbl.imp.ch Check Now Policy and Relay Blacklists SORBS DUL - SORBS Dynamic User List for dynamic/residential IPs Lookup Zone: dul.dnsbl.sorbs.net Check Now SORBS HTTP - SORBS HTTP blacklist for web-based spam sources Lookup Zone: http.dnsbl.sorbs.net Check Now SORBS SMTP - SORBS SMTP blacklist for mail server abuse Lookup Zone: smtp.dnsbl.sorbs.net Check Now SORBS SOCKS - SORBS SOCKS proxy blacklist Lookup Zone: socks.dnsbl.sorbs.net Check Now SORBS MISC - SORBS miscellaneous abuse blacklist Lookup Zone: misc.dnsbl.sorbs.net Check Now SORBS ZOMBIE - SORBS zombie computer blacklist Lookup Zone: zombie.dnsbl.sorbs.net Check Now SORBS SPAM - SORBS spam blacklist Lookup Zone: spam.dnsbl.sorbs.net Check Now SpamRats DUL - SpamRats Dynamic User List Lookup Zone: dul.spamrats.com Check Now SpamRats DYNIP - SpamRats Dynamic IP blacklist Lookup Zone: dynip.rothen.com Check Now SpamRats NOPTR - SpamRats No PTR record blacklist Lookup Zone: noptr.spamrats.com Check Now SpamRats SPAM - SpamRats spam blacklist Lookup Zone: spam.spamrats.com Check Now SpamRats DYNA - SpamRats dynamic IP blacklist Lookup Zone: dyna.spamrats.com Check Now Regional and Community Blacklists Korea Services - Korean-focused spam blacklist Lookup Zone: korea.services.net Check Now Manitu - German ISP blacklist for spam and abuse Lookup Zone: ix.dnsbl.manitu.net Check Now Singular - Hungarian university spam blacklist Lookup Zone: singular.ttk.pte.hu Check Now Anonmails - German community spam blacklist Lookup Zone: spam.dnsbl.anonmails.de Check Now SpamSpike - MailSpike spam blacklist Lookup Zone: z.mailspike.net Check Now Low Impact Blocklists Malware and Exploit Blacklists Abusix Malware - Abusix malware detection blacklist Lookup Zone: malware.mail.abusix.zone Check Now Abusix Phishing - Abusix phishing detection blacklist Lookup Zone: phishing.mail.abusix.zone Check Now Abusix Exploit - Abusix exploit detection blacklist Lookup Zone: exploit.mail.abusix.zone Check Now Virus RBL JP - Japanese virus blacklist Lookup Zone: virus.rbl.jp Check Now IMP WORM - IMP worm and virus blacklist Lookup Zone: worrmbl.imp.ch Check Now Miscellaneous Operator Blacklists WoodyNet - WoodyNet spam blacklist Lookup Zone: woodybl.dnsbl.woodynet.net Check Now Cymru Bogons - Cymru bogon IP blacklist Lookup Zone: bogons.cymru.com Check Now CBL - Composite Blocking List Lookup Zone: cbl.abuseat.org Check Now Combined Abuse.ch - Combined abuse.ch blacklists Lookup Zone: combined.abuse.ch Check Now WPBL - WPBL spam blacklist Lookup Zone: db.wpbl.info Check Now UCEPROTECT L2 - UCEPROTECT Level 2 blacklist Lookup Zone: dnsbl-2.uceprotect.net Check Now UCEPROTECT L3 - UCEPROTECT Level 3 blacklist Lookup Zone: dnsbl-3.uceprotect.net Check Now DroneBL - DroneBL botnet blacklist Lookup Zone: drone.abuse.ch Check Now SORBS - SORBS general blacklist Lookup Zone: dnsbl.sorbs.net Check Now SPFBL - SPFBL spam blacklist Lookup Zone: dnsbl.spfbl.net Check Now DUINV - DUINV spam blacklist Lookup Zone: duinv.aupads.org Check Now ORVEDB - ORVEDB spam blacklist Lookup Zone: orvedb.aupads.org Check Now PBL - Policy Block List Lookup Zone: pbl.spamhaus.org Check Now Proxy BL - Proxy blacklist Lookup Zone: proxy.bl.gweep.ca Check Now PSBL - PSBL spam blacklist Lookup Zone: psbl.surriel.com Check Now Relays BL - Relays blacklist Lookup Zone: relays.bl.gweep.ca Check Now Relays Nether - Relays Nether blacklist Lookup Zone: relays.nether.net Check Now SBL - Spamhaus Block List Lookup Zone: sbl.spamhaus.org Check Now XBL - Exploits Block List Lookup Zone: xbl.spamhaus.org Check Now --- ## How do I get removed from the Invaluement blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/invaluement/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: Invaluement flags domains, URLs, and IPs tied to spam traps or snowshoe patterns. Identify your listing type and submit a removal request. - Keywords: Invaluement blocklist, Invaluement delisting, how to remove from Invaluement, Invaluement URI blacklist, Invaluement SIP removal > Invaluement publishes multiple DNS-based blocklists that flag suspicious domains, URLs, and sending IPs. Listings typically result from spam trap hits, snowshoe sending patterns, or domains found in spam message links. Fix the underlying issue and submit a delisting request through Invaluement's lookup tool. Invaluement is a third-party anti-spam operator that publishes several DNS-based blocklists used by some spam filters to flag suspicious domains and sending IPs. If your domain or IP appears on an Invaluement list, some recipients may see your mail filtered to spam, rejected, or delayed—depending on how their provider uses the list. What is Invaluement? Invaluement maintains multiple blocklists that focus on different spam signals: InvaluementURI: Lists domains and IPs found in URLs inside spam messages (i.e., link destinations). InvaluementSIP: Lists sending IP addresses that are observed sending a high percentage of spam. InvaluementSIP/24: Lists larger IP ranges (a /24 network) when spam patterns are detected across related IPs. These lists are commonly consumed by security gateways and spam filtering systems to help identify unwanted mail. Why am I listed? The most common reasons for appearing on an Invaluement list map to the list type: Listed on InvaluementURI Your domain (or a domain you control) appears in links inside messages classified as spam. Common causes include compromised websites, abused tracking domains, or links used by affiliates/third parties in ways that trigger spam complaints. Listed on InvaluementSIP Your sending IP is associated with high spam rates, complaint rates, or poor list hygiene (e.g., many invalid recipients). This can also happen if you’re on shared infrastructure and another sender on the same IP is generating abuse. Listed on InvaluementSIP/24 Multiple IPs in the same /24 range show spam-like behavior, causing the entire range to be blocked. How does this affect deliverability? Impact varies by recipient environment, but common outcomes include: Spam folder placement (reputation-based filtering) Temporary deferrals (messages delayed and retried) Hard rejections (mail refused at the gateway) If only some mailbox providers or corporate gateways use Invaluement, you may see deliverability issues limited to specific recipients rather than across your whole list. To quickly confirm whether you’re listed, run your domain and sending IP through InboxAlly’s free Spam Database Lookup. How to get removed from Invaluement’s blocklists Invaluement supports manual delisting requests, but removal typically requires you to fix the underlying cause first. A practical remediation flow: Identify what’s listed Check whether the listing is for your sending IP, your domain, or a linked/tracking domain used in messages. Stop the behavior that triggered the listing Pause or reduce sending from the affected IP/domain if you’re seeing active filtering. Fix list hygiene issues (remove invalid addresses, reduce bounce rates, confirm opt-in where applicable). If the issue is URI-based, audit the domains in your links: Remove/replace suspicious redirect chains Ensure your website isn’t compromised Disable abused subdomains or tracking endpoints Request delisting from Invaluement Submit a delisting request through Invaluement’s published process (their website/removal page). Be prepared to explain what changed (e.g., compromised page cleaned, sending reduced, list cleaned). Monitor for relisting Relisting is common if sending patterns or link usage return to the previous risk profile. For ongoing monitoring inside InboxAlly, use Domain Reports (in the InboxAlly app) to track domain reputation and authentication status over time. For a broader walkthrough of what to do when you’re listed (including prioritization and remediation steps), see Blocklist Impact and Remediation. --- ## How do I get removed from UCEPROTECT Level 1? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/uceprotectl1/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: UCEPROTECT Level 1 lists individual IPs for spam-like behavior. Fix the issue and delisting is automatic, typically within 7 days. - Keywords: UCEPROTECT Level 1, UCEPROTECT blocklist removal, how to get off UCEPROTECT, UCEPROTECT delisting, UCEPROTECT Level 1 blacklist > UCEPROTECT Level 1 lists individual sending IPs when it detects spam-like behavior or mail server misconfigurations. Fix the underlying issue and **delisting is automatic — typically within about 7 days**. If the problem isn't resolved, UCEPROTECT may escalate to Level 2 or 3, which covers broader IP ranges. UCEPROTECTL1 (dnsbl-1.uceprotect.net) is a DNS-based blocklist that can list individual sending IPs when it detects spam-like behavior or common mail server misconfigurations. In most cases, once you fix the underlying issue, delisting is automated and typically occurs within about 7 days. What is UCEPROTECTL1? UCEPROTECTL1 is the primary (Level 1) zone operated by UCEPROTECT Network. It lists specific IP addresses that appear to be sending unwanted email or are associated with risky email infrastructure. A Level 1 listing generally indicates an issue tied to a single IP (not an entire provider range). If the problem continues, UCEPROTECT may escalate to broader listings that cover larger IP ranges. Why is my IP listed on UCEPROTECTL1? UCEPROTECTL1 listings are commonly triggered by one or more of the following: Unsolicited Bulk Email (UBE) hitting spam traps (often due to poor list hygiene or sending to addresses that never opted in) Compromised accounts or devices sending unexpected volume (e.g., a hacked mailbox, infected website form, or malware on a server) Open relay or misconfigured mail server allowing unauthorized sending Reverse DNS (rDNS) / PTR issues (missing or incorrect rDNS can contribute to reputation and filtering problems) If spam activity does not stop, UCEPROTECT may escalate the listing beyond Level 1 to include broader IP ranges. To confirm whether your IP or domain is currently listed, use InboxAlly’s free Spam Database Lookup. How do I get removed from UCEPROTECTL1? UCEPROTECTL1 delisting is typically automatic once the underlying issue is resolved and the IP is no longer generating new triggers. Action steps to take first: Stop the source of unwanted mail Disable or secure any compromised mailbox(es) Rotate passwords and enable MFA where possible Check web forms/scripts that may be sending mail unexpectedly Fix mail server configuration Ensure your server is not an open relay Verify rDNS/PTR is correctly set for the sending IP Reduce risk going forward Confirm SPF, DKIM, and DMARC are correctly configured Ensure unsubscribe requests are honored promptly Avoid sending to unverified or purchased lists How long does it take? After spam stops and fixes are in place, delisting commonly occurs within about 7 days. Paid/expedited removal: UCEPROTECT may offer paid expedited options. If you choose to pursue that, make sure you still fix the root cause—otherwise the IP can be re-listed. For ongoing monitoring, use Domain Reports in the InboxAlly app to track authentication and reputation signals over time. How does a UCEPROTECTL1 listing affect deliverability? A UCEPROTECTL1 listing can cause: Blocks or rejections at providers that use this blocklist Spam-folder placement or increased filtering Delays (temporary deferrals) while receiving servers apply additional scrutiny Impact varies by recipient system. Some organizations and smaller providers rely heavily on third-party blocklists, while others weigh many signals (authentication, engagement, complaint rates, content, and sending patterns). If you’re seeing bounces or spam placement and suspect a listing, start with the Spam Database Lookup to confirm status, then remediate the sending and configuration issues above. For a broader, step-by-step approach to diagnosing and fixing blocklist-related deliverability problems, see Blocklist Impact and Remediation. --- ## How do I get removed from UCEPROTECT Level 2? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/uceprotectl2/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: UCEPROTECT Level 2 lists entire IP ranges when nearby Level 1 issues go unresolved. No manual delisting — removal is automatic in ~7 days. - Keywords: UCEPROTECT Level 2, UCEPROTECT Level 2 removal, UCEPROTECT IP range blacklist, UCEPROTECT Level 2 delisting, UCEPROTECT escalation > UCEPROTECT Level 2 lists **entire IP ranges** when unresolved Level 1 listings accumulate nearby — so you can be affected even if your specific IP wasn't the original source. There is **no manual delisting** — removal is automatic (typically ~7 days) once the underlying Level 1 issues across the range are resolved. If you’re listed on UCEPROTECTL2 (dnsbl-2.uceprotect.net), it usually means your IP is part of a larger network range that was escalated after unresolved UCEPROTECTL1 listings nearby. You can’t request a manual delisting—removal is typically automatic once the underlying issues across the range are fixed (often within ~7 days). What is the UCEPROTECTL2 blacklist? UCEPROTECTL2 is UCEPROTECT’s level 2 DNS-based blocklist zone. Unlike level 1 (which targets individual IPs), level 2 can list large IP ranges—sometimes tens of thousands of IPs—when UCEPROTECT detects ongoing or widespread abuse patterns within a subnet or provider network. In practice, this often affects: Hosting providers and ISPs Shared infrastructure (multiple senders on related IP space) Networks where abuse isn’t remediated quickly Why am I listed? UCEPROTECTL2 listings are most commonly triggered by: Escalation from UCEPROTECTL1 that remains unresolved for more than 7 days Multiple IPs in the same subnet showing spam-like behavior (e.g., high complaint rates, spam trap hits, or malware-driven sending) Misconfigurations or vulnerabilities such as: Open relay behavior Compromised accounts sending unsolicited mail Vulnerable web forms or mailing scripts generating unwanted email Because level 2 is range-based, you can be impacted even if your specific server isn’t the original source—your IP may be listed due to other problematic IPs “near” yours in the same provider range. How do I get removed from UCEPROTECTL2? There is no manual removal request process for UCEPROTECTL2. Delisting is handled automatically by UCEPROTECT once the underlying level 1 issues across the affected range are resolved. To improve your odds of being automatically delisted: Stop any suspicious or unwanted sending immediately Pause campaigns if you suspect compromise or list quality issues. Identify and isolate the source of abuse Check for compromised mailboxes, leaked credentials, or unexpected sending patterns. Review server logs for spikes, unknown scripts, or unauthorized access. Fix common server and application risks Ensure your server is not an open relay Patch or disable vulnerable mailing scripts and forms Rotate credentials and enforce strong authentication Clean up list hygiene Remove purchased, scraped, or unverified contacts Suppress chronic bounces, complainers, and non-engagers Work with your hosting provider or ISP Since UCEPROTECTL2 is often tied to provider IP ranges, your provider may need to: Remediate abuse elsewhere in the range Move you to a cleaner IP range (when appropriate) Confirm what actions they’re taking to address the escalation Monitor until the listing clears If no new issues occur, UCEPROTECTL2 delisting commonly completes within about 7 days after the related problems are resolved. To confirm whether you’re currently listed, use InboxAlly’s free Spam Database Lookup. For ongoing monitoring inside the app, use Domain Reports. How does this affect deliverability? A UCEPROTECTL2 listing can lead to: Higher spam-folder placement Temporary deferrals (messages delayed and retried) Rejections by some receiving systems that consult this blocklist Broader reputation damage if the same sending patterns continue Impact varies by recipient domain and mail system configuration—some providers weigh UCEPROTECT more heavily than others. Regardless, treat a level 2 listing as a signal to tighten security, sending practices, and list hygiene, and to coordinate with your provider if you’re on shared or ISP-managed IP space. For a broader walkthrough of what blocklists mean and how to recover, see Blocklist Impact and Remediation. --- ## How do I get removed from UCEPROTECT Level 3? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/uceprotectl3/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: UCEPROTECT Level 3 can list an entire ISP's IP range. Your IP may be caught even if clean — delisting is automatic once Level 1/2 issues clear. - Keywords: UCEPROTECT Level 3, UCEPROTECT Level 3 removal, UCEPROTECT ISP blacklist, UCEPROTECT Level 3 delisting, UCEPROTECT network range blocklist > UCEPROTECT Level 3 can list **broad IP ranges covering an entire ISP** when nearby IPs have unresolved Level 1 and 2 issues. Your IP may be listed even if it's not the source of the problem. Delisting is automatic once the underlying Level 1/2 listings are cleared — typically within about 7 days. UCEPROTECTL3 (dnsbl-3.uceprotect.net) is a third-level blocklist zone that can list broad IP ranges—sometimes covering an entire ISP—when nearby IPs have ongoing UCEPROTECTL1/2 issues that weren’t resolved. In most cases, delisting happens automatically after the underlying UCEPROTECTL1 and UCEPROTECTL2 listings are cleared (often within about 7 days). What is UCEPROTECTL3? UCEPROTECTL3 is the third-level DNS-based blocklist (DNSBL) operated by uceprotect.net. Unlike many blocklists that list a single IP, a level 3 listing can apply to a large range of IP addresses. Practically, this means you can be listed even if your specific sending IP isn’t the original source of the problem—because your IP falls within a range that has been escalated. Why am I listed? UCEPROTECTL3 listings typically happen due to escalation from lower-level listings: Escalation from UCEPROTECTL1 and UCEPROTECTL2 that continues beyond ~7 days Range-based escalation, where the listed scope may expand to cover a much larger portion of the network (potentially the entire ISP) In other words, UCEPROTECTL3 is usually a signal of unresolved issues on IPs “near” yours (within the same provider/network range), not necessarily a single-IP incident. To confirm whether your sending IP (or domain) is currently listed, use InboxAlly’s free Spam Database Lookup. How to get removed UCEPROTECTL3 delisting is generally automated. Removal typically occurs after: The underlying issues that triggered the UCEPROTECTL1 and UCEPROTECTL2 listings are corrected, and Those associated IPs are no longer flagged What to do on your side: Identify the sending IP(s) used by your ESP or mail server Check current listings with the Spam Database Lookup Remediate the root cause (common examples: high complaint rates, spam-like sending patterns, poor list hygiene, or compromised accounts) Wait for automated delisting, which commonly occurs within about 7 days after the related UCEPROTECTL1/2 listings clear For ongoing monitoring, use Domain Reports in the InboxAlly app to track reputation and authentication signals over time. For UCEPROTECTL’s own reference information, see UCEPROTECT’s website. How does this affect deliverability? A UCEPROTECTL3 listing can impact deliverability because some receiving systems consult DNSBLs during filtering decisions. Potential outcomes include: Increased spam folder placement Temporary deferrals (messages delayed) Rejections/blocks by stricter receivers Because UCEPROTECTL3 can be range-based, the impact can be inconsistent across mailbox providers—some may ignore it, while others may treat it as a strong negative signal. Next steps Re-check your IP/domain status with the Spam Database Lookup. For a broader remediation workflow and what to do when you’re listed, follow Blocklist Impact and Remediation. --- ## How do I get removed from the LashBack blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/lashback/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: LashBack flags IPs mailing suppression-list addresses. A listing means your unsubscribe process is broken — fix it, then request removal. - Keywords: LashBack blocklist removal, LashBack unsubscribe blacklist, how to get off LashBack, suppression list compliance, LashBack delisting request > LashBack's blocklist flags sending IPs that mail suppression-list addresses — meaning you're sending to people who previously unsubscribed. A listing is a strong signal that unsubscribe handling is broken somewhere in your sending flow. Fix your suppression process, verify your list against unsubscribe records, and request removal through LashBack. LashBack’s unsubscribe blocklist is a real-time list of IP addresses that appear to be sending mail to suppression-list addresses (i.e., addresses that should not be mailed because they previously unsubscribed). If your sending IP is listed, it’s a strong signal that unsubscribe/suppression handling is broken somewhere in your sending flow. What is LashBack’s unsubscribe blocklist? LashBack tracks IPs that send email to specially created, closely monitored email addresses (“unsubscribe probes”). These probe addresses are used only on suppression lists, so any mail sent to them suggests the sender is not honoring unsubscribe requests. Key characteristics commonly associated with this list: IP-based: Listings are tied to the sending IP address. High volume / frequently updated: The list is large (often cited as ~1M IPs) and updated regularly. Focused on compliance: It’s specifically about mailing suppressed/unsubscribed addresses, not general spam content. Why am I listed? The most common reasons an IP ends up on LashBack are operational issues that cause mail to continue after an unsubscribe. Examples include: Suppression list not applied to one or more campaigns, segments, or automations. Multiple systems sending (ESP + CRM + internal tool) where one system doesn’t share suppression status. Unsubscribe events not syncing across tools (delays, failed webhooks, API errors). List imports that overwrite or ignore suppression flags. Using old lists or reactivating contacts without preserving historical unsubscribes. What to check first: Confirm unsubscribes are being recorded correctly in your source of truth. Verify suppression is applied to every send path (broadcasts, automations, transactional where applicable). Audit any integrations or middleware that sync contacts and subscription status. How do I get removed from LashBack? LashBack typically allows manual delisting requests for an IP address, often free once every 30 days. The exact process can change, so follow the instructions on LashBack’s site for the current delisting procedure. Before requesting removal, make sure you’ve fixed the underlying cause—otherwise you may be re-listed quickly. At minimum: Stop sending to suppressed/unsubscribed addresses immediately. Ensure suppression is enforced across all sending systems and integrations. Re-verify your unsubscribe handling end-to-end (unsubscribe → stored → synced → excluded from sends). How does this affect deliverability? A LashBack listing can contribute to deliverability problems such as: More mail going to spam (reputation impact tied to the listed IP). Reduced inbox placement across major mailbox providers. Increased filtering or throttling if providers interpret the behavior as non-compliant sending. Because this list is about sending to suppression addresses, it can also be a sign of broader list hygiene and compliance issues that mailbox providers take seriously. Monitor and prevent future listings with InboxAlly Use the free Spam Database Lookup to check whether your IP or domain appears on major blocklists. For ongoing monitoring inside InboxAlly, use Domain Reports (available in the InboxAlly app) to track domain reputation and authentication status over time. Related guide: blocklist impact and remediation For a step-by-step approach to diagnosing impact and fixing listings, see Blocklist Impact and Remediation. --- ## How do I get removed from the PSBL blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/psbl/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: The PSBL flags IPs based on real-world spam reports. Listings often clear automatically once spam activity stops, or request manual removal. - Keywords: PSBL blocklist, Passive Spam Block List removal, how to get off PSBL, PSBL delisting, PSBL IP blacklist > The Passive Spam Block List (PSBL) flags sending IPs based on real-world spam reports from participating mail systems. It's a "passive" list — it doesn't scan for misconfigured servers, but aggregates observed spam activity. Listings often clear automatically once spam reports stop, or you can request manual delisting. A Passive Spam Block List (PSBL) is a DNS-based blocklist that flags sending IP addresses based on real-world spam observations (reports and complaints) from participating mail systems. Mail servers use PSBL lookups to decide whether to accept, reject, or filter incoming mail from those IPs. What is a Passive Spam Block List (PSBL)? A PSBL is a “passive” blacklist: it doesn’t actively scan the internet for misconfigured servers. Instead, it aggregates evidence of spam activity seen by real mail servers and publishes a list of IPs associated with that activity via DNS. Key characteristics: DNS-based: mail servers query it in real time during message acceptance. IP-focused: PSBLs typically list sending IP addresses (not domains). Evidence-driven: listings are based on observed spam, not theoretical risk. Why am I listed on a PSBL? Most PSBL listings happen because spam (or spam-like behavior) was observed coming from your sending IP. Common causes include: Compromised account or server sending unsolicited mail High complaint rates (recipients marking messages as spam) Poor list hygiene, leading to spam traps, invalid addresses, or high bounce rates Sudden volume spikes or unusual sending patterns Shared infrastructure issues (another sender on the same IP range behaving badly) Action step: confirm whether it’s your IP, your ESP/shared IP, or a newly assigned IP with prior history that’s listed. To check quickly, use InboxAlly’s free Spam Database Lookup (supports IP and domain checks). For ongoing monitoring inside InboxAlly, use Domain Reports. How do I get removed from a PSBL? Many PSBLs delist automatically after a quiet period (often 24–72 hours) once spam activity stops. If the PSBL supports manual delisting, it usually requires you to address the root cause first. Recommended remediation steps: Stop the source of spam Pause campaigns from the affected IP if needed. Reset credentials and secure any compromised accounts. Fix list quality Remove hard bounces, role accounts (where appropriate), and unengaged segments. Confirm opt-in practices and unsubscribe handling. Stabilize sending behavior Avoid sudden volume jumps. Resume gradually once complaints and bounces are under control. Request delisting (if available) Follow the PSBL’s delisting instructions (requirements vary by operator). Be prepared to confirm the issue is resolved. If you’re on a shared IP and can’t control other senders, the practical fix is often to move to a clean, dedicated sending IP (if your provider supports it) or work with your provider to remediate the shared pool. How does a PSBL affect deliverability? If your sending IP is listed, mailbox providers and receiving servers may: Reject mail outright (hard fail at SMTP time) Route messages to spam/junk Throttle or defer delivery, slowing down sends and reducing inbox placement Even when a specific receiver doesn’t use that PSBL directly, a listing can still correlate with broader reputation damage (complaints, bounces, negative engagement), which impacts deliverability across providers. How does a PSBL work? A PSBL compiles and publishes IP reputation signals based on observed spam activity: Data collection: participating systems record sender IPs associated with spam. Aggregation: repeated reports increase confidence that an IP is problematic. DNS publication: the list is exposed via DNS so mail servers can query it quickly. Real-time enforcement: receiving servers check the sender IP during delivery and apply local policy (reject, quarantine, spam folder, etc.). Frequent updates: listings can change quickly as new data arrives or activity stops. Related tools and next steps Check your status with Spam Database Lookup. Use Domain Reports (in the InboxAlly app) to monitor reputation and authentication signals over time. For a step-by-step remediation workflow, see Blocklist Impact and Remediation. --- ## How do I get removed from the Abuse.ro blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/abuse_ro/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: Abuse.ro is a Romanian DNSBL used for spam scoring. Check your listing status, fix the underlying issue, and request removal. - Keywords: Abuse.ro blocklist, Abuse.ro delisting, how to remove IP from Abuse.ro, Romanian DNSBL, Abuse.ro blacklist removal > Abuse.ro is a Romanian DNSBL that flags IPs and domains associated with spam. While it doesn't block email directly, some mail systems use it for scoring. Check your status with InboxAlly's free Spam Database Lookup, fix the underlying spam issue, and request removal through their delisting process. Abuse.ro is a Romanian reputation blacklist (DNSBL/RBL) that flags IPs and domains associated with spam. While it doesn’t block email by itself, some mail systems use it to filter or score messages—so a listing can reduce deliverability. To quickly check whether your IP or domain appears on major blocklists (including Abuse.ro when available), use InboxAlly’s free Spam Database Lookup. For ongoing monitoring, use Domain Reports in the InboxAlly app. What is Abuse.ro? Abuse.ro is a real-time reputation and classification database that lists IP addresses and domains suspected of sending spam. Mail server operators can query it via DNS to help decide whether to accept, reject, or route messages to spam. Important: Abuse.ro provides reputation data; each receiving mail server decides how (or whether) to use it. How do I check if I’m on the Abuse.ro blacklist? You can check an IP listing by querying Abuse.ro’s DNSBL. 1) Find your sending IP address If you’re not sure, search “What is my IP” in Google (this shows your public IP). For email sending, you may need the outbound mail server IP from your ESP or mail server logs (often different from your office/home IP). 2) Reverse the IP address Example: if your IP is 10.11.12.13, reverse it to 13.12.11.10. 3) Run a DNS query Windows (nslookup) Open Command Prompt Run: nslookup 13.12.11.10.rbl.abuse.ro Mac/Linux (dig) Open Terminal Run: dig 13.12.11.10.rbl.abuse.ro 4) Interpret the result Listed: you may see an address like 127.0.0.2 or 127.0.0.3 Not listed: you’ll typically see NXDOMAIN / “Non-existent domain” For a faster scan across many common blocklists, use the free Spam Database Lookup. Why am I listed on Abuse.ro? Most listings happen when Abuse.ro detects or receives signals consistent with spam, such as: High complaint rates or repeated spam reports Spam trap hits (emails sent to addresses used to identify unsolicited mail) Compromised servers or accounts sending unauthorized mail Poor list hygiene (old, purchased, or unverified lists) Misconfigured infrastructure (e.g., open relay or insecure scripts) If you believe the listing is an error, you can still request a review—but you’ll usually need to show that the underlying sending issue is resolved. How do I get removed from the Abuse.ro blacklist? Abuse.ro delisting is typically a manual process. Do this in order: Confirm the listing Re-check using the DNS query steps above (or validate via the Spam Database Lookup). Stop the unwanted mail at the source Secure compromised accounts Patch infected systems Remove or fix any scripts/forms that can be abused Pause sending to questionable segments until list quality is addressed Verify you control the IP/domain Abuse.ro may expect the request to come from an appropriate administrative contact (often a postmaster-style address). Request review/delisting Email admin@abuse.ro from your postmaster address (or another clearly authoritative admin address). Include: The listed IP(s) and/or domain(s) What caused the issue (if known) What you changed to prevent recurrence Evidence that spam has stopped (timestamps, logs, remediation summary) They will typically verify the situation before removing the listing. How does an Abuse.ro listing affect deliverability? An Abuse.ro listing doesn’t automatically block your mail everywhere, but it can: Increase spam scoring on systems that consult Abuse.ro Contribute to throttling, deferrals, or filtering Reduce inbox placement—especially if combined with other negative signals (complaints, bounces, authentication gaps) To monitor risk over time: Run periodic checks with the free Spam Database Lookup Use Domain Reports in the InboxAlly app to track domain reputation and authentication signals What is a DNSBL/RBL? A DNSBL (Domain Name System Blacklist) or RBL (Realtime Blackhole List) is a database of IPs/domains associated with spam or abuse. Mail servers query these lists (via DNS) and use the results as one input in their filtering decisions. Next steps: blocklist remediation workflow For a step-by-step process to diagnose impact and recover deliverability, see Blocklist Impact and Remediation. --- ## How do I get removed from the Spam Eating Monkey blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/spam-eating-monkey/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: SEM publishes multiple DNS blocklists for IPs, domains, and URLs. Fix spam traps or backscatter issues — many SEM listings expire automatically. - Keywords: Spam Eating Monkey blocklist, SEM blacklist removal, SEM DNSBL delisting, Spam Eating Monkey removal, SEM backscatter blocklist > Spam Eating Monkey (SEM) publishes multiple DNS-based blocklists that flag IPs, domains, and URLs associated with spam-trap activity, backscatter, or newly registered domains. Fix the underlying issue (list hygiene, authentication, or compromised infrastructure), then check the SEM lookup tool for delisting options — many SEM listings expire automatically. Spam Eating Monkey (SEM) blocklists are DNS-based lists (DNSBL/URIBL) used by some mail systems to flag sending IPs, domains, or URLs associated with spam-trap activity, backscatter, or very newly registered domains. If your IP or domain is listed, your email may be rejected or routed to spam by systems that consult SEM. What is the Spam Eating Monkey (SEM) blocklist? Spam Eating Monkey publishes multiple blocklists that identify different types of risk signals: IP-based DNSBLs (IPv4/IPv6): List sending IPs observed sending to spam traps or generating backscatter. Domain/URI-based URIBLs: List domains or URLs found in spam-trap messages. “Fresh” domain lists: List newly registered domains for a short period (often used as a risk heuristic). SEM blocklists you may see referenced SEM-BACKSCATTER: IPs sending backscatter (typically bounces/auto-replies) with a NULL sender to spam traps. Auto-expires after ~15 days of inactivity. SEM-BLACK: IPs sending mail to spam traps. Auto-expires after ~15 days of inactivity. SEM-IPV6BL: IPv6 addresses sending mail to spam traps. Auto-expires after ~15 days of inactivity. SEM-FRESHZERO: Domains registered in the last 24 hours. Auto-expires after ~24 hours. SEM-FRESH / SEM-FRESH10 / SEM-FRESH15 / SEM-FRESH30: Newly registered domains by age threshold (about 5/10/15/30 days). Auto-expires after the same period. SEM-NETBLACK: Networks with low reputation. Does not expire automatically. SEM-URI: Domains/URIs found in spam-trap emails. Auto-expires after ~30 days of inactivity. Why am I listed on a Spam Eating Monkey blocklist? Common reasons include: Spam-trap hits: Your IP sent mail that reached SEM spam traps (often due to poor list hygiene, purchased lists, or old/unengaged lists). Backscatter behavior: Your server generated non-delivery reports/auto-replies to forged senders (misconfigured bounce handling can contribute). Newly registered domain: Your domain is legitimately new and appears on SEM-FRESH* lists temporarily. Low network reputation: Your IP range/network is flagged on SEM-NETBLACK, which typically indicates broader reputation issues beyond a single message. To confirm whether you’re listed (and where), run a check with InboxAlly’s free Spam Database Lookup. How do I get removed from SEM blocklists? In many cases, SEM listings expire automatically once the triggering behavior stops: SEM-BLACK / SEM-IPV6BL / SEM-BACKSCATTER: typically drop off after ~15 days of inactivity. SEM-URI: typically drops off after ~30 days of inactivity. SEM-FRESH* lists: drop off after the defined “fresh” window (24 hours to 30 days). SEM-NETBLACK: may not expire automatically; remediation usually requires sustained reputation improvement. Action steps that help removal happen faster (and prevent re-listing): Stop sending to bad addresses Remove hard bounces and unknown users immediately. Avoid sending to old/unengaged segments until you’ve cleaned the list. Fix backscatter (if applicable) Ensure your mail server rejects invalid recipients during the SMTP transaction (instead of accepting then bouncing later). Review auto-reply/bounce configurations so you’re not generating responses to forged senders. Reduce risky content and links If you’re listed on SEM-URI, audit the domains/URLs in your messages (including redirects and tracking links). Monitor after changes Re-check periodically using Spam Database Lookup. For ongoing monitoring, use Domain Reports in the InboxAlly app to track domain reputation and authentication status over time. How does an SEM listing affect deliverability? Impact depends on whether the receiving system uses SEM and how it’s configured: Hard blocks (rejections): Some servers may reject mail outright when an IP/domain is listed. Spam folder placement: Others may accept the message but route it to spam. Reputation spillover: Repeated listings can contribute to broader sender reputation issues, especially if the underlying cause (spam traps, backscatter, poor list hygiene) isn’t fixed. If you’re troubleshooting a sudden drop in inbox placement, confirm listings with Spam Database Lookup and then track improvements over time in Domain Reports (InboxAlly app). Next steps: blocklist remediation workflow For a step-by-step process (diagnosis, fixes, and prevention), follow Blocklist Impact and Remediation. --- ## How do I get removed from the SEM Fresh blocklist? - URL: https://www.inboxally.com/docs/troubleshooting-recovery/blocklists/semfresh-blacklist/ - Section: Blocklists - Last Modified: 2026-03-10 - Description: SEM Fresh targets newly registered domains and recent spam activity. Listings expire automatically — no manual delisting process exists. - Keywords: SEM Fresh blocklist, SEM Fresh blacklist removal, new domain blocklist, Spam Eating Monkey Fresh, newly registered domain email blocked > SEM Fresh flags newly registered domains and recent spam-like activity. Unlike reputation-based lists, it focuses on **recency signals** — so even clean new domains can be listed temporarily. Listings typically expire automatically once the triggering period passes and the spam-like activity stops. There is no manual delisting process. SEM Fresh (by Spam Eating Monkey) is a real-time blocklist family that flags newly registered domains and recent spam-like activity. If your domain or IP is listed, some mail servers may temporarily delay, reject, or route your email to spam until the listing expires and the triggering activity stops. What is SEM Fresh? SEM Fresh is a set of automated, time-based blocklists operated by Spam Eating Monkey. Unlike reputation systems that track long-term sending behavior, SEM Fresh focuses on recent signals, such as: Newly registered domains (common in short-lived spam campaigns) IPs/domains observed sending to spam traps Backscatter behavior (misconfigured servers generating non-delivery messages to forged senders) Most SEM Fresh-style listings are designed to expire automatically after a defined period—often quickly—once the triggering behavior stops. To confirm whether you’re listed, run a check with InboxAlly’s free Spam Database Lookup. Why am I listed on SEM Fresh? Common reasons include: Your domain is newly registered (and falls into a “fresh domain” window like 0/5/10/15/30 days). A compromised mailbox, API key, or script sent unexpected mail. Your server hit a spam trap (often caused by poor list hygiene or purchased/old lists). Backscatter: your mail server sent bounce messages with a null sender (MAIL FROM: <>) to addresses that didn’t originate the mail. Shared infrastructure issues: another sender on the same shared IP/network triggered the listing. SEM Fresh is heavily weighted toward recency—a sudden change in volume, targeting, or domain age can be enough to trigger it. How do I get removed from SEM Fresh? SEM Fresh generally does not offer manual delisting. Removal happens automatically after the list’s expiration rules are satisfied and the triggering activity stops. Do this immediately: Verify the listing Use Spam Database Lookup to see which SEM list you’re on (and whether it’s your domain, IP, or both). Stop the behavior that triggered the listing Pause bulk or automated sending temporarily. Check for compromise: review recent logins, API usage, SMTP activity, and any web forms/scripts that can send mail. Review recent campaigns for sudden volume spikes, new lists, or new sending patterns. Reduce future trap/complaint risk Tighten list hygiene (remove old/unengaged addresses; avoid questionable sources). Monitor spam complaints and unsubscribe behavior closely. Wait for automatic expiration Once sending is clean, most SEM Fresh-related entries clear on their own based on the list’s timer. For ongoing monitoring inside InboxAlly, use Domain Reports to track domain reputation and related signals over time. SEM blocklists and typical expiration rules Blocklist What it lists Expiration / removal rules SEM-FRESHZERO Newly registered domains (typically registered in the last 24 hours) Automatically removed after 24 hours SEM-FRESH Domains registered in the last 5 days Automatically removed after 5 days SEM-FRESH10 Domains first registered in the last 10 days Automatically removed after 10 days SEM-FRESH15 Domains first registered in the last 15 days Automatically removed after 15 days SEM-FRESH30 Domains first registered in the last 30 days Automatically removed after 30 days SEM-BACKSCATTER IPs sending mail to a spam trap with a NULL sender (MAIL FROM: <>) Removed after 15 days without further backscatter activity SEM-BLACK IPs sending mail to a spam trap Removed after 15 days without further spam activity SEM-IPV6BL IPv6 addresses sending mail to a spam trap Removed after 15 days without further spam activity SEM-NETBLACK Networks identified as having persistently low reputation Entries do not expire automatically SEM-URI Domains and URIs detected in the body of email sent to a spam trap Removed after 30 days without being seen again Note: SEM Fresh is operated by Spam Eating Monkey. You can read more on their public site: https://spameatingmonkey.com/ How does SEM Fresh affect deliverability? If you’re listed, impacts are usually immediate but temporary, such as: Deferrals (temporary delays) while the receiving server evaluates risk Rejections (bounces) from servers that enforce SEM lists strictly Spam folder placement due to elevated risk signals Because SEM Fresh is time-based, deliverability often improves soon after: the triggering activity stops, and the listing expires. If deliverability problems continue after expiration, it usually indicates an underlying issue (compromise, list quality, authentication gaps, or ongoing complaint rates) that needs remediation. Frequently Asked Questions I received an error mentioning spameatingmonkey.net. What does it mean? It typically means the receiving server checked Spam Eating Monkey data and found your domain or sending IP listed on one of their blocklists (including SEM Fresh variants). How long does a listing last? It depends on the specific list: “Fresh domain” lists expire in 1–30 days based on domain age windows. Trap/backscatter lists commonly require ~15–30 days without repeat activity. Some entries (like SEM-NETBLACK) may not expire automatically. Can I request removal? In most cases, no—SEM Fresh-style lists are automated and clear based on time and observed behavior. For a broader walkthrough of what to fix and how to recover, see Blocklist Impact and Remediation. --- ## What is the difference between email reputation repair and warm-up? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/email-reputation-repair-vs-email-warm-up/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-13 - Description: Reputation repair fixes a damaged sender identity; warm-up builds trust for a new one. Pick the right process based on your sending history. - Keywords: email reputation repair, email warm up vs reputation repair, how to fix email sender reputation, rebuild email domain reputation, sender reputation recovery > **Reputation repair** fixes an existing sender identity that is underperforming — spam placement, blocks, or high bounces — by addressing root causes like list quality, authentication, and complaint rates. **Warm-up** builds trust for a new domain, IP, or address that has little or no sending history by gradually increasing volume while generating positive engagement signals. Email reputation repair and email warm-up both improve deliverability, but they solve different problems. Use reputation repair when an existing sender identity is already underperforming (spam placement, blocks, high bounces). Use warm-up when you’re building trust for a new domain, address, or IP with little/no sending history. Positive engagement signals strengthen sender reputation while complaints and bounces weaken it. 1. Positive signals evaluated: opens, reads, replies, forwards, spam folder rescues, consistent sending patterns, and clean list hygiene with low bounce rates. 2. Negative signals evaluated: spam reports, hard bounces, spam trap hits, blocklist appearances, and consistently low engagement rates. 3. Positive and negative signals weighed against each other to produce cumulative sender reputation score. 4. Reputation score influences inbox, promotions, or spam placement. 5. After delivery, opens, replies, and rescues strengthen reputation while spam complaints weaken it — continuous feedback cycle. What is email reputation repair? Email reputation repair is the process of recovering inbox placement after a sender’s reputation has been damaged. It focuses on fixing the underlying causes (list quality, engagement, authentication, complaint rates) and rebuilding trust with mailbox providers. If you need the full step-by-step process, see: How to Repair Email Sender Reputation After Deliverability Issues. To diagnose whether you have a reputation problem, InboxAlly’s Placement Tester and Email Audit can show where your emails land (inbox vs. spam) and what’s likely driving the issue. Domain Reports can also help you monitor authentication and reputation signals over time. What is email warm-up? Email warm-up is a controlled ramp-up of sending volume for a new email identity (domain, subdomain, address, or IP). You start with low volume and strong engagement signals, then gradually increase sending so mailbox providers learn your mail is wanted. For a week-by-week schedule, see: Email Warm-Up Timeline: Week-by-Week Schedule. InboxAlly warm-up is supported by its seed email network, which generates positive engagement signals (opens, clicks, moves to inbox) to help train mailbox providers during the ramp-up. How to tell which you need Use the checklist below to decide quickly. If multiple items apply, prioritize the section with the strongest signals (for example: blocklisting and provider blocks almost always mean repair). Signal You likely need reputation repair You likely need warm-up Sender history You’ve been sending for weeks/months/years and performance dropped You have no or very limited sending history Inbox placement Messages suddenly (or consistently) land in spam/junk Messages are inconsistent early on, especially at low volume Bounce rates High hard bounces or repeated “user unknown”/invalid address bounces Low bounces, but you’re keeping volume intentionally small Blocks & errors Provider blocks (e.g., “blocked,” “rejected,” “policy reasons”), throttling, or repeated deferrals No blocks—just cautious sending to establish trust Blocklists Your domain/IP appears on a blocklist Not blocklisted (or you haven’t checked yet) List quality Older list, purchased/scraped contacts, low engagement, many inactive recipients Fresh, permission-based list you haven’t mailed much yet Authentication SPF/DKIM/DMARC missing or misaligned, or recently changed Authentication is set up correctly before scaling Practical “if this, then that” If you’re seeing spam placement + high bounces + blocks, start with reputation repair. If you’re launching a new domain/subdomain/address (or moving to a new sending IP), start with warm-up. If you’re unsure, run InboxAlly’s Placement Tester and Email Audit, then review Domain Reports to confirm authentication and reputation status. You can also use the free Spam Database Lookup to check for common blocklists. Not sure which approach you need? Open the IA Assistant in the InboxAlly app — it can assess your current deliverability situation and recommend next steps. Can you need both? Yes. A common scenario is a sender with a damaged reputation who decides to start fresh with a new domain or subdomain. In that case: You may do reputation repair on the old sender identity (to stop ongoing damage and improve deliverability where possible), and You’ll still need warm-up on the new identity because it has little/no sending history. For a structured volume plan when increasing sends, follow: Email Ramp-Up Schedule. Ready to improve inbox placement? Start a free InboxAlly trial. --- ## How do I ramp up email sending volume safely? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/email-ramp-up-schedule/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-10 - Description: Day-by-day volume targets for ramping up email sends — when to double, when to hold, and how InboxAlly seeds accelerate the timeline. - Keywords: email ramp up schedule, email sending volume increase plan, how to ramp up email sends, email warm up daily volume, IP warm up schedule, email volume ramp up best practices > Start with a small volume (around 50 emails) and roughly double your daily sends as long as inbox placement trends positively. If placement drops, hold at the previous day's volume until metrics recover. Using InboxAlly seed emails during ramp-up generates engagement signals that let you scale faster than a traditional warm-up. An email ramp-up schedule is a day-by-day plan for gradually increasing your sending volume so mailbox providers can build trust in your domain and IP. You start with a small number of sends (typically around 50), roughly double each day as long as inbox placement trends positively, and hold volume steady whenever metrics dip. Using InboxAlly seed emails during ramp-up generates engagement signals that let you scale faster than a traditional warm-up. For the broader warm-up strategy — including what to send, who to target, and how to monitor progress week by week — see Email Warm-Up Timeline: Week-by-Week Schedule. The volume of emails are increased (usually doubled) each day so long as the inbox placement continues to trend positively. If placement begins to decline, best practice is to maintain your previous day’s volume so long as your delivery metrics are under-performing. For example, if you expect to send 10,000 emails in a day, start with the initial 50 emails on your first day and increase volume day-over-day until you reach your desired volume. The engagement boost from your InboxAlly seeds will allow you to ramp up faster and more successfully than a traditional ramp up. How to use Seed Emails to ramp up sending on a domain or IP? We will provide some examples for ramping up different volumes of emails. When using seed emails, you have two options: Use a two-stage ramp up (recommended) Use a hybrid only ramp up Volume should only increase when engagement metrics hold steady — if engagement drops, hold or reduce volume. 1. Seed phase (weeks 1-2): begin at 2-5% of target volume with most engaged subscribers, target >30% open rate to establish baseline trust. 2. Establish phase (weeks 2-3): increase to 10-20% of target volume with broader engaged segments, maintain >25% open rate. 3. Scale phase (weeks 4-5): increase to 35-75% of target volume with full list segments, maintain >20% open rate. 4. Full volume (week 6+): reach 100% of target volume, monitor continuously — if metrics drop, reduce and investigate. 5. Ongoing monitoring: volume changes, new domains, and ESP migrations all require re-warming. Two Stage ramp up of a new IP or Domain If you are not already sending, we suggest a two-stage ramp up with 100% synthetic traffic for the first week and then mixing-in your real traffic the second week. Create an email, or several variants, as well as subject lines that will be used during the ramp up cycle. Run these emails through a spam tester to ensure that the content of the email does not accidentally raise any concerns with spam filters. Send the scheduled amount of seed emails for that day. If you have the capability through your sending platform, throttle the sending and send during the typical daytime hours of the majority of your recipients. Each day, monitor the inbox placement in the InboxAlly platform and ensure the trend shows an inboxing improvement. If inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick. Depending on your prior IP reputation, it is not uncommon that you may need to hold your volume constant at some occasions on the schedule. If there is a positive trend in deliverability, progress to the next step of the schedule. Continue progressing with the send target each day until you are sending using all of your seed emails. For example, if you have 1,000 seeds on a Premium Plan, once you reach the day where you send 1,000 seed emails out, each day thereafter you will continue at that same level of 1,000 seed emails. Begin mixing in your real emails over the next 7 days until you reach the desired final volume. To ensure the best inboxing on an ongoing basis, continue sending your full volume daily along with the seed emails. We usually recommend that the seed emails make up at least 5% of your total volume (with a minimum of 50 seed emails per ESP per sender). However with some experimentation, you might be able to get by with less. Only double send volume when inbox placement shows day-over-day improvement Example ramp up schedules (two-stage approach) How many emails do you want to send per month? Sending 100,000 emails/month requires scaling to 4,000 emails/day. The recommended number of seeds and starting sends is as follows. Seeds Recommended Seed Ratio Day 1 Volume 200 5% 20 Send to your seed emails only for the first 6 days using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Synthetic Sending (Seeds Emails only) Day Number 1 2 3 4 5 6 Send Volume 20 40 80 150 175 200 Begin mixing in your real emails with your seed emails using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Hybrid Sending (Seeds + Real Emails) Day Number 7 8 9 10 11 12 13 Send Volume 300 400 600 1000 1800 3400 4200 Seed Emails 200 200 200 200 200 200 200 Real Emails 100 200 400 800 1600 3200 4000 Sending 500,000 emails/month requires scaling to 20,000 emails/day. The recommended number of seeds and starting sends is as follows. Seeds Recommended Seed Ratio Day 1 Volume 1000 5% 50 Send to your seed emails only for the first 6 days using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Synthetic Sending (Seeds Emails only) Day Number 1 2 3 4 5 6 Send Volume 50 100 200 400 800 1000 Begin mixing in your real emails with your seed emails using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Hybrid Sending (Seeds + Real Emails) Day Number 7 8 9 10 11 12 13 Send Volume 1500 2000 3000 5000 9000 17000 21000 Seed Emails 1000 1000 1000 1000 1000 1000 1000 Real Emails 500 1000 2000 4000 8000 16000 20000 Sending 1,000,000 emails/month requires scaling to 40,000 emails/day. The recommended number of seeds and starting sends is as follows. Seeds Recommended Seed Ratio Day 1 Volume 2000 5% 100 Send to your seed emails only for the first 6 days using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Synthetic Sending (Seeds Emails only) Day Number 1 2 3 4 5 6 Send Volume 100 200 400 800 1600 2000 Begin mixing in your real emails with your seed emails using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Hybrid Sending (Seeds + Real Emails) Day Number 7 8 9 10 11 12 13 Send Volume 3000 4000 6000 10000 18000 32000 42000 Seed Emails 2000 2000 2000 2000 2000 2000 2000 Real Emails 1000 2000 4000 8000 16000 32000 40000 Sending 5,000,000 emails/month requires scaling to 200,000 emails/day. The recommended number of seeds and starting sends is as follows. Seeds Recommended Seed Ratio Day 1 Volume 10,000 5% 250 Send to your seed emails only for the first 6 days using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Synthetic Sending (Seeds Emails only) Day Number 1 2 3 4 5 6 7 Send Volume 250 500 1000 2000 4000 8000 10000 Begin mixing in your real emails with your seed emails using the following schedule. Monitor inbox placement and if inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick and then continue with the schedule. Hybrid Sending (Seeds + Real Emails) Day Number 8 9 10 11 12 13 14 15 Send Volume 11000 12000 3000 5000 9000 17000 21000 210000 Seed Emails 10000 10000 10000 10000 10000 10000 10000 10000 Real Emails 1500 3000 6000 12000 24000 48000 96000 200000 Pro Tip Each day, 6 hours before you wish to send to your real emails, send to the seed emails first using the same subject, body text and from email that you will send to your real emails. Hybrid ramp up of a new IP or Domain If you are organically growing your traffic or unable to dedicate the time for a two stage ramp up, you can mix-in the seeds to ramp up your IP or domain while sending your real email volume. Simply estimate the final daily send volume and ensure that you have enough seeds to cover 5% of that volume. During the first week of ramp up, scale to 100% seed usage. By the end of the second week of ramp up, you should be able to scale to your full volume. Create an email, or several variants, as well as subject lines that will be used during the ramp up cycle. Run these emails through a spam tester to ensure that the content of the email does not accidentally raise any concerns with spam filters. Send the scheduled amount of seed emails for that day. If you have the capability through your sending platform, throttle the sending and send during the typical daytime hours of the majority of your recipients. Each day, monitor the inbox placement in the InboxAlly platform and ensure the trend shows an inboxing improvement. If inboxing declines for a given day or does not clearly show an improvement, maintain current send volume for the subsequent day(s) until the placement shows an uptick. You may also consider holding your real email volume constant and only scaling the seed emails until inboxing shows an improvement. Depending on your prior IP reputation, it is not uncommon that you may need to hold your volume constant at some occasions on the schedule. When there is a positive trend in deliverability, progress to the next step of the schedule. Continue progressing with the send target each day until you are sending using all of your seed emails. For example, if you have our Premium Plan, which gives you 1,000 seeds, once you reach the day when you send 1,000 seed emails out, each day thereafter you will continue at that same level of 1,000 seed emails while adding to and increasing your real email send volume. To ensure the best inboxing on an ongoing basis, continue sending your full volume daily along with the seed emails. We usually recommend that the seed emails make up 5% of your total volume (with a minimum of 50 seed emails per ESP per sender). However with some experimentation, you might be able to get by with less. Example ramp up schedule for 200,000 daily emails (hybrid approach) Day Number Seed Email % Seed Emails Real Emails 1 2% 200 50 2 4% 400 100 3 6% 600 500 4 12% 1200 1000 5 25% 2500 2000 6 50% 5000 4000 7 100% 10000 8000 8 100% 10000 15000 9 100% 10000 25000 10 100% 10000 35000 11 100% 10000 50000 12 100% 10000 75000 13 100% 10000 100000 14 100% 10000 150000 15 100% 10000 200000 What to do if your ramp up does not scale By following the example schedules above, you should be able to scale your daily sends to the volume you need. There are many factors in email deliverability and sometimes things do not always go as planned. If you have any challenges in maintaining the level of inboxing you desire, we recommend speaking to one of our deliverability experts for specific help in achieving your inboxing goals. Please reach out to us to schedule some time for a call. Some of the daily KPIs that we will ask for are the following: Number of emails sent Open rate Spam complaints Click through rates If you want to learn more in-depth about email deliverability best practices, check out our other blog post. --- ## How long does it take to warm up an email domain? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/how-long-does-it-take-to-warm-up-a-domain/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-10 - Description: Plan for 6–8 weeks of gradual volume increases, engagement monitoring, and complaint control — with week-by-week targets for a new domain. - Keywords: how long to warm up email domain, email warm up timeline, domain warm up schedule, email warmup period, new domain warm up weeks, email warm up best practices > Most senders should plan for a **6–8 week warm-up period**, sometimes longer for brand-new domains. The goal is to gradually ramp sending volume while keeping engagement high and complaints low — proving to mailbox providers that real people want your emails. InboxAlly can accelerate this timeline by generating positive engagement signals from day one. Most senders should plan for a 6–8 week email warm up timeline—and sometimes longer when you’re trying to warm up a new domain (especially if it’s brand-new). The goal isn’t to reach full volume fast; it’s to build a steady sender reputation by ramping up gradually while keeping engagement high and complaints/bounces low. If you’re starting fresh, set expectations early: mailbox providers treat unknown senders as risky until they see consistent, positive signals over time. That means your domain warm up period is essentially a proof phase—showing that real people open, read, and interact with your emails, and that you’re not generating spam complaints, hard bounces, or sudden volume spikes. Push too hard too soon, and you’ll often see throttling, spam placement, or blocks that slow you down more than a patient ramp-up would. In this guide, you’ll get a practical, week-by-week email warmup schedule that answers how long to warm up email, including: Volume targets by week (when to increase—and when to pause) What to send during warm-up to drive safe engagement What to watch (opens, replies, bounces, complaints, spam placement) How InboxAlly can accelerate warm-up by generating engagement signals from day one, plus links to the Email Ramp Up Schedule and How Long Does It Take to Warm Up a Domain resources for deeper detail Why warm-up matters (and what happens if you skip it) Email providers don’t treat a new sender as “neutral”—they treat you as unknown. During the first days and weeks, your sending behavior becomes the baseline for how inboxes judge you going forward. Sender reputation basics (what’s being “warmed up”) Reputation is tracked at multiple levels, and each can start with little or no trust: Domain reputation: Your root domain (e.g., example.com) earns trust based on consistent, low-risk sending. Subdomain reputation: A new subdomain (e.g., mail.example.com) is often evaluated separately; it may need its own domain warm up period. IP reputation: If you’re on a dedicated IP, that IP starts “cold.” Even on shared infrastructure, your sending patterns still matter. Mailbox-level history: Individual “From” addresses and inboxes can develop their own reputation signals over time. ISPs use early signals—volume, bounce rates, complaints, and engagement—to decide whether you’re a legitimate sender or a potential spammer. That’s why an email warm up timeline is essentially a controlled trust-building process. What happens if you skip warm-up and blast your full list Sending at full volume from a cold domain/IP commonly triggers: Throttling and deferrals: Providers slow delivery, return temporary errors, or queue mail for hours/days. Spam placement: Even “delivered” messages land in Promotions/Spam, reducing engagement and reinforcing negative signals. Blocks: You may see provider-specific rejections that halt sending entirely. Reputation damage: A bad first impression can take weeks or months to reverse—especially if you keep pushing volume. InboxAlly helps accelerate warm-up by generating positive engagement signals early, so you build reputation while you ramp. Core metrics to track throughout the schedule Anchor every week of your email warmup schedule to these signals: Hard bounces (invalid addresses): keep as close to 0% as possible. Spam complaints: any spike is a “slow down now” alert. Opens/clicks/replies: engagement validates legitimacy (InboxAlly is designed to improve these signals). Inbox vs. spam placement: track per provider, not just “delivered.” Provider throttling signals: deferrals, temp failures, and delayed delivery patterns (especially at Gmail, Outlook, Yahoo). Before you start: domain age, authentication, and list hygiene (your warm-up foundation) A successful email warm up timeline starts before you send your first campaign. ISPs judge unknown senders aggressively, so your goal is to look stable, authenticated, and wanted. Domain age: plan for extra scrutiny If you’re trying to warm up a new domain, domain age matters. Brand-new domains (typically <30 days old) often face tighter filtering and throttling because they have no history. Recommended domain warm up period approach: Best practice: register/configure the domain, then let it age 2–4 weeks before meaningful sending. If you must send while aging: keep volumes extremely low, send only to your most engaged recipients, and avoid sudden spikes. For more detail, see Impact of Domain Age on Email Deliverability and How Long Does It Take to Warm Up a Domain. Baseline setup checklist (don’t skip this) Before following any email warmup schedule, confirm your identity and keep it consistent: SPF: authorizes your sending sources DKIM: cryptographically signs mail from your domain DMARC: enforces policy and reporting; ensure alignment with your From domain Use a consistent From name and From address (and reply-to) throughout ramp-up Avoid frequent changes to: sending domain/subdomain From identity templates and link domains sending patterns (big day-to-day swings) InboxAlly’s Quick Start Guide and setup wizard help you validate these essentials quickly, so your warm-up signals aren’t undermined by missing authentication. List hygiene and targeting: start with “most engaged” Warm-up is not the time to “test the whole list.” Start with recipients most likely to open and reply, then expand gradually. Do this first: Verify your list and remove risky segments: old addresses (stale data) purchased/third-party lists role accounts if they historically underperform (e.g., info@) long-term unengaged contacts Define “engaged” for your business, such as: opened or clicked in the last 30–60 days replied or booked a meeting in the last 90 days opted in recently (fresh sign-ups) To accelerate positive engagement signals from day one, consider InboxAlly’s Email Warm Up Service and learn the mechanics in How Does InboxAlly Work. Volume should only increase when engagement metrics hold steady — if engagement drops, hold or reduce volume. 1. Seed phase (weeks 1-2): begin at 2-5% of target volume with most engaged subscribers, target >30% open rate to establish baseline trust. 2. Establish phase (weeks 2-3): increase to 10-20% of target volume with broader engaged segments, maintain >25% open rate. 3. Scale phase (weeks 4-5): increase to 35-75% of target volume with full list segments, maintain >20% open rate. 4. Full volume (week 6+): reach 100% of target volume, monitor continuously — if metrics drop, reduce and investigate. 5. Ongoing monitoring: volume changes, new domains, and ESP migrations all require re-warming. Email warm up timeline: week-by-week schedule (with what to send each week) This email warm up timeline is designed for new or “cold” senders who need to rebuild trust with mailbox providers. The goal is to increase volume while generating strong engagement signals (opens, replies, clicks, saves) and keeping negative signals (bounces, complaints, spam placement) near zero. If you’re using InboxAlly, follow the same volume targets—InboxAlly simply helps you earn positive engagement faster and more consistently (see How Does InboxAlly Work and the Email Warm Up Service). Tip: If your domain is brand new, consider letting it age before heavy sending. The Impact of Domain Age on Email Deliverability and How Long Does It Take to Warm Up a Domain explain why the first 30 days can be extra sensitive. Week 1–2 (10–50 emails/day): “Prove you’re wanted” Who to send to Your most engaged recipients only (recent openers/clickers/repliers). People who have explicitly requested your emails (new signups, customers, active users). Avoid cold lists, purchased lists, and “maybe interested” segments. What to send Simple, human emails that look like 1:1 communication: Short updates, helpful tips, quick check-ins, onboarding guidance. Plain-text or light formatting; minimal images and links. High-open-rate content you already know performs well: “Here’s the resource you asked for” “Quick question about your [goal]” “Following up on [topic]—want the checklist?” How to write it Keep copy tight: 50–150 words is a good target. Use a real sender name, natural subject lines, and a clear reason for emailing. Where appropriate, invite a reply (replies are a strong positive signal): Ask a simple question with an easy answer. Offer a choice (“Which option fits you best: A or B?”). Operational checklist Send daily (or at least 5 days/week). Consistency matters more than “big days.” Watch for early warning signs: bounce spikes, throttling, or sudden spam placement. If you need a structured ramp, reference the Email Ramp Up Schedule and use the Quick Start Guide to set up InboxAlly’s engagement-based warm-up. Week 3–4 (50–200 emails/day): “Expand carefully, keep engagement high” Who to send to Broader engaged segments, such as: Opened/clicked in the last 30–60 days Active customers/users Recent webinar/event attendees Still avoid long-dormant contacts. What to send Begin introducing campaign-like content gradually: A weekly newsletter edition A product update with one primary CTA Educational sequences (2–4 emails) with clear value per message Keep the “human” feel even if it’s a campaign: One main idea per email Limited links (1–3), minimal heavy design Cadence and volume Increase volume in small steps (e.g., +20–40/day every few days) rather than doubling overnight. Maintain a steady schedule so providers see predictable behavior. Provider-specific monitoring Track performance by mailbox provider (e.g., separate trends for major providers): Open/click trends Spam placement or “missing inbox” reports Deferrals/throttling patterns If one provider lags, hold volume steady (or reduce) for that provider’s segment while continuing cautiously elsewhere. Week 5–6 (200–500 emails/day): “Introduce less-engaged segments without triggering complaints” Who to send to Carefully add less-engaged recipients in controlled batches. Segment by recency: 60–90 days since last engagement (small batch first) 90–120 days (only if metrics remain strong) Keep your most engaged segment in the mix daily to “anchor” engagement rates. What to send Use re-engagement-style messaging that earns positive actions: “Still want these updates?” preference check “What would you like to receive?” topic selection A high-value asset (guide, checklist) with a single CTA Consider a “breakup” style email for older segments: Clear opt-out language (“If this isn’t relevant, no worries—unsubscribe here.”) This can reduce complaints by giving people an easy exit. Non-negotiable metrics Keep complaint rates extremely low (aim as close to zero as possible). Keep bounces low by: Removing invalid addresses Avoiding old, unverified lists Pausing segments that show rising hard bounces What to avoid Big promotional blasts to the full list. Sudden template changes (new design, lots of images, many links) at the same time as a volume jump. Week 7–8 (scale toward target volume): “Ramp to normal sending—without losing inbox placement” Who to send to Add additional segments in controlled batches: Expand recency windows gradually Introduce new audiences only after prior batches perform well If you have multiple subdomains or streams, ramp each stream thoughtfully (don’t assume one warm-up covers all). What to send Your normal mix of content, introduced progressively: Newsletters, lifecycle sequences, product announcements, promotions Keep engagement-friendly structure: Clear value above the fold One primary CTA Easy unsubscribe and preference options How to scale Increase volume toward your target while keeping steady daily sending. If you see negative signals (spam placement, throttling, engagement drop), pause increases for 3–5 sending days and stabilize before pushing higher. Monitoring priorities Inbox vs spam placement trends Sudden drops in opens/clicks (often a placement signal, not “bad content”) Provider-specific throttling/deferrals List health (bounces, complaints, unsubscribes) For a faster, more controlled ramp—especially if you’re eager to reach full volume—InboxAlly’s engagement signals can help you build reputation while you follow this schedule (see Email Warm Up Service and Email Ramp Up Schedule). How to tell warm-up is working (and when to slow down) Warm-up success looks like consistency as you follow your email warm up timeline—metrics stay steady (or improve) while daily volume rises. Positive signals your warm-up is working Watch for these trends over several sends (not just one day): Stable or declining bounce rates (especially hard bounces) as you ramp volume Low spam complaints and minimal unsubscribes relative to list size Improving inbox placement (more mail landing in Primary/Inbox vs Promotions/Spam) Reduced throttling: fewer slowdowns, fewer “try again later” responses, faster delivery completion Steady engagement as volume increases: opens/clicks don’t collapse when you add new segments InboxAlly engagement stays strong, reinforcing positive reputation signals as you scale (see How Does InboxAlly Work) Warning signals you’re ramping too fast Slow down if you see any of the following: Bounce spikes (often a sign you expanded to riskier segments or skipped verification) More spam-folder placement or sudden drops in inbox placement Sharp open/click declines that don’t match a content change “Rate limited,” deferrals, or temporary failures increasing day-over-day Blocks or blacklist indicators (provider rejections, reputation alerts) What to do when metrics slip Don’t panic—and don’t go dark. Instead: Pause volume increases for 2–3 sends (keep sending to your best segment). Step back to the last “safe” daily volume from your email warmup schedule (reference Email Ramp Up Schedule). Tighten targeting: send only to recently engaged recipients; exclude older/unresponsive contacts. Run placement + content checks: test subject lines, links, and formatting; validate inbox vs spam outcomes (InboxAlly makes this easier). Re-verify your list and remove hard bounces/unknowns before ramping again (see How Long Does It Take to Warm Up a Domain). Different warm-up scenarios: new IP vs new domain vs a cold (previously active) domain—and subdomains New IP vs. new domain: what reputation is shared (and what isn’t) IP reputation is tied to the sending IP address. If you move to a new dedicated IP, you’re rebuilding trust with mailbox providers at the IP level. Domain reputation is tied to your From domain (and often your DKIM signing domain). A new domain has no history, so filters watch engagement and complaints more aggressively. Why a new domain often needs more patience: even with a “clean” IP, a brand-new domain can trigger extra scrutiny—especially during the domain warm up period and if the domain is very new. If you’re on an ESP shared IP: the IP reputation is largely “borrowed” from the pool, so your email warm up timeline depends more on domain reputation + recipient engagement. In this case, focus on a conservative email sending ramp up and strong opens/clicks. InboxAlly can accelerate early positive signals (see Email Warm Up Service and How Does InboxAlly Work). Existing domain that went cold: restart based on downtime + list quality How long to warm up email again depends on: Downtime length (weeks vs. months) List freshness (recent opt-ins vs. older, unengaged contacts) Prior complaint/bounce history Recommended restart ramp: Start at 10–50/day to your most engaged segment for several days. Increase in small steps every 2–3 days (avoid doubling repeatedly). Reintroduce broader segments only after stable inbox placement. Sudden spikes look suspicious because they resemble compromised accounts or purchased-list behavior. Subdomains: do you need to warm up separately? Subdomains (e.g., news.example.com) build their own reputation, but mailbox providers may still associate them with the root domain—especially via shared branding, DNS, and sending patterns. Even if your root domain is healthy, ramp up a new subdomain with a dedicated warmup schedule to avoid throttling and spam placement. Follow InboxAlly’s Email Ramp Up Schedule and review How Long Does It Take to Warm Up a Domain for timing benchmarks. Manual warm-up vs warm-up tools (and how InboxAlly accelerates the timeline safely) Manual warm-up (DIY) Manual warm-up means gradually increasing daily sends to your real audience while keeping complaints, bounces, and spam placement low. Pros No additional tooling required Builds reputation on genuine subscriber behavior Cons / operational burden Time-intensive list segmentation and daily volume planning Requires constant monitoring and quick adjustments Results vary widely based on list quality and content Why engagement is the limiting factor (not volume) Mailbox providers don’t reward “more sending.” They reward positive engagement signals (opens, replies, clicks, saves, moving to Primary/Inbox) and punish negative ones (deletes without reading, spam complaints, bounces). If engagement doesn’t keep pace, increasing volume can backfire. Common DIY mistakes Ramping too fast: jumping from small batches to full-list sends before reputation stabilizes Sending to unengaged segments: warming up with cold lists creates negative signals immediately Stopping too early: pausing sends resets momentum; consistency matters during the domain warm up period For a baseline plan, use the Email Warmup Planner alongside the Email Ramp Up Schedule. Engagement-based warm-up tools Engagement-based warm-up tools add a controlled layer of consistent positive signals from day one using seed emails (real inboxes that open, read, and interact). This helps stabilize reputation while you continue sending to your real audience. Where they fit Run seed emails in parallel with your normal warm-up sends Keep real-audience sends focused on your most engaged recipients first Use seed emails to maintain consistency on days your audience engagement fluctuates How InboxAlly accelerates safely InboxAlly combines seed emails with a guided setup wizard so you can start warming up quickly without guessing. Monitor and adjust with InboxAlly IA Score: a clear, ongoing indicator of deliverability health Placement Tester / Email Audit: validate inbox vs spam placement and diagnose issues early IA Assistant: open it in the InboxAlly app for guided help with warm-up pacing, authentication checks, and troubleshooting placement issues Recommended next reads: How Long Does It Take to Warm Up a Domain Email Warm Up Service How Does InboxAlly Work Impact of Domain Age on Email Deliverability Quick Start Guide Start improving inbox placement today with a free InboxAlly trial. --- ## What email content practices improve deliverability? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/email-content-best-practices-for-deliverability/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-10 - Description: Copy, links, images, and HTML signals that spam filters weigh — plus the content mistakes that send emails straight to junk. - Keywords: email content best practices, email deliverability content tips, spam filter content triggers, text to image ratio email, email HTML best practices, how to avoid spam folder > Clear value in the first two lines, consistent branding, one primary CTA, descriptive links, balanced text-to-image ratio, clean HTML, and a visible unsubscribe. Avoid image-only layouts, aggressive claims, link farms, shortened URLs, and messy markup — these are the content signals spam filters weigh alongside authentication and sender reputation. Email content matters for deliverability because inbox providers and spam filters evaluate what you say and how you format it alongside authentication (SPF/DKIM/DMARC), sender reputation, and recipient engagement. Great copy won’t fix a bad domain, but when those fundamentals are in place, content is often the deciding factor between Inbox, Promotions, and Spam. This guide focuses on the biggest content-based levers that move deliverability outcomes fast: Spam-filter patterns (not just spam trigger words—also repetition, urgency stacks, and risky phrasing) Text-to-image balance (why image-heavy emails get flagged or clipped) Link + tracking hygiene (too many links, mismatched anchors, shared tracking domains) HTML quality (clean structure, inline CSS, accessible formatting) Personalization signals (segmentation and dynamic relevance beyond {{first_name}}) Compliant unsubscribes (including one-click requirements that reduce complaints) Send: clear value in the first 2 lines, consistent branding, one primary CTA, descriptive links, readable text, and a visible unsubscribe. Avoid: image-only promos, “guaranteed”/aggressive claims, link farms, broken or shortened URLs, messy HTML, and hidden opt-outs. Before you hit your full list, run your content through the free Email Spam Checker or Email Content Tester to catch issues early. For scoring context, see How SpamAssassin Scoring Works. Also make sure your list is clean with email list verification. How modern spam filters evaluate email content (beyond “spam words”) Modern email spam filters don’t flag messages just because they contain a few “bad” words. Mailbox providers and filtering layers score content using patterns, ratios, and context—then combine that with sender reputation and recipient behavior. How content gets scored: patterns, ratios, and context Filters look for signals that correlate with unwanted mail, including: Keyword clusters (not single words): Certain topics become risky when combined—e.g., urgency + money + guarantees. One “discount” is normal; repeated “limited time,” “act now,” “risk-free,” and “cash” in the same email is not. Frequency and density: Repeating the same phrase in the subject, preheader, headline, and CTA can look like templated promotion rather than genuine communication. Formatting anomalies: Excessive punctuation (e.g., “!!!”), ALL CAPS, or aggressive styling (multiple font sizes/colors). Image-heavy layouts with minimal text (often used to hide keywords). Broken HTML, messy code, or copy-pasted templates that render inconsistently. Template fingerprints: Filters can recognize reused structures (same blocks, same CTA placement, same phrasing) across many sends—especially when paired with low engagement. User feedback signals: Complaints, deletes-without-reading, low replies, and low “read time” can amplify minor content issues. Positive engagement can do the opposite. Before you send, use the free Email Spam Checker to catch content and formatting risks early. “What words or phrases trigger spam filters?” There isn’t a universal banned-word list, but these commonly contribute to higher risk—especially in combination or repeated: Urgency: “act now,” “limited time,” “don’t miss out,” “urgent” Money/claims: “guaranteed,” “no risk,” “100% free,” “earn extra cash,” “get paid” Overhyped promos: “best price,” “winner,” “exclusive deal,” “once in a lifetime” Formatting cues: “FREE!!!”, “READ NOW”, “$$$” Context matters: “Free shipping on your order” in a normal sentence is typically fine. “FREE $$$ ACT NOW!!!” plus multiple links and heavy styling is a pattern filters associate with spam. SpamAssassin (high-level): rule-based scoring and thresholds SpamAssassin is a classic rule-based content filter. Each rule adds or subtracts points based on what it detects (e.g., suspicious phrases, HTML patterns, link characteristics). The total becomes a spam score. If the score crosses a configured threshold, the message is more likely to be flagged or routed to spam. For a deeper breakdown, see How SpamAssassin Scoring Works. Content filters vs provider ML models (Gmail/Microsoft) Rule-based systems evaluate what’s in the email. Provider machine-learning models evaluate how recipients react at scale—opens, reads, replies, moves to inbox, and spam complaints—alongside sender history. That’s why improving engagement (and validating content with the free Email Spam Checker) can often override minor content issues that would otherwise drag down deliverability. Text-to-image ratio and formatting that keeps emails readable (and scannable) to filters What is a good text-to-image ratio for emails? There’s no single “magic” ratio, but a reliable deliverability-safe target is at least 60% live text / 40% images (or more text-heavy). The goal is simple: avoid image-only emails and make sure the core message is readable even if images don’t load. Practical guidance: Put the main value proposition in live HTML text, not baked into a banner. Use images to support (product shot, chart, hero), not to replace copy. Add descriptive alt text for every meaningful image (e.g., “Spring sale: 20% off annual plan”). Keep a clear hierarchy: one primary headline, short paragraphs, scannable bullets, and a single primary CTA. Why image-heavy emails get flagged Image-forward layouts can look “clean” to humans but “thin” to filters. Common risk signals include: Low semantic text: Filters can’t confidently classify intent when most content is pixels. Hidden-text tricks: Tiny font, same-color text, or off-screen text used to “stuff” keywords is a classic spam pattern. Poor accessibility: Missing alt text and text-in-images degrade user experience—filters increasingly reward accessible, readable content. Similarity to phishing/promotional blasts: Big image + button + little context resembles common scam and mass-promo templates. Email formatting best practices (HTML) Use formatting that reads like a helpful message, not a “coupon flyer”: Typography: 14–16px body text, 1.4–1.6 line-height, high contrast, short line lengths. Emphasis: Use bold sparingly; avoid repeated ALL CAPS, excessive punctuation, and rainbow highlighting. Branding: Keep a consistent header/footer, but don’t let logos and badges dominate above the fold. Links: Avoid a wall of links (nav menus, social icons, multiple CTAs). Prefer 1 primary CTA plus 1–2 supporting links. Before sending, run your content through the free Email Content Tester and review scoring signals in How SpamAssassin Scoring Works. Should I use a plain-text version alongside HTML? Yes—include a plain-text part for better compatibility and clearer intent signals (especially for corporate/security-heavy inboxes). How to do it well: Generate from the HTML (most ESPs can auto-create), then edit for readability. Match the message: same offer, same CTA destination, similar structure. Avoid: mismatched content, broken line wraps, tracking-only link lists, or “blank” plain-text parts. InboxAlly's seed emails can also help offset minor formatting signals by reinforcing positive inbox-provider feedback loops. Link hygiene: URLs, anchors, tracking parameters, and what spam filters dislike Spam filters evaluate link patterns, not just your wording. Links can raise your spam score when they look manipulative, risky, or inconsistent. Link-based risk signals to avoid Too many links: A high link-to-text ratio (especially in short emails) can resemble phishing or affiliate spam. Repeated domains: Linking the same domain 6–10 times (nav-style footers, repeated CTAs) can look automated. URL shorteners: Shortened links hide the destination and are frequently abused. Redirect chains: Multiple hops (tracking → redirect → final URL) increase risk and can break in some clients. Mismatched anchor text vs destination: “Invoice PDF” linking to a marketing landing page is a classic trust signal failure. “Good vs bad” link examples Good Descriptive anchor + matching destination: Anchor: “Download the Q2 deliverability checklist” URL: https://yourdomain.com/resources/q2-deliverability-checklist Consistent, secure domains: Use HTTPS and keep links on your primary domain or a clearly related subdomain. Minimal redirects: One tracking hop at most, then the final page. Bad Generic anchor + different domain: Anchor: “Click here” → https://other-domain.example/promo Shortened URL: Anchor: “View details” → https://bit.ly/… Misleading anchor: Anchor: “Unsubscribe” → a preference center that doesn’t actually unsubscribe (also a compliance risk). Broken links and reputation (404s, mixed content, sketchy TLDs) 404/410 pages signal poor maintenance and can correlate with low-quality campaigns. Mixed content (HTTPS email linking to HTTP assets) can trigger warnings and reduce trust. Unfamiliar or “sketchy” TLDs and newly registered domains are more likely to be filtered. Pre-send link validation: Run your email through InboxAlly's free Email Spam Checker before sending. It checks your links, redirects, and domains automatically and flags issues alongside your overall spam score (see How SpamAssassin Scoring Works for scoring context). How do tracking links affect deliverability? Tracking often swaps your visible domain for a tracking domain and adds redirects/parameters, which can look like obfuscation—especially if the tracking domain is shared or has weak reputation. Keep tracking while reducing risk by: Using a custom tracking domain aligned with your brand. Limiting redirects and avoiding shorteners. Keeping anchor text honest and consistent with the final destination. Pairing clean links with positive engagement signals (InboxAlly's seed emails can help offset minor content/link signals). Tracking domains and brand alignment: why shared tracking hurts and how to fix it Why shared tracking domains can hurt deliverability Many ESPs (and link trackers) rewrite your links to a shared tracking domain (for example, a generic redirect host used by thousands of senders). That creates three deliverability problems: Pooled reputation: Mailbox providers learn reputation at the domain/host level. If the tracking host is heavily used, your clicks are mixed into a single reputation bucket you don’t control. Cross-sender contamination: If other senders on that shared host run spammy campaigns, the tracking domain can be distrusted—your legitimate emails inherit that risk. Filter distrust of “busy” redirectors: Heavily used tracking hosts often look like link obfuscation. Filters may treat them as higher-risk, especially when combined with promotional language, many links, or mismatched branding. How to set up a custom tracking domain (ESP-agnostic) Use a branded subdomain so your links align with your identity and authentication. Choose a subdomain Common patterns: links.yourdomain.com, click.yourdomain.com, or track.yourdomain.com Keep it consistent with your brand and easy to recognize. Add DNS records Typically a CNAME from your subdomain to your ESP/tracking provider’s host. If your provider requires additional records (A/AAAA/TXT), add those exactly as specified. Enable SSL (HTTPS) Turn on SSL in your ESP/tracker, or provision a certificate if required. Avoid mixed-content or HTTP-only redirects. Align with your From domain If you send from news@yourdomain.com, prefer tracking on the same root domain (e.g., links.yourdomain.com) to strengthen alignment signals. Verify redirects end-to-end Test multiple links to confirm: correct destination, HTTPS, no redirect loops, and no unexpected intermediate hops. Why custom tracking improves inbox placement Custom tracking creates consistency signals: aligned domains, fewer suspicious hops, and clearer brand continuity—reducing spam score risk tied to link hygiene. InboxAlly’s deliverability approach pairs domain/link alignment (preventing avoidable filtering) with seed emails to reinforce positive mailbox-provider signals. For pre-send checks, use the free Email Spam Checker and review How SpamAssassin Scoring Works to spot link-related point additions before you hit send. Subject lines and HTML best practices that reduce spam score (without killing conversions) Subject line patterns: what triggers filters vs what earns opens Modern filters look for patterns that correlate with deception or low-quality mail—not just “spam trigger words.” Avoid these common risk signals: Excessive punctuation/caps: !!!, ??, FREE!!!!!, ACT NOW Misleading reply/forward bait: fake “Re:” / “Fwd:” when there’s no thread Overuse of emojis/symbols: multiple icons, arrows, currency symbols, or decorative Unicode Bait-and-switch language: “Your account is suspended” when it’s really a promo Rewrite examples (same offer, lower risk): Bad: “LAST CHANCE!!! 70% OFF ends tonight!!!” Better: “70% off ends tonight (2 hours left)” Bad: “Re: quick question” (cold promo) Better: “Quick question about your [goal]” (only if it’s truly relevant) Bad: “🚨 You’ve been selected for a FREE gift 🎁” Better: “A thank-you gift with your next order” Bad: “Your invoice is attached” (not true) Better: “Receipt + next steps for your order” (only if accurate) Tip: keep subjects specific, truthful, and aligned with the first line of the email to avoid “promise mismatch” complaints. HTML and formatting best practices (deliverability-safe) Spam filters and mailbox providers increasingly penalize HTML that looks auto-generated, obfuscated, or inconsistent across sends. See Gmail and Yahoo Changes for Bulk Senders in 2024 and Why Are My Emails Going to Spam? for the broader policy context. Use these HTML rules: Clean code: remove unused tags, comments, and editor cruft Minimal nesting: avoid deeply nested tables/divs Inline CSS: prefer simple inline styles over complex wrappers that bloat code. Plain-text parity Include a real plain-text version (not empty, not “View in browser” only). Match intent and links: the plain-text should contain the same primary CTA and destination as HTML. SpamAssassin / “spam score” testing workflow A spam score is a heuristic total based on rules (content patterns, HTML issues, link signals, authentication hints). Higher scores indicate higher risk of spam-folder placement. Many systems treat ~5.0 as a common “fail” threshold, but your mailbox providers may behave differently. How to interpret common flags HTML-only / low text: fix (add copy + plain-text). Too many links / redirect chains: fix (reduce links, remove shorteners, ensure clean destinations). Suspicious phrases: often fix (rewrite), but don’t obsess over single “spam trigger words” if the overall email is legitimate and well-structured. Missing List-Unsubscribe: fix immediately (see RFC 8058 Compliance). Minor formatting nits (e.g., one unusual header): sometimes ignore if everything else is clean—prioritize issues tied to links, authentication, and content structure. For deeper context, see How SpamAssassin Scoring Works. InboxAlly tools to run before you send Use InboxAlly’s free Email Content Tester for quick subject/body/link and formatting checks. Run a score-based scan with the free Email Spam Checker to surface common SpamAssassin-style flags. For teams iterating weekly, use the in-app Email Content Tester (create an account via InboxAlly signup) to standardize pre-send QA. Safe rollout plan (reduce risk while you iterate) Send to your most engaged segment first (recent openers/clickers). Monitor: spam complaints, bounces, and inbox vs spam placement (use your seed tests). Adjust content/links/tracking, then expand to broader segments in stages. When iterating, InboxAlly’s seed emails can help stabilize placement signals while you refine content and formatting. Need help optimizing your email content? Open the IA Assistant in the InboxAlly app for guidance, or start a free trial to test your content and monitor inbox placement. --- ## Do subdomains share email sender reputation? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/how-does-reputation-work-between-sub-domains/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-10 - Description: Subdomains build mostly independent sender reputations, but root-domain problems can bleed across. Manage the overlap to protect deliverability. - Keywords: subdomain email reputation, do subdomains share sender reputation, subdomain vs root domain deliverability, email sending subdomain strategy, subdomain reputation isolation > Subdomains mostly build their own sender reputation independently, but they are not fully isolated from the root domain. If mailbox providers see consistently risky behavior tied to your organization, they may apply extra scrutiny to related subdomains — especially when authentication, infrastructure, or sending patterns overlap. Subdomains mostly build their own sender reputation independently, but they’re not fully isolated from the root domain. Understanding where reputation is separate (and where it can “bleed” across) helps you protect transactional deliverability from marketing risk and warm up new sending streams correctly. How subdomain reputation works Most major mailbox providers (Gmail, Outlook, Yahoo) treat subdomains as mostly independent senders with their own reputation signals. For example: marketing.example.com earns a reputation based on its own volume, engagement (opens/clicks/replies), spam complaints, bounces, and consistency. notify.example.com builds its own reputation separately—so your receipts and password resets aren’t automatically judged by how your newsletter performs. That said, the root domain (example.com) still acts like an umbrella identity. If providers see consistently risky behavior tied to your organization, they may apply extra scrutiny to related subdomains—especially when authentication, infrastructure, or sending patterns overlap. A few practical nuances: Gmail tends to weight domain reputation heavily, so domain-level trust (including the root domain) matters. Outlook often considers IP reputation more, so shared IPs and sending infrastructure can increase the chance of cross-impact. The takeaway: subdomains are a strong way to segment risk, but they’re not a “get out of jail free” card if overall sending practices are poor. When to use separate subdomains Use separate subdomains when two email streams have different risk profiles or engagement patterns. Common, practical setups include: Marketing vs. transactional marketing.example.com for newsletters, promotions, product announcements notify.example.com (or mail.example.com) for receipts, password resets, account alerts This protects critical messages if marketing engagement dips or complaints rise. Outreach / cold email outreach.example.com for prospecting or low-engagement lists This isolates higher-risk sending from your main brand domain and your transactional stream. Different product lines or brands If you operate multiple products, separate subdomains help keep reputations independent (and make troubleshooting easier when one stream underperforms). Rule of thumb: if you’d be comfortable with one stream getting temporarily throttled or filtered without impacting the other, they should probably be on different subdomains. What to configure for each subdomain Treat every subdomain as its own sender that needs complete setup and ongoing care. Each subdomain should have: SPF coverage Either a dedicated SPF record for the subdomain, or ensure the parent domain’s SPF legitimately covers the services sending for that subdomain. DKIM signing Configure DKIM for the subdomain with its own selector(s), so mail is cryptographically signed as authorized. DMARC alignment DMARC should align with the visible “From” domain. If you send as From: updates@notify.example.com, your authentication should align to notify.example.com (not just example.com). Its own warm-up A new subdomain should be treated like a fresh sender—start low, ramp gradually, and prioritize high-engagement recipients first. Follow the volume guidance in: Email Warm-Up Timeline: Week-by-Week Schedule Email Ramp-Up Schedule You can also use the free Email Warmup Planner to map a safer ramp. Monitoring Track each subdomain separately in Domain Reports so you can spot authentication issues, reputation drops, or sudden changes in performance early. Use Placement Tester when you need to confirm inbox vs. spam placement across providers. What can bleed across subdomains Reputation spillover is most likely when providers see shared risk signals. Common scenarios include: Consistently poor practices on the root domain High complaint rates, frequent bounces, or repeated filtering on example.com can reduce trust in related subdomains. Shared authentication failures If DMARC is failing broadly (or misconfigured at the organizational level), it can undermine trust across subdomains. Blocklist side effects If one subdomain is blocklisted, some lists may also flag the root domain or related subdomains. Use the free Spam Database Lookup to check status, and follow the Blocklist Impact and Remediation Guide. Sudden aggressive sending from a new subdomain A brand-new subdomain that immediately sends high volume can look suspicious—especially if the root domain has limited positive history. Not sure whether your sending streams need separate subdomains? Open the IA Assistant in the InboxAlly app for guidance on subdomain strategy, authentication setup, and warm-up planning. Start a free InboxAlly trial --- ## Does domain age affect email deliverability? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/impact-of-domain-age-on-email-deliverability/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-13 - Description: New domains face extra scrutiny from mailbox providers and blocklists. Domain age matters most early on — sending behavior matters more long-term. - Keywords: domain age email deliverability, does domain age affect email, new domain email reputation, how old does a domain need to be to send email, domain age and spam filters > Domain age has the biggest impact when your domain is new — mailbox providers and some blocklists treat recently registered domains as higher risk, which can temporarily reduce inbox placement. Over the long term, sending behavior, engagement, and authentication matter far more than age alone. An old domain with a poor reputation will still have deliverability issues. Domain age is the length of time a domain has been registered and active. Mailbox providers and certain blocklists treat recently registered domains as higher risk, which can temporarily reduce inbox placement — but over the long term, sending behavior, engagement, and authentication matter far more than age alone. What is Domain Age and how does it impact my email deliverability? Domain age is the amount of time your domain has been registered and active. In deliverability terms, domain age matters most when your domain is new: mailbox providers and some blocklists treat recently registered domains as higher risk, which can temporarily reduce inbox placement until the domain “ages” and builds a positive sending history. Domain age definition Domain age is a fairly simple concept: it’s the amount of time that your domain name has been registered and active. A domain that was registered yesterday has a domain age of one day, and a domain registered five years ago has an age of five years. Older domains generally have a better reputation and are considered more trustworthy by many services. Older domains generally rank better in search engines and have better email deliverability, as long as they haven’t been used for spam in the past. Does domain age affect deliverability? There are many factors that impact your email deliverability, such as your sender reputation, authentication, past sending practices, and your domain’s age. Over the long term, domain age has a relatively small relationship with deliverability, with one big exception: New domains. Generally, ISPs consider older domains to be more reputable and trustworthy than new domains, but an old domain with a poor reputation will still have deliverability issues. A brand-new domain with zero reputation or history may appear on blacklists designed to flag new domains, and the only way to be removed from them is to wait for your domain to age. For general context on how blacklists affect sending (and what to do about them), see the Blocklist Impact and Remediation Guide. For example, Spam Eating Monkey (a blacklist provider) has several blacklists that include all recently registered domains. These include blacklists such as the SEM-FRESH blacklist for domains registered in the last five days and the SEM-FRESH30 blacklist for domains registered in the last 30 days. Each of these blacklists automatically adds and removes domains that were created in that time period, and there is no way to manually be removed from them while your domain is still not old enough. (Related: SEM-FRESH blocklist.) In the instance of a new domain, your email deliverability will be negatively affected until your domain is removed from these blacklists. You may find with newer domains that emails go to spam more often, are less likely to end up in the main inbox, having worse overall deliverability. In general, even domains greater than 30 days old that are less than 60-90 days old have worse deliverability than old ones because of these reasons. During this period, it’s best to warm up your domain to ensure solid deliverability after you’ve been removed from these blacklists. Use the Email Warm-Up Timeline: Week-by-Week Schedule as your step-by-step plan. How can you improve your domain age and reputation? The only way to change your domain age is to have an active domain for a long period of time. The older your domain, the less likely it is to be flagged by age-related blacklists. The good news is that new domains start off without any sender history or reputation, so you can start fresh if you’ve experienced deliverability problems in the past. To set a new domain up for success: Register early: Register your domain 2–4 weeks before you plan to send campaigns. Set up authentication during the aging period: Configure SPF, DKIM, and DMARC before you ramp volume. (InboxAlly users can monitor this in Domain Reports.) Start with very low volume: Send first to your most engaged recipients (people who recently opened/clicked/replied). Ramp up gradually: Follow a structured plan like the Email Ramp-Up Schedule. Generate positive engagement signals: Use InboxAlly’s seed email network to create consistent opens, clicks, and “move to inbox” actions during the critical early period. Follow a full warm-up plan: Reference the Email Warm-Up Timeline: Week-by-Week Schedule for the complete progression. Not sure if your domain is ready to send? Open the IA Assistant in the InboxAlly app for a guided check of your domain age, authentication, and readiness. --- ## How does email spam testing work? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/how-does-email-spam-testing-work/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-10 - Description: Pre-send content scans, seed-inbox placement tests, and ongoing monitoring — three layers of spam testing that catch deliverability issues early. - Keywords: email spam testing, how to test email for spam, email placement test, pre-send spam check, inbox placement testing tools, email deliverability testing > Email spam testing checks your messages before and during sending to catch deliverability issues. **Pre-send content tests** analyze subject lines, HTML, and links against spam filter rules. **Placement tests** send to real seed inboxes to see where your email actually lands. **Ongoing monitoring** tracks inbox vs. spam placement across providers over time. Email spam testing means checking your emails before and during sending to catch issues that hurt inbox placement. There are different types of tests for different purposes — here’s how they work and when to use each. The five-stage filtering pipeline that determines whether your email reaches the inbox, promotions, or spam. 1. Authentication alignment checks SPF, DKIM, and DMARC to verify sender identity and domain legitimacy. 2. Content analysis scans message copy, formatting, structure, and headers for suspicious patterns. 3. Link reputation evaluates URLs and linked domains for trust, historical abuse, and redirect behavior. 4. Sender reputation uses historical signals like engagement, complaint rate, and sending consistency to assess trust. 5. Spam trap and complaint signals increase risk score. 6. All signals combine into an overall filtering decision routing to inbox, promotions, or spam. Pre-send content testing (check your email before sending) What it does Pre-send content testing analyzes your draft email before it goes to your list. It reviews your: Subject line and body copy HTML structure and formatting Headers and basic technical signals (as visible in the message) Links and tracking elements The goal is to flag common spam-filter triggers early, when they’re easiest to fix. What it catches A good content test can surface issues like: Spammy or overly promotional language (e.g., aggressive “free/urgent” phrasing) Broken or messy HTML (extra tags, malformed code, hidden text) Image-to-text ratio problems (e.g., one big image with little text) Problematic links (suspicious domains, mismatched link text vs. destination, URL shorteners) Missing unsubscribe link (especially important for marketing email) Missing or misaligned authentication indicators in the message headers (when detectable) How to use it Send your draft to a testing address or paste the content into a testing tool. Review the spam score and the specific recommendations. Fix the flagged items (copy, links, formatting, footer/unsubscribe, etc.). Re-test until the results look clean. Then send to your real audience. InboxAlly tools to use InboxAlly’s free Mail Tester checks your spam score and highlights common content and formatting issues before you send. The free Email Content Tester is useful for quick subject line and content scoring when you’re iterating on copy. When to run it Treat this as a one-time check per campaign — run it before every major send (newsletters, promotions, launches, cold outreach sequences, etc.). Inbox placement testing (see where your emails actually land) What it does Inbox placement testing sends your email to real test inboxes across major mailbox providers (like Gmail, Outlook, Yahoo, and others). It then reports whether the message landed in: Inbox Spam/Junk Promotions/Other tabs (provider-dependent) Missing (not delivered or not found) Why it’s different from content testing Content testing tells you if something might trigger filters. Placement testing tells you where the email actually ended up. Placement is influenced by more than copy and HTML, including: Sender/domain reputation Authentication alignment (SPF/DKIM/DMARC) Sending patterns and volume changes Provider-specific filtering behavior This tests the full picture Because placement testing involves real inboxes, it reflects the combined impact of: Your message content Your technical setup Your current reputation with each provider InboxAlly tools to use Placement Tester (in-app) runs inbox vs. spam placement tests across providers so you can validate deliverability before you scale a campaign. Email Audit (in-app) goes deeper when results are poor — it reviews authentication, content, and sending patterns together to help pinpoint why placement is happening. Important note Don’t confuse test inboxes (used for placement testing) with InboxAlly’s seed emails (used to generate engagement signals like opens/clicks/moves to inbox). They solve different problems and are used at different stages. Ongoing monitoring (catch problems before they grow) Content tests and placement tests are point-in-time snapshots. Ongoing monitoring helps you spot trends early, before they turn into reputation damage. Use monitoring to track and prevent: Gradual reputation decline Authentication drift (DNS changes, misalignment) Blocklist issues List quality problems that increase bounces/complaints InboxAlly tools to use Domain Reports (in-app) to monitor authentication status and reputation signals over time. Free Spam Database Lookup to check whether your domain or IP appears on major blocklists. Free Email List Verification to validate lists and reduce bounces, spam traps, disposable emails, and catch-all risk. When to use what Before every campaign → run the free Mail Tester Before a big send or after deliverability changes → run Placement Tester If placement is poor and you don’t know why → run Email Audit Periodically (weekly/monthly) → check Domain Reports and Spam Database Lookup Before importing a new list → run Email List Verification Not sure where to start? Open the IA Assistant in the InboxAlly app — it can help you choose the right tests based on what you’re seeing. Start a free InboxAlly trial --- ## Why are automated email warmup services risky? - URL: https://www.inboxally.com/docs/warm-up-sending-strategy/the-dangers-of-using-an-automated-email-warmup-service/ - Section: Warm-Up & Sending Strategy - Last Modified: 2026-03-12 - Description: Automated warmup tools exchange emails between customer accounts — but Gmail and Outlook detect the patterns, risking suspensions and exposure. - Keywords: automated email warmup risks, email warmup service dangers, are email warm up tools safe, automated warmup vs seed emails, email warmup service problems, warm up tool account suspension risk > Automated warmup services connect your account to hundreds of other customers to exchange emails, but Gmail and Outlook can detect these patterns — especially at higher volumes. Key risks include: ineffectiveness at scale, incompatibility with most ESPs, public exposure of your email content to other customers, and potential Terms of Service violations that can get your account suspended. An automated email warmup service connects your email account with hundreds or thousands of other customers to exchange emails back and forth, with the goal of gradually increasing send volume and building sender reputation. However, providers like Gmail and Outlook can detect these patterns — especially at higher volumes — which can trigger account suspensions, reduce deliverability, and expose your email content to other customers on the same platform. Here are the key risks to understand before using one. 1. Ineffectiveness for many Although these services pool your email with others, Google and Outlook can detect that your account is being manipulated by automation. While it may work well enough for small amounts of email, larger volumes tend to be less effective due to inbox providers recognizing common patterns among users. Plus, you have limited control over the warmup process itself. 2. Reduced functionality with ESPs Do you use an Email Service Provider (ESP) like MailChimp, Klaviyo, or SendinBlue? Most warmup services aren't compatible with these platforms. And, even the ones that do work with ESPs don't send emails the same way you usually would, instead using SMTP or an API, which means the warmup results might not translate to "real" sends. 3. Public visibility of your email content When connecting with a warmup service, you’re potentially letting your competitors or other customers see your emails and the content you're sending. You can check this by looking at your sent emails folder to see who your emails have been sent to, or by looking at your inbox or archived emails, and seeing that content and from whom it was sent. 4. Security issues Warmup services require full access to your email account which means you're not only sharing access to all the emails you have ever sent but also all the emails you have received. This can include your customer list, sensitive information, and even personal data. While you may trust the company, can you be confident that none of their employees or contractors will conduct unauthorized activities or misuse your data? Also, are they based in a country with whom you are comfortable with, which follows international business law? 5. Lowered deliverability due to spammers Spammers on the same warmup service can lessen the effectiveness of these services or even hurt your deliverability. Inbox providers can detect when multiple emails emanating from the same platform are warming up (regardless if you paste in your own template), flagging it as potential spam. As a result, using a shared warmup service can inadvertently harm your email campaign and deliverability. 6. Easily detectable non-human activity While humans engaging with emails they receive is ideal, robotic engagement through APIs or automation can be easily detected, rendering the service significantly or totally ineffective. Moreover, your email account may be temporarily disabled if it is frequently accessed from various geographies or machines. Additionally, these services do not allow you to simulate a realistic sending process, where an email broadcast is sent and interacted with gradually over an extended period. This can lead inbox providers to recognize the automated nature of the engagement.. 7. Cluttered inbox Due to the services sending emails back and forth among multiple email accounts, your inbox may become cluttered with random messages and replies that are difficult to distinguish from genuine correspondence. Although some services allow you to include a code for filtering purposes, using a code can also be used as a trackable fingerprint for inbox providers to detect. 8. IP/Domain Repair Capabilities If you do not necessarily need to warm up a new email account, but instead want to repair a damaged one with deliverability issues, most warmup services can't do that. (Most don’t even pretend nor claim they do). This is because they don’t have the efficacy due to reasons mentioned above or simply not enough emails for large senders to send to make a difference. Conclusion So, while it may seem tempting to speed up the warming process with an automated email warmup service, the majority of these services have potential issues that may likely outweigh the benefits. For a more trustworthy and reliable approach to improving your email deliverability, consider using InboxAlly, an email spam fix/warmup solution. Unlike other solutions, InboxAlly ensures your email content remains private and avoids many of the pitfalls associated with automated email warmup services. The bottom line is: Weigh the pros and cons carefully before jumping on board with an automated email warmup service. Explore other alternatives like InboxAlly to determine what works best for you and your email marketing campaigns. And remember, the key to a successful email campaign is ensuring it reaches your recipients' primary inboxes without jeopardizing your domain, IP address, and email security. Darren Blumenfeld is the founder of InboxAlly, an email spam fix/warmup solution that avoids the pitfalls of other solutions. --- ## Email Deliverability - URL: https://www.inboxally.com/docs/concepts/email-deliverability/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Email deliverability is the ability of an email to reach the recipient's inbox rather than being filtered to spam, bounced, or blocked. - Keywords: email deliverability, inbox placement, sender reputation, spam filtering > Email deliverability measures whether your emails actually reach the inbox. It's determined by sender reputation, authentication, content quality, and recipient engagement — not just whether the email was technically sent. Email Deliverability Email deliverability is the measure of how successfully an email reaches the intended recipient's inbox. It encompasses sender reputation, email authentication, content quality, and recipient engagement — all of which mailbox providers evaluate to decide whether an email belongs in the inbox, spam folder, or should be blocked entirely. How emails flow through mailbox provider systems from send to delivery, with engagement feeding back into reputation. 1. Email sender transmits a message using its sending infrastructure and domain. 2. Mailbox providers authenticate the sender using SPF, DKIM, and DMARC. 3. Mailbox providers evaluate the sender's historical reputation using engagement, complaints, and sending behavior. 4. Spam filtering algorithms analyze message content, links, authentication alignment, and reputation signals. 5. Based on filtering signals the message is delivered to inbox, promotions, or spam. 6. Opens, clicks, and spam complaints feed back into sender reputation and influence future filtering. Why Email Deliverability Matters Every email that lands in spam is a missed opportunity. Whether you're sending transactional emails, marketing campaigns, or cold outreach, deliverability directly determines your return on investment. High deliverability means: More of your audience sees your message Higher open rates and click-through rates Better sender reputation over time (a positive feedback loop) Lower cost per conversion Low deliverability means: Wasted sending costs on emails nobody sees Declining sender reputation (a negative spiral) Potential blocklisting that affects your entire domain What Determines Deliverability Mailbox providers like Gmail, Yahoo, and Microsoft evaluate several factors: Sender Reputation Your sender reputation is a score assigned by mailbox providers based on your historical sending behavior. It's the single most important factor in deliverability. Email Authentication Properly configured SPF, DKIM, and DMARC prove that you are who you claim to be. Without authentication, your emails are far more likely to be flagged as suspicious. Engagement Signals Engagement signals — opens, clicks, replies, and time spent reading — tell mailbox providers that recipients want your email. Low engagement tells them the opposite. Content and Sending Patterns Sudden spikes in volume, spammy content, and high complaint rates all damage deliverability. Consistent, gradual sending with relevant content supports it. How InboxAlly Helps InboxAlly improves deliverability by generating positive engagement signals through seed emails. When InboxAlly's network of real mailboxes opens, reads, and interacts with your emails, mailbox providers observe genuine engagement — boosting your sender reputation and improving inbox placement over time. This is especially effective during email warmup when a new domain or IP has no reputation history, or during reputation recovery after a deliverability setback. --- ## Inbox Placement - URL: https://www.inboxally.com/docs/concepts/inbox-placement/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-09 - Description: Inbox placement is the percentage of sent emails that successfully land in the recipient's primary inbox rather than spam, promotions, or other folders. - Keywords: inbox placement, inbox placement rate, email delivery vs placement > Inbox placement measures how many of your emails actually reach the inbox — not just whether they were delivered. An email can be 'delivered' but still land in spam. Inbox placement is the metric that matters. Inbox Placement Inbox placement is the percentage of sent emails that successfully arrive in the recipient's primary inbox, as opposed to being routed to the spam folder, promotions tab, or blocked entirely. It is the most accurate measure of email deliverability success. Why Inbox Placement Matters "Delivery rate" and "inbox placement rate" are not the same thing. An email is considered "delivered" if it doesn't bounce — but it may still land in spam. A 98% delivery rate can mask a 40% inbox placement rate. Inbox placement is what actually drives results: Emails in spam are effectively invisible to recipients Promotions tab placement reduces open rates significantly Only primary inbox placement reliably generates engagement What Affects Inbox Placement Mailbox providers decide where to place your email based on: Sender reputation — your historical sending track record Engagement signals — how recipients interact with your emails Email authentication — whether SPF, DKIM, and DMARC are properly configured Content quality — relevance, formatting, and spam trigger avoidance List hygiene — bounce rates, complaint rates, and inactive recipients How InboxAlly Helps InboxAlly directly improves inbox placement by generating real engagement signals through its network of seed emails. When mailbox providers see consistent opens, reads, and positive interactions, they move your emails from spam to the inbox — improving your placement rate over time. --- ## Seed Emails - URL: https://www.inboxally.com/docs/concepts/seed-emails/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-09 - Description: Seed emails are real email addresses used to test and improve inbox placement by generating authentic engagement signals with mailbox providers. - Keywords: seed emails, seed list, inbox placement testing > Seed emails are real mailbox addresses that receive your campaigns and generate genuine engagement — opens, reads, and interactions — to signal to mailbox providers that your emails are wanted. Seed Emails Seed emails are real email addresses maintained across major mailbox providers (Gmail, Yahoo, Microsoft, etc.) that receive a sender's campaigns and generate authentic engagement signals — opens, reads, clicks, and replies — to improve the sender's reputation and inbox placement. How Seed Emails Work Unlike test addresses that simply confirm delivery, seed emails actively engage with your messages. When mailbox providers observe real accounts consistently opening and reading your emails, they interpret this as a positive signal about your sending reputation. The process: Your campaign is sent to your regular list plus a set of seed addresses Seed mailboxes open, read, and interact with the email Mailbox providers register this engagement against your sending domain and IP Your sender reputation improves based on the accumulated positive signals Inbox placement rates increase across your entire sending volume Why Seed Emails Matter Mailbox providers make placement decisions based on aggregate engagement data. A sender whose emails are consistently opened and read will earn better placement than one whose emails sit unopened. Seed emails are especially critical during: Email warmup — establishing reputation for new domains or IPs Reputation recovery — rebuilding after a deliverability setback Ongoing maintenance — sustaining strong inbox placement over time How InboxAlly Helps InboxAlly operates a large network of real seed email addresses across Gmail, Yahoo, Microsoft, and other major providers. When you add InboxAlly's seed list to your campaigns, the network generates authentic engagement signals that directly improve your sender reputation and inbox placement. --- ## Engagement Signals - URL: https://www.inboxally.com/docs/concepts/engagement-signals/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Engagement signals are recipient interactions — opens, clicks, replies, and reading time — that mailbox providers use to evaluate sender quality. - Keywords: engagement signals, email engagement, open rate signals, recipient interaction > Engagement signals are the actions recipients take with your emails. Mailbox providers track these interactions to decide whether future emails from you belong in the inbox or spam folder. Engagement Signals Engagement signals are measurable recipient interactions with email — including opens, clicks, replies, forwards, time spent reading, and moving messages out of spam — that mailbox providers use as input when making inbox placement and sender reputation decisions. Types of Engagement Signals Positive Signals Opens — recipient opened the email Clicks — recipient clicked a link in the email Replies — recipient responded to the email Forwards — recipient shared the email Read time — recipient spent time reading (not just glancing) Moving from spam to inbox — recipient rescued the email from spam Adding to contacts — recipient added the sender to their address book Negative Signals Spam complaints — recipient marked the email as spam Deleting without reading — recipient dismissed the email immediately Ignoring — email sits unopened over time Unsubscribing — recipient opted out of future emails How positive and negative engagement signals feed into sender reputation and drive inbox placement. 1. Positive engagement signals — opens, clicks, replies, read time — strengthen sender reputation. 2. Negative signals — spam complaints, bounces, blocklist hits, volume spikes — damage reputation. 3. Mailbox providers aggregate these signals into a sender reputation score. 4. The reputation score determines whether emails are placed in the inbox, spam folder, or blocked entirely. Why Engagement Signals Matter Mailbox providers like Gmail, Yahoo, and Microsoft use engagement signals as the primary behavioral input for sender reputation. Strong engagement tells providers that recipients want your email. Weak or negative engagement tells them the opposite. This creates a feedback loop: High engagement → better inbox placement → more visibility → more engagement Low engagement → worse placement → less visibility → even lower engagement How InboxAlly Helps InboxAlly generates consistent, authentic positive engagement signals through its network of seed emails. By ensuring your emails receive real opens, reads, and interactions across major mailbox providers, InboxAlly helps establish and maintain the engagement patterns that drive strong inbox placement. --- ## IA Assistant - URL: https://www.inboxally.com/docs/concepts/ia-assistant/ - Section: Email Deliverability Concepts - Last Modified: 2026-05-20 - Description: The IA Assistant is InboxAlly's in-app AI chat that diagnoses email deliverability issues using your account data and walks you through the fix. - Keywords: IA Assistant, InboxAlly AI assistant, AI deliverability assistant, email deliverability chatbot > The IA Assistant is InboxAlly's in-app AI chat assistant. It analyzes your sending data, checks authentication, diagnoses deliverability issues, and recommends concrete next steps based on the playbooks used by InboxAlly's in-house deliverability team. IA Assistant The IA Assistant is InboxAlly's in-app AI chat assistant. It analyzes a sender's account data — IA Reputation Score, placement test results, authentication records, and DMARC reports — to diagnose deliverability issues, walk users through the right checks in the right order, and recommend concrete next steps drawn from the playbooks used by InboxAlly's in-house deliverability team. How the IA Assistant Works A sender opens the IA Assistant inside the InboxAlly app and describes the problem in plain language — for example, "my emails are going to spam at Gmail" or "is my DMARC set up correctly?" The Assistant pulls the relevant data from the sender's account, identifies the most likely cause, and walks the sender through the diagnostic and fix. Unlike a generic AI chatbot, the IA Assistant is grounded in two things: The sender's actual account data — sender reputation signals, inbox placement results, email authentication status, and DMARC reports The diagnostic playbooks used by InboxAlly's in-house deliverability team Why the IA Assistant Matters Email deliverability problems are rarely caused by a single issue — they're usually a combination of authentication gaps, list quality, content signals, and engagement patterns. The IA Assistant compresses the diagnostic process by running the same checks an expert would, in the right order, using the sender's own data. It's particularly useful during reputation recovery, after switching ESPs, or whenever a metric moves in an unexpected direction. How to Use the IA Assistant The IA Assistant is available in every InboxAlly plan, including the free trial. It activates automatically on login and is opened from the app sidebar. For a full walkthrough, see What is the IA Assistant? --- ## Sender Reputation - URL: https://www.inboxally.com/docs/concepts/sender-reputation/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-12 - Description: Sender reputation is the internal evaluation mailbox providers make about your sending domain and IP based on engagement, complaints, bounces, and sending behavior. - Keywords: sender reputation, email sender score, domain reputation, IP reputation, email reputation, sender score > Sender reputation is the internal evaluation each mailbox provider makes about your sending domain and IP address. It's built from engagement history, complaint rates, bounce rates, and sending patterns — and it's a primary factor in whether your email reaches the inbox, lands in spam, or gets blocked. Sender Reputation Sender reputation is the internal evaluation each mailbox provider makes about an email sender based on engagement signals, complaint rates, bounce rates, and sending behavior. It determines whether emails are placed in the inbox, routed to spam, or blocked entirely. Positive and negative signals that feed into sender reputation and determine inbox placement. 1. Positive engagement signals — opens, clicks, replies, read time — strengthen sender reputation. 2. Negative signals — spam complaints, bounces, blocklist hits, volume spikes — damage reputation. 3. Mailbox providers aggregate these signals into a sender reputation score. 4. The reputation score determines whether emails are placed in the inbox, spam folder, or blocked entirely. How Sender Reputation Works Each major mailbox provider maintains its own internal evaluation of your sending domain and IP addresses. There is no single universal "sender score" — Gmail, Microsoft, and Yahoo each assess you independently using their own models. These evaluations are not publicly visible as a number, but monitoring tools provide partial visibility (see below). Reputation is built from signals that vary in impact: High-impact signals — these can damage reputation in a single campaign: Spam complaints — recipients marking your email as spam. Above 0.3% complaint rate is dangerous. Above 0.1% is where Google starts paying attention. Spam trap hits — sending to addresses that exist solely to catch bad senders. Even a small number signals list quality problems. Blocklist inclusion — landing on Spamhaus, Barracuda, or similar lists can cause immediate rejection at scale. Steady-state signals — these build or erode reputation over time: Engagement signals — opens, clicks, replies, read time. Consistent positive engagement is the strongest reputation builder. Bounce rates — high hard bounce rates signal bad list hygiene and erode reputation gradually. Sending volume and consistency — sudden spikes raise flags, but so does going silent. If you send consistently then stop for months, you effectively lose your established reputation and need to warm up again. Email authentication — SPF, DKIM, DMARC compliance. Authentication failures don't just hurt reputation — they can cause outright rejection regardless of how good your reputation is. How Providers Differ Gmail, Microsoft, and Yahoo don't evaluate reputation the same way: Gmail weighs domain reputation heavily and provides the most visibility through Postmaster Tools. Domain reputation and Compliance Status (V2) are the primary dashboards. Gmail also tracks IP reputation but has announced V1 IP dashboards for retirement. For most Gmail troubleshooting, domain reputation is where you start. Microsoft provides IP-level monitoring through SNDS but has no public domain reputation tool. This doesn't mean Microsoft ignores domain signals — it means you can't see them. Microsoft's filtering tends to be more aggressive on IP-level signals, making shared IP quality and blocklist status more critical for Outlook/Hotmail delivery. Yahoo monitors reputation by DKIM signing domain through Sender Hub Insights. No IP-level tool. Yahoo explicitly states that following their recommendations provides consistent reputation "regardless of which IP mail is sent from." For the full breakdown of what's IP-level vs domain-level, see IP vs Domain Reputation. IP and domain reputation are separate evaluations — different protocols, different tools, different portability. 1. IP reputation is tied to the sending server's IP address and reflects the behavior of everyone who sends from that IP. Domain reputation is tied to the From: domain and DKIM signing domain and follows your brand across infrastructure changes. 2. Protocols like PTR, SPF, and IP blocklists are inherently IP-level. DKIM, DMARC, BIMI, and List-Unsubscribe are inherently domain-level. Spam complaints, bounces, and spam trap hits are attributed to both. 3. Google Postmaster Tools provides both IP and domain reputation dashboards. Microsoft SNDS is IP-only. Yahoo Sender Hub Insights is domain-only. 4. When you change ESPs, domain reputation travels with you but IP reputation resets. When you change your From: domain, domain reputation resets but IP reputation is unchanged. 5. A common mistake is buying a dedicated IP to fix deliverability when the problem is domain reputation — a new IP does nothing for a damaged domain. How to Check Your Reputation Provider Tool What It Shows Gmail Google Postmaster Tools Domain reputation (High/Medium/Low/Bad), Compliance Status, IP reputation, spam rate, authentication rates Microsoft SNDS Per-IP reputation (Green/Yellow/Red), volume, trap hits Yahoo Sender Hub Domain-based insights, complaint rates, authentication status Cross-provider InboxAlly Spam Database Lookup Blocklist status across major lists If you're below a provider's data threshold (common for lower-volume senders), these tools may show no data. In that case, monitor what you can measure directly: complaint rates from your ESP, bounce rates, and blocklist status. Building vs Losing Reputation Reputation is asymmetric — it takes weeks or months of consistent, low-complaint sending to build, and it can be damaged in a single campaign. Building reputation: Consistent sending to engaged recipients over weeks/months Low complaint rates (below 0.1%) Low bounce rates (below 2%) Strong authentication (SPF + DKIM + DMARC passing) Gradual volume increases during warmup Damaging reputation: A single campaign with high complaint rates can drop you from "High" to "Low" in Google Postmaster Tools Hitting a spam trap — even once — signals a list quality problem that providers take seriously A volume spike without warmup looks like compromised infrastructure or spam behavior Going silent for months, then resuming at previous volume — providers treat you as effectively new again Recovery is possible but slow. It follows a similar pattern to initial warmup: reduce volume to your most engaged recipients, fix the root cause, and gradually rebuild. See reputation recovery for the full process. Why Sender Reputation Matters Sender reputation is a primary factor in inbox placement. A strong reputation means your emails go to the inbox by default. A damaged reputation means even legitimate, wanted emails may land in spam — and recipients who would have engaged never get the chance. The compounding effect is what makes reputation so critical: damaged reputation → spam placement → less engagement → further reputation damage. Breaking this cycle requires deliberate intervention, not just "sending better email." How InboxAlly Helps InboxAlly breaks the negative reputation cycle by generating consistent positive engagement signals through seed emails. Seeds open, read, and interact with your email — giving providers the behavioral data that signals a trusted sender. This is most valuable in three scenarios: during email warmup when you have no established reputation, during reputation recovery when you need to rebuild trust after a setback, and during steady-state sending to maintain the engagement baseline that sustains your reputation. --- ## IP vs Domain Reputation - URL: https://www.inboxally.com/docs/concepts/ip-vs-domain-reputation/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-12 - Description: IP reputation and domain reputation are separate evaluations — tied to different identifiers, measured by different tools, and portable differently when you change infrastructure. - Keywords: IP reputation, domain reputation, sender reputation, IP vs domain reputation, dedicated IP reputation, shared IP reputation, DKIM signing domain, ESP migration reputation > IP reputation is tied to the sending server's IP address and reflects the behavior of everyone who sends from that IP. Domain reputation is tied to the From: domain and DKIM signing domain and follows your brand regardless of which IP or ESP you send through. They are separate evaluations — you can have a clean IP with a damaged domain, or a strong domain on a problematic IP. IP vs Domain Reputation IP reputation and domain reputation are separate evaluations that mailbox providers perform independently. IP reputation is tied to the sending server's IP address. Domain reputation is tied to the From: header domain and DKIM signing domain. They are measured by different tools, built on protocols that are inherently IP-level or domain-level, and portable differently when you change infrastructure. IP and domain reputation are separate evaluations — different protocols, different tools, different portability. 1. IP reputation is tied to the sending server's IP address and reflects the behavior of everyone who sends from that IP. Domain reputation is tied to the From: domain and DKIM signing domain and follows your brand across infrastructure changes. 2. Protocols like PTR, SPF, and IP blocklists are inherently IP-level. DKIM, DMARC, BIMI, and List-Unsubscribe are inherently domain-level. Spam complaints, bounces, and spam trap hits are attributed to both. 3. Google Postmaster Tools provides both IP and domain reputation dashboards. Microsoft SNDS is IP-only. Yahoo Sender Hub Insights is domain-only. 4. When you change ESPs, domain reputation travels with you but IP reputation resets. When you change your From: domain, domain reputation resets but IP reputation is unchanged. 5. A common mistake is buying a dedicated IP to fix deliverability when the problem is domain reputation — a new IP does nothing for a damaged domain. The Core Distinction IP reputation reflects the behavior of everyone who sends from a given IP address. On a shared IP, you share that reputation with other senders. On a dedicated IP, the reputation is yours alone — but it starts from unknown, not neutral. Most providers throttle unknown IPs aggressively, which is why warmup exists. Domain reputation follows your brand. It's tied to the From: header domain and your DKIM signing domain (d= tag). Change ESPs, change IPs — domain reputation travels with you. A brand-new domain also starts from unknown — just like a new IP — and needs to build reputation through consistent, low-complaint sending before providers trust it at volume. These are independent evaluations. A clean IP won't save a damaged domain, and a strong domain can still be dragged down by a problematic IP. Subdomain isolation adds a practical lever: separating transactional mail (mail.brand.com) from marketing (promo.brand.com) lets you build and protect reputations independently. A spike in marketing complaints won't drag down your transactional delivery. How much isolation you actually get varies by provider — Google treats subdomains with more independence than some others, and a severely damaged parent domain can still cast a shadow. But for most senders, subdomain separation is the single most effective way to protect critical mail streams. What's Inherently IP-Level vs Domain-Level This distinction is structural — it follows from protocol specifications, not inferred from provider behavior. IP-level by definition — these are what you're managing when you warm up a new IP, investigate a blocklisting, or decide between shared and dedicated: PTR / Reverse DNS — maps IP to hostname (RFC 1035) SPF — authorizes sending IPs (RFC 7208). The record lives in domain DNS, but SPF evaluates the connecting IP. IP blocklists — Spamhaus SBL, CBL, XBL list IP addresses Microsoft SNDS — reports reputation per-IP Sending volume and rate — measured per-IP by receiving servers Domain-level by definition — these are what follow you when you migrate ESPs, and what you damage when you send to bad lists regardless of which IP you use: DKIM — signature tied to d= domain (RFC 6376) DMARC — policy evaluated per From: domain (RFC 7489). Note: SPF alignment for DMARC is a domain-level check even though SPF evaluation is IP-level. BIMI — brand logo tied to verified domain Google Postmaster Tools Compliance Status — evaluates per-domain List-Unsubscribe — domain-level compliance signal (RFC 8058) Attributed to both: Spam complaints, bounce rates, and spam trap hits are attributed to the IP that delivered and the domain that sent. The attribution mechanism itself illustrates the split — Gmail's feedback loop reports complaints by DKIM signing domain (domain-level), while Microsoft's JMRP reports by delivering IP (IP-level). IP and domain reputation are not the full picture. Modern providers also use per-recipient engagement — whether a specific user opens, reads, or deletes mail from a specific sender. IP and domain reputation set the baseline; engagement history between you and each recipient refines it. How to Monitor Each Provider IP Reputation Domain Reputation Gmail Postmaster Tools — IP Reputation (V1) Postmaster Tools — Compliance Status (V2) Microsoft SNDS — per-IP reputation, volume, traps No public domain-level tool Yahoo No dedicated IP tool Sender Hub Insights — domain-based (DKIM domain) Google provides both. Microsoft's public tooling is IP-only — but Microsoft absolutely uses domain signals internally for filtering. The gap is in monitoring visibility, not in what Microsoft evaluates. Yahoo is domain-only. Portability When you change... IP Reputation Domain Reputation ESP / sending provider Resets (new IPs) Travels with you Sending IP (same ESP) Resets for that IP Unchanged From: domain Unchanged Resets (new domain) DKIM signing domain Unchanged Affected This table answers the most common question in ESP migration: "Will my reputation follow me?" It depends on which reputation. One nuance: "travels with you" is directionally correct but not instant. During an ESP migration, providers re-evaluate your domain in the context of new sending infrastructure. Domain reputation follows, but expect a brief dip in delivery performance during the transition — especially if the new ESP's IPs are unknown to providers. When Dedicated IP Makes Sense (and When It Doesn't) A dedicated IP isn't a universal upgrade — it's a tool that requires specific conditions to work: Below ~50,000 emails/month: Stick with shared IP. You don't generate enough sending volume for providers to build a meaningful reputation profile. A dedicated IP at low volume stays permanently unknown — which is worse than a well-managed shared pool. Focus on domain reputation instead. 50,000–100,000+/month: Dedicated IP becomes viable if you can commit to a consistent warmup schedule and maintain steady volume. Gaps in sending reset progress. Most ESPs charge a monthly fee per dedicated IP — check your provider's pricing. High volume with multiple mail streams: Consider multiple dedicated IPs — one for transactional, one for marketing. Combined with subdomain isolation, this gives you independent reputation control per mail stream. The real decision: Dedicated IP gives you control over IP reputation but demands volume and consistency to maintain it. Shared IP outsources IP reputation management to your ESP — and on a strict ESP with good sender enforcement, shared pool quality can be better than a dedicated IP you can't properly warm. In both cases, domain reputation is yours to build or damage. Common Mistakes Buying a dedicated IP to "fix" deliverability when the problem is domain reputation. A new dedicated IP starts at unknown — providers will throttle it until you prove yourself through warmup. It does nothing for a damaged domain. Before buying a dedicated IP, check Google Postmaster Tools for domain reputation. If you're below Google's data threshold (common for lower-volume senders), look at complaint rates, bounce rates, and blocklist status instead — these are domain-level signals you can measure without GPT. If the domain is the problem, fix list hygiene, content, and engagement first. Migrating ESPs to escape a bad domain reputation. Domain reputation follows you. New ESP, same domain, same problem. If the domain is damaged, the fix is list hygiene and engagement — not a fresh set of IPs. Not checking the DKIM d= tag. Make sure your ESP signs with your domain (d=yourbrand.com), not theirs. This ensures DMARC alignment and gives you ownership of your domain reputation. Some ESPs use a shared signing domain by default — you may need to specifically request custom DKIM. How InboxAlly Helps InboxAlly's seed emails generate the engagement signals that build domain reputation. Two scenarios where this matters most: during an ESP migration, seeds keep domain-level engagement consistent while your new IPs are still unknown and throttled. During a dedicated IP warmup, strong domain reputation from seed engagement gives providers a reason to trust mail from an IP they haven't seen before — you're not starting from unknown on both dimensions at once. --- ## Spam Filters - URL: https://www.inboxally.com/docs/concepts/spam-filters/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Spam filters are automated systems used by mailbox providers to evaluate incoming emails and determine whether they should reach the inbox or be blocked. - Keywords: spam filters, email filtering, spam detection, content filtering > Spam filters are the gatekeepers of email. They evaluate sender reputation, authentication, content, and engagement patterns to decide whether your email reaches the inbox, lands in spam, or gets blocked entirely. Spam Filters Spam filters are automated systems operated by mailbox providers and email security services that analyze incoming emails across multiple dimensions — sender reputation, authentication, content, and recipient behavior — to determine whether an email should be delivered to the inbox, placed in spam, or rejected entirely. The multi-layered spam filtering pipeline that determines where your email lands. 1. Connection-level checks verify the sending IP is not blocklisted and has valid reverse DNS. 2. Authentication checks validate SPF, DKIM, and DMARC alignment. 3. Reputation checks evaluate the sender's historical domain and IP reputation. 4. Content analysis scans for spam patterns, suspicious URLs, and misleading content. 5. Engagement history reviews how recipients have previously interacted with this sender. 6. Based on all signals, the email is placed in inbox, promotions, or spam. How Spam Filters Work Modern spam filters are not simple keyword scanners. They use layered evaluation: Connection-level checks — Is the sending IP blocklisted? Does it have a valid reverse DNS? Authentication checks — Does the email pass SPF, DKIM, and DMARC? Reputation checks — What is the sender reputation of this domain and IP? Content analysis — Does the email contain spam patterns, suspicious URLs, or misleading content? Engagement history — Do recipients typically open, read, or mark this sender's emails as spam? Each mailbox provider runs its own filtering system. Gmail, Yahoo, and Microsoft all weight these factors differently. Common Spam Filter Triggers Missing or failing email authentication Low sender reputation High spam complaint rates Sending volume spikes without warmup URL shorteners or known-bad domains in links Excessive image-to-text ratio Misleading subject lines Why Understanding Spam Filters Matters You can't bypass spam filters — but you can work with them. Every factor spam filters evaluate is something you can influence through proper authentication, consistent sending behavior, and strong engagement. How InboxAlly Helps InboxAlly addresses the engagement component of spam filtering by generating positive engagement signals through seed emails. When spam filters see that real recipients consistently open and engage with your emails, they classify you as a legitimate sender — improving inbox placement. --- ## Mailbox Providers - URL: https://www.inboxally.com/docs/concepts/mailbox-providers/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-09 - Description: Mailbox providers are services like Gmail, Yahoo, and Microsoft Outlook that host email accounts and make inbox placement decisions for their users. - Keywords: mailbox providers, email service providers, Gmail, Yahoo Mail, Microsoft Outlook > Mailbox providers (Gmail, Yahoo, Microsoft, etc.) host recipient email accounts and control whether your emails reach the inbox. Each provider has its own filtering algorithms, reputation systems, and deliverability requirements. Mailbox Providers Mailbox providers are services that host email accounts for recipients — including Gmail, Yahoo Mail, Microsoft Outlook, and Apple Mail. They operate spam filters, reputation systems, and placement algorithms that determine whether incoming emails reach the inbox, land in spam, or are blocked. Major Mailbox Providers Gmail (Google) Largest global provider with over 1.8 billion users Weighs domain reputation heavily Uses tabs (Primary, Promotions, Social) for inbox organization Provides Postmaster Tools for sender visibility Yahoo Mail / AOL (Yahoo) Operated by Yahoo (now part of Yahoo Inc.) Requires one-click unsubscribe for bulk senders Offers Complaint Feedback Loop (CFL) for monitoring spam reports Microsoft Outlook / Hotmail (Microsoft) Includes Outlook.com, Hotmail, and Live.com domains Offers JMRP and SNDS for sender monitoring Focused Inbox separates important and non-important email Apple Mail (iCloud) Growing user base through Apple device ecosystem Mail Privacy Protection can mask open tracking Why Mailbox Providers Matter Each provider makes independent placement decisions. You may have strong inbox placement with Gmail but poor placement with Microsoft. Understanding each provider's requirements and monitoring tools is essential for consistent deliverability. How InboxAlly Helps InboxAlly maintains seed email addresses across all major mailbox providers. This generates positive engagement signals provider by provider, improving your sender reputation with each platform independently. --- ## Spam Complaints - URL: https://www.inboxally.com/docs/concepts/spam-complaints/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-12 - Description: Spam complaints occur when email recipients mark a message as spam, directly damaging the sender's reputation with mailbox providers. - Keywords: spam complaints, complaint rate, report spam, mark as junk > A spam complaint happens when a recipient clicks 'Report Spam' or 'Mark as Junk.' Even a small complaint rate can severely damage your sender reputation and inbox placement. Spam Complaints Spam complaints occur when email recipients manually mark a message as spam or junk in their mailbox. Each complaint is reported to the mailbox provider and counts against the sender's reputation, making it one of the most damaging negative signals in email deliverability. How Providers Report Complaints When a recipient clicks Report Spam, the complaint enters the provider's reputation system before being routed to the sender. Each provider handles this differently. Cross-provider comparison of spam complaint feedback loops — Gmail (aggregate), Yahoo (individual), Microsoft (both). 1. Recipient clicks Report Spam. 2. Provider records complaint internally. 3. Reputation impact calculated against total inbox-delivered volume. 4. Signal routed to sender via feedback loop if configured. Gmail provides aggregate spam rate and reputation dashboards through Postmaster Tools. Yahoo forwards individual complaint messages in ARF format via its CFL program. Microsoft offers both individual complaints via JMRP and IP-level dashboards via SNDS, managed through one portal. Complaint Rate Thresholds Mailbox providers track your complaint rate as a percentage of total emails delivered: Below 0.1% — healthy range, no impact 0.1% – 0.3% — warning zone, reputation may begin to decline Above 0.3% — critical, expect significant spam folder placement or blocking Google explicitly recommends keeping complaint rates below 0.1% and treats rates above 0.3% as a serious reputation signal. Common Causes of Spam Complaints Recipients who don't remember subscribing No clear or easy unsubscribe option Sending too frequently Irrelevant or poorly targeted content Purchased or scraped email lists Continuing to send after unsubscribe requests Why Spam Complaints Matter A single campaign with a high complaint rate can damage sender reputation that took months to build. Mailbox providers treat complaints as the strongest negative signal because they represent a direct recipient action — the person explicitly said "I don't want this." How InboxAlly Helps InboxAlly's seed emails never generate spam complaints. Instead, they generate positive engagement signals that offset the reputational impact of the occasional complaint from your regular list, helping maintain healthy sender reputation. --- ## Open Rate - URL: https://www.inboxally.com/docs/concepts/open-rate/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-09 - Description: Open rate is the percentage of delivered emails that recipients open, serving as a key engagement metric and deliverability signal. - Keywords: open rate, email open rate, open tracking, email metrics > Open rate measures what percentage of your delivered emails are opened by recipients. While not perfectly accurate due to tracking limitations, it remains a core metric for measuring email engagement and a signal mailbox providers use for reputation. Open Rate Open rate is the percentage of delivered emails that are opened by recipients, calculated as (unique opens ÷ emails delivered) × 100. It is one of the most widely tracked email metrics, used both as a performance indicator and as an input to mailbox provider reputation algorithms. How Open Rate Is Tracked Most email platforms track opens using a tiny invisible image (tracking pixel) embedded in the email. When the recipient's mail client loads this image, it registers as an open. Limitations Apple Mail Privacy Protection — pre-loads tracking pixels, inflating open rates for Apple Mail users Image blocking — some clients block images by default, underreporting opens Plain text emails — cannot include tracking pixels These limitations mean open rate is an approximate metric, not an exact count. What Is a Good Open Rate? Open rates vary significantly by industry and email type: Transactional emails: 40–60% Marketing emails: 15–25% Cold outreach: 10–20% More important than the absolute number is the trend — declining open rates signal a deliverability or engagement problem. Why Open Rate Matters for Deliverability Mailbox providers use their own internal open data (not your tracking pixel) as an engagement signal. Emails that are consistently opened contribute to stronger sender reputation. Emails that sit unopened contribute to weaker reputation and reduced inbox placement. How InboxAlly Helps InboxAlly's seed emails open and read every email they receive, generating real opens that mailbox providers register as positive engagement signals. This directly supports your open-rate-driven reputation metrics. --- ## Engagement Rate - URL: https://www.inboxally.com/docs/concepts/engagement-rate/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-09 - Description: Engagement rate is the overall measure of how actively recipients interact with your emails, combining opens, clicks, replies, and other interactions. - Keywords: engagement rate, email engagement, click rate, reply rate > Engagement rate is the composite measure of recipient interaction with your emails — encompassing opens, clicks, replies, and other actions. It's a broader metric than open rate alone and a stronger signal of email quality. Engagement Rate Engagement rate is the composite measure of how actively recipients interact with an email campaign, encompassing multiple actions — opens, clicks, replies, forwards, and reading time. It provides a more complete picture of email performance than any single metric alone. Components of Engagement Rate Engagement rate is typically calculated from multiple engagement signals: Open rate — percentage of recipients who opened the email Click-through rate (CTR) — percentage who clicked a link Reply rate — percentage who responded Read time — how long recipients spent with the email open Forward rate — percentage who shared the email Different platforms calculate engagement rate differently. Some weight clicks more heavily than opens; others include reply rate. Why Engagement Rate Matters Mailbox providers care about the full engagement picture, not just opens. A campaign with high opens but zero clicks tells a different story than one with moderate opens and strong click-through. High engagement rate: Strengthens sender reputation across all signals Improves inbox placement for future sends Indicates content relevance and audience-message fit Low engagement rate: Weakens reputation over time Leads to increased spam folder placement Signals a need to revisit content, targeting, or sending frequency How InboxAlly Helps InboxAlly's seed emails generate multiple types of positive engagement signals — not just opens, but reads and interactions that contribute to a strong composite engagement profile with mailbox providers. --- ## Email Authentication - URL: https://www.inboxally.com/docs/concepts/email-authentication/ - Section: Email Deliverability Concepts - Last Modified: 2026-05-29 - Description: Email authentication is the set of protocols — SPF, DKIM, and DMARC — that verify a sender's identity and protect against spoofing. - Keywords: email authentication, SPF, DKIM, DMARC, email security > Email authentication uses SPF, DKIM, and DMARC protocols to verify that an email actually comes from the domain it claims to come from. Proper authentication is a baseline requirement for inbox placement. Email Authentication Email authentication is the set of DNS-based protocols — SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) — that verify a sender's identity and protect recipients from spoofing and phishing. How SPF, DKIM, and DMARC work together to authenticate email and enforce domain policy. 1. SPF checks whether the sending IP is authorized by the domain's DNS record. 2. DKIM verifies the cryptographic signature matches the domain's public key. 3. DMARC checks that SPF and DKIM results align with the From domain. 4. If alignment passes, the email is authenticated. If it fails, DMARC policy determines the action — none, quarantine, or reject. 5. DMARC generates aggregate and forensic reports for the domain owner. DNS Records for Email — Complete Map Authentication protocols live in DNS. This diagram shows all eight records that affect email deliverability — where each one lives, what type it is, and whether it's required. All eight DNS records for email — where they live, what type they are, and whether they're required. 1. SPF: TXT record at @ listing authorized sending servers. 2. DKIM: TXT or CNAME record at selector._domainkey with cryptographic public key. 3. DMARC: TXT record at _dmarc setting authentication policy and reporting address. 4. MX: MX record at @ specifying inbound mail servers. 5. PTR: reverse DNS record set by IP provider mapping sending IP to hostname. 6. MTA-STS: TXT record at _mta-sts enforcing strict TLS for inbound email. 7. TLS-RPT: TXT record at _smtp._tls for TLS failure reporting. 8. BIMI: TXT record at default._bimi for brand logo display in supporting inboxes. The Three Authentication Protocols SPF (Sender Policy Framework) SPF specifies which mail servers are authorized to send email on behalf of your domain. It's a DNS TXT record that lists approved sending IPs. Our free SPF Record Generator helps you assemble a single, correctly ordered record that stays under the 10-lookup limit. DKIM (DomainKeys Identified Mail) DKIM adds a cryptographic signature to each email, allowing the receiving server to verify that the message hasn't been altered in transit and that it was authorized by the domain owner. DMARC (Domain-based Message Authentication, Reporting, and Conformance) DMARC ties SPF and DKIM together, telling mailbox providers what to do when authentication fails (none, quarantine, or reject) and where to send authentication reports. You can build a valid policy with our free DMARC Record Generator before publishing it in DNS. Once SPF, DKIM, and DMARC are in place, the natural next step is BIMI — which displays your brand logo in supported inboxes once DMARC is enforced. The free BIMI Record Generator includes a DMARC prerequisite check and logo validator, so it's a quick way to confirm you're ready. Why Authentication Matters As of 2024, Gmail and Yahoo require proper authentication for all bulk senders. Without it: Emails are more likely to be flagged by spam filters Sender reputation cannot be properly established Your domain is vulnerable to spoofing by bad actors Inbox placement rates suffer significantly Authentication is table stakes — it won't guarantee inbox placement on its own, but missing it will almost guarantee spam placement. How InboxAlly Helps InboxAlly works alongside authentication — it doesn't replace it. Once your email authentication is properly configured, InboxAlly's seed emails amplify the reputational benefit by generating positive engagement signals that build on the trust foundation authentication provides. --- ## Reputation Recovery - URL: https://www.inboxally.com/docs/concepts/reputation-recovery/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Reputation recovery is the process of rebuilding sender reputation after a deliverability setback such as blocklisting, high complaint rates, or spam folder placement. - Keywords: reputation recovery, email reputation repair, deliverability recovery, sender score recovery > Reputation recovery is the process of restoring your sender reputation after it's been damaged. It requires identifying the cause, fixing underlying issues, and gradually rebuilding trust with mailbox providers. Reputation Recovery Reputation recovery is the process of rebuilding a sender's email reputation after a deliverability setback — such as blocklisting, elevated spam complaint rates, or sustained spam folder placement — by addressing root causes, reducing sending volume, and gradually re-establishing positive engagement patterns. Common Causes of Reputation Damage High spam complaint rates — above 0.3% on a campaign Blocklist inclusion — landing on Spamhaus, Barracuda, or other blocklists Spam trap hits — sending to addresses designed to catch bad senders Sudden volume spikes — sending dramatically more email without warmup Poor list hygiene — high bounce rates from stale or purchased lists Authentication failures — broken SPF, DKIM, or DMARC The reputation recovery process — from diagnosis through gradual rebuild. 1. Identify the problem using Google Postmaster Tools, Microsoft SNDS, and blocklist lookups. 2. Diagnose the root cause — high complaints, spam traps, authentication failure, or list quality. 3. Fix the underlying issue — clean lists, repair authentication, remove problematic content, request delisting. 4. Reduce sending volume to most engaged recipients only. 5. Gradually rebuild volume while monitoring inbox placement and complaint rates at each stage. The Recovery Process 1. Identify the Problem Use tools like Google Postmaster Tools, Microsoft SNDS, and blocklist lookup services to diagnose what went wrong. 2. Fix the Root Cause Resolve the underlying issue — clean your list, fix authentication, remove problematic content, or get delisted from blocklists. 3. Reduce Volume Scale back sending to your most engaged recipients only. This concentrates positive engagement signals. 4. Rebuild Gradually Slowly increase volume over weeks, monitoring inbox placement and complaint rates at each step — similar to an email warmup. How InboxAlly Helps InboxAlly accelerates reputation recovery by generating consistent positive engagement signals through seed emails during the recovery period. This gives mailbox providers the behavioral data they need to reclassify you as a trusted sender, shortening the recovery timeline. --- ## Spam Folder Placement - URL: https://www.inboxally.com/docs/concepts/spam-folder-placement/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Spam folder placement occurs when mailbox providers route an email to the recipient's spam or junk folder instead of the inbox. - Keywords: spam folder, junk folder, spam placement, email going to spam > Spam folder placement means your email was delivered but placed in spam instead of the inbox. The recipient likely never sees it. It's the most common deliverability failure and is driven by sender reputation, engagement patterns, and content signals. Spam Folder Placement Spam folder placement occurs when a mailbox provider's filtering system routes an incoming email to the recipient's spam or junk folder rather than the primary inbox. The email is technically "delivered" but is effectively invisible to most recipients. The five categories of signals that determine whether your email reaches the inbox or lands in spam. 1. Authentication signals: SPF, DKIM, and DMARC pass or fail status. 2. Content signals: spam-like patterns, image-to-text ratio, misleading subject lines. 3. Link signals: suspicious URLs, URL shorteners, known-bad domains. 4. Sender reputation signals: historical engagement, complaint rates, bounce rates. 5. Infrastructure signals: IP reputation, reverse DNS, blocklist status. 6. All signals converge into a spam score that determines inbox or spam placement. Why Emails Land in Spam Mailbox providers route emails to spam based on: Weak sender reputation — the most common cause Low engagement signals — recipients don't open or interact with your emails Failed email authentication — SPF, DKIM, or DMARC failures High spam complaint rates — recipients have marked previous emails as spam Content triggers — spam-like patterns, suspicious links, or misleading subject lines Blocklisting — your domain or IP appears on a blocklist The Impact of Spam Placement Most recipients never check their spam folder. Once your emails start landing in spam: Open rates drop dramatically Engagement rates decline further Sender reputation continues to deteriorate The problem compounds — less engagement leads to more spam placement This negative spiral makes early detection and intervention critical. Detecting Spam Placement Monitor inbox placement rates through seed testing Watch for sudden drops in open rates Check Google Postmaster Tools for domain reputation changes Review Microsoft SNDS for IP reputation data How InboxAlly Helps InboxAlly directly combats spam folder placement. When seed emails in InboxAlly's network receive your message in spam, they move it to the inbox and engage with it — sending a powerful signal to the mailbox provider that your emails are wanted. Over time, this trains spam filters to deliver your emails to the inbox by default. --- ## Email Warmup - URL: https://www.inboxally.com/docs/concepts/email-warmup/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Email warmup is the process of gradually increasing sending volume on a new or dormant email domain or IP to establish sender reputation with mailbox providers. - Keywords: email warmup, IP warmup, domain warmup, warmup schedule > Email warmup is the process of slowly ramping up your sending volume on a new domain or IP address. It builds sender reputation gradually so mailbox providers learn to trust your emails before you send at full volume. Email Warmup Email warmup is the process of gradually increasing email sending volume on a new or dormant domain or IP address over a period of weeks, allowing mailbox providers to evaluate the sender's behavior and establish a positive sender reputation before full-volume sending begins. Why Warmup Is Necessary New domains and IP addresses have no sending history — no sender reputation. Mailbox providers treat unknown senders with suspicion. Sending a large volume from an unknown sender triggers spam filters and can result in immediate blocking. Warmup solves this by: Establishing a track record of legitimate sending Building positive engagement signals gradually Allowing mailbox providers to classify you as a trusted sender Preventing the reputation damage that comes from hitting filters at high volume Email warmup volume ramp — gradual increases over weeks to build sender reputation safely. 1. Week 1: Send 50–100 emails per day to most engaged recipients only. 2. Week 2: Increase to 200–500 per day, expanding to recent openers and clickers. 3. Week 3: Ramp to 1,000–2,000 per day with broader engaged segments. 4. Week 4: Scale to 5,000–10,000 per day with continuous monitoring. 5. Week 5+: Reach full target volume while monitoring placement and complaints. 6. Danger zone: ramping too fast triggers spam filters and damages the reputation being built. A Typical Warmup Schedule Week Daily Volume Strategy 1 50–100 Send to your most engaged recipients only 2 200–500 Expand to recent openers and clickers 3 1,000–2,000 Include broader engaged segments 4 5,000–10,000 Continue expanding with monitoring 5+ Full volume Ramp to target volume while monitoring metrics The exact schedule depends on your target volume and the mailbox providers you're targeting. Signs Warmup Is Working Consistent inbox placement above 90% Stable or improving open rates Spam complaint rates below 0.1% No blocklist appearances Positive domain reputation in Google Postmaster Tools How InboxAlly Helps InboxAlly accelerates warmup by providing seed emails that generate positive engagement signals from day one. Instead of relying solely on organic engagement from a small initial audience, InboxAlly's network ensures consistent opens and reads across major mailbox providers — giving your new domain or IP the behavioral data it needs to build sender reputation faster. --- ## List Hygiene - URL: https://www.inboxally.com/docs/concepts/list-hygiene/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: List hygiene is the practice of regularly cleaning and maintaining email lists to remove invalid, inactive, and risky addresses that damage sender reputation. - Keywords: list hygiene, email list cleaning, list verification, remove invalid emails, email bounce rate > List hygiene means keeping your email list clean by removing invalid addresses, inactive subscribers, spam traps, and duplicates. Poor list hygiene is one of the fastest ways to damage sender reputation and trigger spam filtering. List Hygiene List hygiene is the ongoing practice of cleaning and maintaining email lists by removing invalid addresses, inactive subscribers, spam traps, role-based addresses, and duplicates. It directly protects sender reputation and inbox placement by reducing bounces, complaints, and spam trap hits. Why List Hygiene Matters Every email sent to a bad address costs you — not just in wasted sends, but in reputation damage. Mailbox providers track your bounce rates, spam trap hits, and engagement ratios. A dirty list makes all three worse. Poor list hygiene leads to: High bounce rates — invalid addresses generate hard bounces that damage sender reputation Spam trap hits — old or recycled addresses become spam traps that flag you as a careless sender Low engagement rates — inactive subscribers drag down engagement signals, telling providers your email isn't wanted Blocklisting — sustained abuse signals can land your domain or IP on blocklists What to Remove Invalid Addresses Addresses that hard bounce — misspelled domains, non-existent mailboxes, or syntax errors. Remove immediately after the first hard bounce. Inactive Subscribers Recipients who haven't opened or clicked in 90+ days. Either re-engage them with a targeted campaign or suppress them from regular sends. Spam Traps Addresses that appear legitimate but exist solely to catch senders with poor list practices. You can't identify them directly — you prevent them through good hygiene. Role-Based Addresses Addresses like info@, admin@, sales@ that aren't tied to a person. They generate low engagement and higher complaint rates. Duplicates Sending the same person multiple copies increases complaint risk and wastes seed email capacity. How Often to Clean Every send: Remove hard bounces automatically Monthly: Suppress inactive subscribers (90+ days, no engagement) Quarterly: Run full list verification to catch degraded addresses Before any large campaign: Verify the list to avoid spike-related reputation damage How InboxAlly Helps InboxAlly's built-in list verification lets you upload a CSV and remove invalid, inactive, and duplicate addresses before sending. Clean lists mean more of your sends reach real recipients who engage — strengthening sender reputation and improving inbox placement. --- ## Spam Traps - URL: https://www.inboxally.com/docs/concepts/spam-traps/ - Section: Email Deliverability Concepts - Last Modified: 2026-03-10 - Description: Spam traps are email addresses used by mailbox providers and blocklist operators to identify senders with poor list practices. - Keywords: spam traps, honeypot email, recycled spam trap, pristine spam trap, email trap > Spam traps are email addresses operated by mailbox providers and anti-spam organizations to catch senders who use purchased lists, scrape addresses, or fail to maintain list hygiene. Hitting a spam trap can severely damage sender reputation. Spam Traps Spam traps are email addresses maintained by mailbox providers, blocklist operators, and anti-spam organizations specifically to identify senders with poor list acquisition or maintenance practices. They look like real addresses but are never used by real people — any email sent to them is, by definition, unsolicited. Types of Spam Traps Pristine Traps Addresses that have never belonged to a real person. They're created solely to catch senders who scrape websites, purchase lists, or use dictionary attacks to guess addresses. Hitting a pristine trap is the strongest signal of bad list practices. Recycled Traps Addresses that once belonged to real users but were abandoned and repurposed by the provider as spam traps. Common examples include former employees at companies or old free email accounts. Hitting recycled traps indicates you're not maintaining list hygiene — you're sending to addresses that haven't engaged in months or years. Typo Traps Addresses at misspelled domains (e.g., user@gmial.com) that are monitored for incoming mail. These catch senders who don't validate email addresses at the point of collection. Why Spam Traps Are Dangerous A single spam trap hit can: Immediately damage sender reputation with the operating provider Trigger blocklist inclusion (Spamhaus, Barracuda, and others operate trap networks) Cause sustained spam folder placement across multiple mailbox providers Take weeks or months to recover from through reputation recovery The damage is disproportionate because spam traps signal systemic problems with how you acquire and maintain your list — not just a one-off mistake. How to Avoid Spam Traps You can't identify spam traps directly — they're designed to be indistinguishable from real addresses. Prevention is the only strategy: Never purchase or scrape email lists — this is the most common source of pristine trap hits Use confirmed opt-in (double opt-in) — ensures every address is real and intentional Validate addresses at collection — catch typos before they enter your list Remove inactive subscribers — anyone who hasn't engaged in 90+ days could be a recycled trap Run regular list verification — catch invalid and risky addresses before sending Monitor bounce rates — rising bounces often precede trap hits How InboxAlly Helps InboxAlly's list verification removes invalid and risky addresses before they can cause damage. Combined with seed emails that generate consistent positive engagement signals, InboxAlly helps maintain the strong sender reputation that insulates you from the occasional trap hit.