Skip to content

iCoreHosting Official Knowledgebase Article Structure

Why Anti-Spam Systems Cannot Block All Scam Emails 2

Service Direction / Introduction / Scope

Scammers change their wording, sender, links and files to avoid detection. Filters also need to avoid blocking genuine business mail. Combine filtering with updates, careful review and independent verification.

This guide covers layered protection against scam email.

Service Transparency

Filters balance detection against the risk of blocking genuine business mail. New patterns, compromised senders, changing links and difficult-to-inspect files can evade checks. Available security features depend on your service and configuration.

Definitions

  • Layered protection: Several complementary safeguards, such as filtering, device security and independent verification.
  • Allow list: An exception that permits selected senders or domains; it must be used carefully.
  • Quarantine: A holding area for messages awaiting review, where the service provides one.

Description of Content / Step-by-Step Guide

  1. Keep protection current
    • New wording and domains may evade old rules.
    • Keep filtering and device security updated; report suspicious examples.
  2. Review before tightening rules
    • Aggressive rules can block genuine invoices or customer mail.
    • Check quarantine and use allow lists carefully, only when justified.
  3. Check the request itself
    • A compromised real mailbox may pass SPF, DKIM and DMARC.
    • Review the sender, reply-to address and purpose of the message.
  4. Open trusted portals directly
    • Links can redirect or change after delivery.
    • Use trusted bookmarks and pay attention to browser security warnings.
  5. Verify unexpected attachments
    • New, encrypted or compressed files may be hard to inspect.
    • Confirm the file through another channel and keep endpoint security updated.
  6. Build safe habits
    • Use strong unique passwords and two-step verification where available.
    • Verify payment or access requests and report suspicious mail privately.

Important Note

HTTPS protects the connection to a website. It does not prove that an email, website owner or business request is trustworthy. No single security check guarantees safety.

Common Mistakes

  • Making rules very aggressive without reviewing quarantine.
  • Allow-listing an unknown domain to bypass a warning.
  • Assuming HTTPS or successful email authentication guarantees that content is safe.

Responsibility Breakdown

Customer / organization: Review suspicious messages, protect credentials and verify unusual requests through trusted contacts. Maintain appropriate internal approval and device-security procedures.

iCoreHosting: Review reported hosting-email or filtering issues within the applicable service scope using the information provided.

Third parties: External email providers, software vendors and business contacts control their own systems and must independently confirm requests relating to them.

Limitations

No filter or guide can guarantee that every scam is detected. Authentication, familiar branding or a clean scan is not proof of a genuine request. This guidance does not guarantee prevention, recovery or a particular investigation outcome.

Support Information

Contact iCoreHosting Support through the official channel. Include the affected address, approximate date and time, a short description and full email headers where available. Share sensitive evidence privately; never send your password or OTP.

FAQ

Why do new scams evade rules?
Their wording, domains or files may differ from known patterns.

Does HTTPS mean a website is trustworthy?
No. It protects the connection, not the truth of the website or request.

Can scanning guarantee an attachment is safe?
No. New, encrypted or compressed files may be difficult to inspect. Verify unexpected files independently.

Use Case

Situation: A familiar-looking invoice includes an unexpected compressed attachment and urges immediate action.

Action: Do not open it immediately. Confirm the file through a known channel and follow your organization’s device-security procedures.

Expected result: Independent review reduces the chance of acting on an unverified attachment.

Summary

Keep protections updated, review suspicious messages and verify sensitive requests. Filters, device security and careful human review work together.