Urgent.News

What's breaking now, across thousands of outlets.

Tech

Gmail bounced everything the relay sent: three broken auth mechanisms and a silent OpenDKIM

Short answer: Three independent mechanisms were broken at once, and fixing any one of them changed nothing visible. The domain had no v=spf1 record (only a dead SenderID one), the PTR resolved forward to a different server, and OpenDKIM was signing nothing because KeyTable and SigningTable were attached as refile: while their contents were in plain two-column format. That last one cost the most…

Three fundamental issues caused Gmail to reject the relay's emails: a missing SPF record, incorrect PTR record, and OpenDKIM not signing the emails. The domain lacked a v=spf1 record, the PTR resolved to a different server, and OpenDKIM failed to sign the emails due to KeyTable and SigningTable being attached as refile. The Postfix server on a legacy container also had incorrect InternalHosts configuration, and the mail log did not reveal any DKIM-Signature.

To resolve the issues, the PTR needed to be changed to match the A record, Postfix myhostname should match the PTR, and the SPF record should be corrected.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Binary Search Trees

Why should you care? Imagine you have thousands or millions of numbers and frequently need to: Search for a value Insert new values Delete existing values Keep values organized An unsorted array may…

Subdomain Takeover Severity Comes From Security Context, Not the Exploit Mechanism

Subdomain Takeover Severity Comes From Security Context, Not the Exploit Mechanism saostatic.uber.com pointed to an unregistered CloudFront distribution.

  • Severity of subdomain takeover depends on security context, not exploit mechanism.
  • Dangling CNAME can lead to SSO bypass across all services for a domain.
  • 4-question framework aims to address triage failure in classification of critical bugs.

Stop Hand-Partitioning Disks: Practical systemd-repart on Linux

Stop Hand-Partitioning Disks: Practical systemd-repart on Linux You ship a minimal OS image. The target disk is 64 GB, 256 GB, or 2 TB. Root is still 8 GB. Swap does not exist.

  • systemd-repart simplifies disk partitioning for Linux OS images
  • Configurations defined in repart.d/.conf files, no fragile installer hooks
  • Incremental and idempotent tool, operates on GPT disks

Your agent orchestrator is a black box. Mine is a folder.

Status: experimental. I started Agent Board last night. The protocol will probably change. There is a point with agent orchestration software where you stop feeling like you are shipping software and…

  • Agent Board presents projects as folders with Markdown files for each task.
  • Five status columns - todo, doing, review, blocked, and done - track ticket progress.
  • Explicit messaging system enables agents to communicate about each ticket.

More from Sunday 6 September →