Why mixing transactional and marketing emails on one domain hurts deliverability

·1 views

Sending all email types from a single domain means transactional messages like password resets share a sender reputation with marketing and cold outreach campaigns. When a poorly performing marketing send damages that shared domain reputation, critical transactional emails can begin landing in spam, even though the two systems are otherwise unrelated. Email receivers evaluate the From: domain as a unified history, making no distinction between a wanted account alert and an unsolicited bulk campaign. Experts recommend splitting email traffic across separate subdomains by risk profile, with cold outreach assigned an entirely separate registered domain to contain reputation damage. Proper DMARC configuration using the sp= tag, along with subdomain-specific SPF records and DKIM keys, is essential to make this separation effective.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Fake job interviews used to deliver malware and drain crypto savings

Microsoft's Defender Experts team documented a cyberattack campaign called Contagious Interview, active since at least December 2022, in which threat actors impersonate recruiters from crypto or AI firms to target job seekers. The attack is designed to reach the technical assessment stage, where candidates are socially conditioned to run unfamiliar code without suspicion. Victims are typically instructed to clone and execute a malicious NPM package from seemingly legitimate platforms like GitHub or GitLab. In one case reported by BBC World Service on 4 September 2026, a UK job seeker lost £18,000 in cryptocurrency savings within hours of completing such an assessment. Microsoft advises that no legitimate employer requires candidates to run unknown code on personal machines, and recommends using isolated virtual environments for coding tests.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Contributes Recent-Papers Section to Harvard's Open-Source ML Textbook

A developer successfully merged a pull request (PR #1962) into the Harvard CS249r Machine Learning Systems open-source textbook, hosted on GitHub with over 28,400 stars. The contribution addressed an existing issue requesting improvements to the StaffML section of the book. The developer built a new React component to display a curated list of recent papers on the About page, matching the project's existing design conventions. The pull request passed review by two project maintainers before being accepted. The textbook is used by thousands of machine learning students and practitioners worldwide.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Critical GitLab CVE-2026-85706 Exposes Over 1.2M Instances to File Read Attacks

A maximum-severity vulnerability, CVE-2026-85706, was discovered in GitLab's repository commits API, allowing unauthenticated arbitrary file reads with a CVSS score of 10.0. GitLab released patches on September 10, 2026, covering versions 19.1.8, 19.2.6, and 19.3.2, with CISA adding the flaw to its Known Exploited Vulnerabilities catalog the next day. Internet scans via ZoomEye identified over 1.26 million publicly reachable GitLab instances as of September 19, 2026, though the figure reflects exposure scope rather than confirmed vulnerable systems. Security teams are advised to inventory all self-managed instances, apply available patches immediately, and restrict public access where upgrades cannot be deployed right away. Additionally, service account credentials accessible through potentially exposed instances should be audited and rotated as a precautionary measure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Stale READMEs Drive Away New Contributors — Here's an Automated Fix

Outdated setup instructions in open-source READMEs frequently cause new contributors to abandon projects before making a single contribution, according to a developer essay published on DEV Community. The author argues this 'README rot' is one of the costliest silent bugs in software, since frustrated users simply leave rather than filing issues. While the docs-as-code movement improved documentation review processes, it still relies on human diligence to keep content current — a dependency the author calls structurally flawed. To address this, the author built ReadmeForge, a GitHub Action that monitors code pushes, analyzes diffs, and automatically opens pull requests proposing README updates for human review. The tool is free for public repositories and requires no API key configuration, aiming to make documentation accuracy a continuous, automated side effect of normal development work.

0 comments Read more at DEV Community