Safe Sender Continues Going to Outlook Junk

2026-11-18T18:20:21.99+00:00

Safe Sender Continues Going to Outlook Junk

I receive legitimate voicemail notifications from Home Telecom at ******@message.homesc.com. Each message includes a WAV attachment containing the voicemail.

Every one of these messages is sent to Outlook Junk despite my having:

  • Added the exact email address to Safe Senders
  • Added the entire message.homesc.com domain to Safe Senders
  • Added the sender as a contact
  • Repeatedly selected Not Junk
  • Created an Outlook rule to move the messages to my Inbox

Nothing has worked.

I'm wondering if there is some server-side filtering taking precedence over my Safe Sender settings, possibly because of the WAV attachment or the way Home Telecom's email server is authenticated.

Is there a way to see exactly why Outlook classified one of these messages as Junk, or another way to permanently allow this specific sender without reducing spam protection for everything else?

Outlook | Web | Outlook.com | Settings
0 comments No comments

2 answers

Sort by: Most helpful
  1. EmilyS_726 34,570 Reputation points Volunteer Moderator
    2026-11-19T02:03:55.97+00:00

    The email was rejected on server level before it gets to your mail box, meaning, it didn't even have the chance to check your safe sender list.

    The reason for rejection is because this sending domain doesn't have DMARC, SPF or DKIM set up at all on their end. Sender is responsible for setting those up.

    User's image

    Was this answer helpful?


  2. AI answer

    2026-11-18T18:21:49.98+00:00

    Check Blocked senders and domains for a conflicting entry first; if none exists, inspect the message headers for classification and authentication clues, then report the persistent false positive to Outlook.com support and Home Telecom.

    1. Check for a conflicting blocked entry

    You have already exhausted Safe Senders, contacts, Not junk, and Inbox rules, so do not recreate those settings.

    1. In Outlook.com, open Settings → Mail → Junk email.
    2. Under Blocked senders and domains, look for:
      • The exact voicemail sender address.
      • message.homesc.com.
      • Any broader Home Telecom domain that could match it.
    3. Remove any matching entry and select Save.
    4. Test with a newly generated voicemail notification.

    A blocked sender/domain is routed directly to Junk, while Safe Senders is intended to prevent that routing.^1^

    2. Inspect the message headers

    Outlook.com does not necessarily disclose its complete internal spam score or a plain-language reason, but the full headers can expose useful classification and authentication evidence.

    1. Open one affected message in Junk Email.
    2. Select More actions (...) → View → View message details.
    3. Copy the complete header to a text editor.^2^
    4. Search for:
      • Authentication-Results
      • X-Forefront-Antispam-Report
      • X-Microsoft-Antispam
      • Return-Path
      • From:

    If Microsoft anti-spam fields are present, these values can provide clues:

    • SFV:SFE — the user's Safe Senders entry was recognized.
    • SFV:SPM — spam filtering classified the message as spam.
    • CAT:SPM, CAT:BULK, CAT:PHSH, or CAT:SPOOF — category assigned to the message.
    • Authentication-Results — inspect spf=, dkim=, dmarc=, and, if present, compauth=.
    • BCL — a bulk-mail indicator.

    Microsoft documents these fields for cloud organizations, but consumer Outlook.com does not guarantee that every field will be present or that headers will reveal every internal signal.^3^ Do not rely on SCL alone: in Microsoft’s cloud filtering stack, it does not by itself determine the final spam category or action.^4^

    Redact your address, message IDs, IP addresses, and other personal data before posting headers publicly.

    3. Act on what the headers show

    • SPF, DKIM, DMARC, or composite authentication fails: Send the complete headers privately to Home Telecom and ask its mail administrator to investigate the voicemail system’s outbound authentication and alignment.
    • Spam, bulk, spoof, or phishing classification appears despite successful authentication: Treat this as a persistent Outlook.com false positive. Report it through Outlook.com: select Help on the menu bar, describe the problem, and continue to Still need help? → Yes.^5^
    • The header shows SFV:SFE but the message still lands in Junk: Include that specific evidence in the support report because it indicates the Safe Senders entry was recognized but another classification or protection may have determined the final placement.
    • No useful verdict fields appear: Provide Outlook.com support with the unmodified header, arrival time, sender address, and a statement that the address and domain are already safelisted and absent from the blocked list.

    The WAV attachment might contribute to content-based classification, but its presence alone does not establish the cause. Home Telecom can isolate that possibility by sending two otherwise equivalent test notifications—one with the WAV attachment and one without—and comparing delivery and headers.

    4. Sender-side permanent remediation

    If the evidence points to authentication, IP/domain reputation, or repeated Outlook.com false positives, the durable fix is sender-side. Home Telecom should review its SPF and sending-IP configuration, reverse DNS, reputation, and complaint rates, then use Microsoft’s Outlook.com Sender Support services or issue-submission process.^6^

    An ordinary Outlook.com Inbox rule is not a reliable bypass: messages can be classified and moved to Junk before Inbox rules process them.^7^ Microsoft 365 admin controls such as Defender submissions, message trace, anti-spam policies, and transport rules are not available to a personal Outlook.com mailbox.


    References

    1. Block or allow (junk email settings) | Microsoft Support
    2. View internet message headers in Outlook
    3. Anti-spam message headers in cloud organizations
    4. Spam confidence level (SCL) in Microsoft 365
    5. Safe Senders in Outlook.com | Microsoft Support
    6. Sender Support in Outlook.com | Microsoft Support
    7. How to block a domain before it hits Outlook.com junk folder? - Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.