Outlook/Hotmail is no longer blocking my mail server

Original Article ↗ Hacker News Discussion ↗

Struggles with getting self-hosted or small-provider email delivered to Outlook/Hotmail highlight how aggressively Microsoft and other large providers fight spam, often by silently dropping or IP-blocking legitimate mail from VPS ranges. Commenters trade configuration tips (SPF, DKIM, DMARC, reputation building, smart hosts) and workarounds like using transactional email services, while an engineer from Microsoft’s anti-spam team explains why proactive, conservative blocking is effectively baked into their system. The conversation broadens into concerns about centralization of email, the difficulty of competing with big providers’ spam filters, and proposals such as government-issued email addresses versus strictly market-based solutions.

Deliverability vs. Spam Handling

  • Distinction between spam-folder placement, hard bounces, and silent drops:
    • Many see mail silently landing in spam or being dropped without notice, especially by large providers.
    • Some prefer bounces for senders (clear failure signal), others prefer aggressive spam filtering for recipients (less inbox noise).
  • “Accept then drop” behavior (seen at Gmail and Outlook in some cases) is widely criticized as violating early email norms (“deliver, defer, or bounce, but don’t silently discard”).

Self-Hosting Email: Mixed Experiences

  • Some report years of trouble-free self-hosting (especially in Europe, on stable IPs).
  • Others repeatedly hit opaque blocks, especially with Outlook/Hotmail and Office 365, despite correct SPF/DKIM/DMARC and clean history.
  • Low-volume personal servers are particularly vulnerable: they can’t easily build reputation, and delisting cycles are time‑consuming.

Microsoft/Outlook Anti-Spam Behavior

  • Outlook sometimes outright blocks or silently discards email, including from long‑clean IPs and non-spammy content.
  • An engineer explains:
    • Proactive IP blocking is deliberate; if delisting is easy, spammers abuse it.
    • Some filtering (e.g., SmartScreen) can trigger silent drops; message-body inspection is limited for privacy/compliance reasons.
    • Systemic issues (e.g., subnet-wide blocking, high false positives for small senders) are acknowledged but hard to fix; tools like SNDS are seen as outdated and unreliable by some users.
  • Users complain about:
    • Entire netblocks (e.g., Linode, DigitalOcean ranges) getting blocked.
    • Opaque and slow delisting processes; escalation rituals are quasi‑“magic spells”.

Cloud Hosts, Blocklists, and IP Reputation

  • Cheap VPS providers (especially some named ones) are widely seen as major spam sources; others note they have tightened SMTP and abuse controls but remain tainted.
  • Some admins now block such providers entirely, even for web traffic.
  • Disagreement whether this is justified “guilt by association” or overreach that punishes careful tenants.

Workarounds and Tools

  • Common workaround: relay outbound mail through transactional services (SES, Mailgun, Mailpace, SMTP2GO), while keeping inbound self-hosted.
  • Testing and configuration tools (mail-tester, DMARC learning sites, MECSA) are praised for uncovering misconfigurations (e.g., missing DKIM).

Centralization, Capitalism, and Email Governance

  • Many argue big providers offer vastly better spam filtering but at the cost of de facto gatekeeping and weakened decentralization.
  • Debate over whether consolidation is an inherent outcome of capitalism or a result of weak antitrust and regulatory choices.
  • Some foresee free webmail shrinking as data-monetization becomes harder; others question willingness/ability of poorer users to pay.

Government-Provided Email & Privacy

  • Proposal: one lifelong, government-backed email per citizen as a stable digital contact and recovery channel.
  • Supporters: aligns with government’s role in physical mail and identity, could reduce corporate lock‑in and account‑lockout risks.
  • Critics: fear surveillance, political misuse, mandatory adoption, and difficulty of recovery without new security problems.
  • Real-world attempts (e.g., European national email systems, Germany’s De‑Mail, Estonia’s address-forwarding) show mixed success and usability/privacy tradeoffs.

Reform Ideas and Spam Economics

  • Suggestions include:
    • Per-email micro‑fees (like stamps) or reputation‑linked costs to deter spam.
    • Reputation or KYC-based closed networks with strong identity.
  • Counterarguments:
    • Spammers treat fees as operating costs; costs mostly burden legitimate, low‑margin or personal communication.
    • Historical and current experience (physical mail, Twitter “blue checks”) suggests nominal fees don’t eliminate abuse, just reshape it.