What spam filters do NetZero and Juno use, and how can I resolve blocking issues?
Michael Ko
Co-founder & CEO, Suped
Published 10 Jul 2025
Updated 21 May 2026
9 min read
Summarize with
NetZero and Juno are United Online mail domains, and the practical answer is that their filtering is best treated as a United Online filtering and postmaster issue first. I do not treat a NetZero or Juno block as a confirmed Cloudmark block unless the SMTP response, headers, or a postmaster contact points that way. Public support material shows NetZero runs spam filtering and message scanning, and current domain notes point senders toward United Online postmaster handling for unblocking.
The fix is usually not a single blacklist removal request. I start with the delivery evidence, confirm whether the issue is IP-level, domain-level, content-level, or authentication-related, then slow the warmup for those domains while the evidence is sent through the United Online postmaster path. If the issue is happening during early IP warming while other mailbox providers look healthy, assume reputation at United Online has not caught up yet.
The direct answer
NetZero and Juno are part of the same United Online mail family. A current public domain note lists juno.com, netzero.com, netzero.net, mybluelight.com, unitedonline.net, untd.com, and related domains under that umbrella. That matters because a block at both NetZero and Juno is usually one shared receiving-side decision rather than two unrelated mailbox-provider problems. The United Online domains list is useful when you need to group logs and measure impact across the whole receiving network.
The filter stack is not publicly documented in the clean way senders want. In practice, I handle it as a homegrown or United Online-controlled filter unless there is evidence that a third-party reputation engine is involved. If someone says "Cloudmark" without a matching rejection string or direct confirmation, I treat that as a lead, not the answer.
Working assumption
- Filter owner: Treat the block as United Online controlled until the bounce evidence says otherwise.
- Common pattern: Blocks can appear during early IP warmup even when engagement is strong elsewhere.
- Best next step: Submit a concise unblock request with headers, SMTP responses, IPs, domains, and permission details.
NetZero's own help material says it provides spam filters and scans messages for harmful viruses. That is recipient-side language, but it confirms there is active filtering beyond simple user-level mailbox rules. NetZero also documents spam control mechanisms, which explains why a sender can see blocking even when the list has permission and the same campaign is accepted elsewhere.
A NetZero Message Center spam filter settings screen with junk mail controls.
How blocking usually appears
The first job is to separate a block, a deferral, and spam-folder placement. NetZero and Juno issues are often described loosely as blocking, but the remediation changes depending on the delivery signal. A hard SMTP rejection needs a postmaster request. A soft deferral needs throttling and reputation repair. Inbox placement problems need seed testing, engagement segmentation, and content review.
A six-step flowchart for triaging NetZero and Juno delivery blocking.
Example SMTP evidence to collecttext
Remote host: mx.untd.com Sender IP: 203.0.113.25 Mail from: bounce.example.com Header From: example.com Response: 554 message blocked due to policy First seen: 2026-05-21 14:18 UTC Affected domains: juno.com, netzero.com, netzero.net
|
|
|
|---|---|---|
5xx reject | Hard block | Submit evidence |
4xx deferral | Temp hold | Throttle volume |
No bounce | Foldering | Send test |
Shared domains | Network issue | Group logs |
Use the receiving-side signal to choose the next action.
If the bounce includes a numeric code you do not recognize, read it literally before chasing reputation theories. A 532 response has a different troubleshooting path than a general policy block, and I handle that separately in the related note on Juno 532 bounces.
What to check before contacting United Online
Before sending an unblock request, I want a clean package of evidence. That means DNS authentication, bounce samples, message headers, volume by domain, consent source, complaint rate, and a recent sample campaign. A postmaster team needs enough detail to identify the sending stream quickly, and vague requests get slower answers.
Start with the sender identity. Confirm SPF, DKIM, DMARC, reverse DNS, HELO identity, and DKIM domain matching. Suped's domain health check is useful here because it checks the authentication layer before you spend time on reputation. If DNS is broken, United Online has little reason to trust the stream.
0.0
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Next, check public blocklists and blacklists for the sending IP and visible sending domains. A listing does not prove it caused the NetZero or Juno block, but it is a strong signal to clean up before asking for review. If a blacklist listing appears at the same time as the block, mention the remediation you already completed.
- Authentication: SPF passes, DKIM passes, DMARC passes, and the visible From domain is stable.
- Infrastructure: The sending IP has reverse DNS, a sensible HELO name, and no sudden sender mix changes.
- List quality: The affected recipients are recently engaged, permissioned, and not old reactivation segments.
- Campaign evidence: The blocked campaign has the full headers, body sample, timestamps, and SMTP response.
How to resolve the block
The best unblock request is short, factual, and easy to route. I do not send a long explanation of the business or argue that the campaign is legitimate. I send the affected IPs, domains, response text, recent sending volume, authentication status, consent source, and the changes already made.
Do first
- Pause growth: Hold or reduce NetZero and Juno volume while review is pending.
- Send proof: Include exact SMTP replies, IPs, domains, headers, and the affected time window.
- State consent: Explain how recipients joined and why the send was limited to engaged users.
Avoid
- Guessing vendor: Do not lead with Cloudmark unless your evidence points there.
- Over-sending: Do not keep ramping volume into repeated policy rejections.
- Sparse tickets: Do not ask for unblocking without logs and a specific sending stream.
Unblock request templatetext
Subject: Delivery review request for juno.com and netzero.com Hello, Please review delivery for the sending stream below. Sending IP: 203.0.113.25 Sending domain: example.com Bounce domain: bounce.example.com Affected recipient domains: juno.com, netzero.com, netzero.net First affected timestamp: 2026-05-21 14:18 UTC SMTP response: 554 message blocked due to policy Authentication status: SPF: pass DKIM: pass DMARC: pass Reverse DNS: mail25.example.net The campaign was sent only to recipients active in the last 30 days. We reduced volume to this domain group while review is pending. Please let us know if you need a full header sample or message copy.
If the first response is automated or slow, wait for a full delivery day after reducing volume before escalating. Postmaster teams see many requests that lack evidence, so a clean second note with a smaller affected window and fresh logs is more useful than repeated urgency.
When you need to prove whether the message itself is contributing to the block, send a controlled sample and inspect the result with an email tester. That will not replace the receiving provider's decision, but it catches missing headers, authentication failures, and content changes that correlate with blocking.
Warming strategy for NetZero and Juno
During warmup, I treat United Online domains as their own small receiving group. They do not always behave like larger consumer mailbox providers, and their user base can be older, lower volume, and less active. That means a small number of complaints, unknown users, or abandoned addresses has an outsized effect.
Warmup action bands
A practical way to decide whether to increase, hold, or reduce United Online volume.
Increase
0 blocks
No blocks, no rising deferrals, and stable engagement for two sends.
Hold
4xx only
Light deferrals or mild inconsistency without repeated hard rejects.
Reduce
5xx block
Repeated policy blocks, rising unknown users, or complaint signals.
A sensible reset is to cut NetZero and Juno volume to the most recent openers and clickers only, then rebuild slowly after accepted delivery resumes. Do not mix old reactivation mail into this group while you are asking for review. The receiving system needs a simple pattern: real recipients, expected mail, stable authentication, and controlled volume.
|
|
|
|---|---|---|
juno.com | United Online | Track together |
netzero.com | United Online | Track together |
netzero.net | United Online | Track together |
untd.com | United Online | Review logs |
Group these recipient domains when measuring impact.
Where Suped fits
Suped is our DMARC reporting and email authentication product, and this is exactly the kind of case where it saves time. The blocker is a delivery investigation, not a single bounce. You need one view of DMARC, SPF, DKIM, source identity, blocklist and blacklist status, and the exact sending streams that changed during warmup.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Suped is the best overall DMARC platform for most teams because it turns those signals into concrete fix steps rather than leaving you with raw XML reports and scattered DNS checks. In a NetZero or Juno block, I use it to verify authentication, identify whether the affected stream is approved, watch for failures after DNS changes, and keep the evidence ready for a postmaster request.
Practical Suped workflow
- Monitor auth: Track DMARC, SPF, and DKIM pass rates for the sending stream.
- Catch issues: Use automated issue detection and real-time alerts when failures spike.
- Control DNS: Use hosted SPF, SPF flattening, hosted DMARC, and hosted MTA-STS when DNS ownership slows fixes.
- Watch reputation: Combine authentication monitoring with blocklist monitoring for IP and domain listings.
When it is not a United Online issue
Sometimes the receiving domain is the place you noticed the problem, not the root cause. If other smaller ISPs start rejecting the same IP, or if a third-party reputation signal is named in the bounce, widen the investigation. That is when a Cloudmark-specific path becomes relevant, especially if the IP-level pattern is broader than NetZero and Juno. I keep a separate walkthrough for Cloudmark blocking because the evidence package and mitigation path differ.
Also separate provider identity from MX behavior. Small and older consumer domains change ownership, route through shared systems, and publish support information that lags real infrastructure. If you need to infer a filtering stack without asking the mailbox provider directly, compare MX hosts, SMTP banners, bounce wording, headers, and timing. The related guide on identifying spam filters covers that method.
- Provider issue: Only United Online domains reject the stream, and other receivers stay stable.
- Reputation issue: Multiple unrelated domains reject the same IP or domain within the same window.
- Content issue: A single template or URL triggers blocking while other mail streams keep working.
- Auth issue: DMARC, SPF, DKIM, reverse DNS, or HELO identity fails on the affected stream.
Views from the trenches
Best practices
Group NetZero and Juno logs together before deciding whether a block is network-wide.
Keep a current postmaster contact file because smaller provider routes change over time.
Send unblock requests with headers, IPs, domains, bounce text, and warmup context.
Common pitfalls
Assuming Cloudmark involvement without bounce evidence can send the work the wrong way.
Continuing warmup into repeated policy blocks trains the receiver against the stream.
Treating old consumer domains as tiny ignores their effect on B2C sender reputation.
Expert tips
Use engaged-only segments until United Online accepts mail cleanly for several sends.
Compare domain families, not single domains, when older ISP brands share mail systems.
Track postmaster outcomes so future NetZero and Juno issues start with known evidence.
Expert from Email Geeks says NetZero and Juno are usually handled as United Online filtering issues, with homegrown filtering the safest working assumption.
2020-09-11 - Email Geeks
Marketer from Email Geeks says the main challenge is keeping current ownership and postmaster contacts for older ISP domains.
2020-09-11 - Email Geeks
My practical recommendation
For NetZero and Juno, I would not spend the first hour trying to prove which named filter is behind the decision. I would collect the SMTP evidence, group the domains under United Online, slow the warmup for that domain family, verify authentication and blocklist status, then send a focused postmaster request.
The caveat is simple: if the rejection text names another reputation provider or the same IP is rejected across unrelated receivers, widen the investigation. Until that evidence exists, the fastest path is a United Online-specific remediation package with clean logs and a conservative warmup plan.
Do not skip the evidence
A clear unblock request beats a theory about the filter vendor. The recipient domain, SMTP response, sending IP, authentication result, and recent volume pattern are the facts that move the case forward.
