Content Quality: News piece, 842 words (range 400-1200), clear Overview / What Is New / Upgrade Considerations / Related Maintenance Release / What We Don't Know structure. Accurate, appropriately technical, upgrade-relevant items (v2 file format downgrade block, OIDC discovery validation, hash_password endpoint, passive-declaration permissions, removed AMQP 1.0 headers) are surfaced. Title is 92 characters.
Source Verification: Both sources are first-party GitHub release pages for rabbitmq/rabbitmq-server. Read sources/2026-10/rabbitmq-440-adds-delayed-messages-for-quorum-queues-and-unix-domain-socket-amqp-listeners/source-0.html.gz (v4.4.0) and source-1.html.gz (v4.3.7); both HTTP 200, suspicious_patterns null for both. Snapshots contain the release text, but because summarizing fetchers have returned bad dates for this page, I re-fetched the raw release bodies via the GitHub API (repos/rabbitmq/rabbitmq-server/releases/tags/v4.4.0 and v4.3.7). API timestamps: v4.4.0 published_at 2026-10-19T06:38:13Z (created 2026-10-17), draft=false, prerelease=false; v4.3.7 published_at 2026-10-20T00:56:49Z. The snapshot also shows datetime 2026-10-19T06:38:13Z. 'October 19, 2026' is confirmed and 4.3.7 was indeed published after 4.4.0. Verified individually against the raw 4.4.0 body: (1) delayed messages on quorum queues: x-opt-delivery-time annotation or header, future time in ms since Unix epoch, routed and enqueued immediately, delivered once reached; AMQP 1.0 message annotation, AMQP 0-9-1 'long' header; AMQP 1.0 consumer may set it in annotations of a 'modified' outcome -- all confirmed, no preview/experimental/feature-flag gating is mentioned, so 'Adds' in the title is not overstated. (2) Unix domain socket: 'AMQP listeners can now bind to a Unix domain socket, using the same listeners.tcp.* settings as a TCP listener' with example listeners.tcp.1 = unix:/var/run/rabbitmq/rabbitmq.sock:0 -- confirmed verbatim; notes say 'AMQP listeners' without distinguishing 1.0/0-9-1 and the article correctly does not either. (3) stream.max_connections, mqtt.max_connections, stomp.max_connections confirmed; connection_max/channel_max renamed max_connections/max_channels with originals still supported -- confirmed. (4) Sole connection ownership per AMQP 1.0 Connection Uniqueness, rabbitmqctl sole_connection_status / sole_connection_force_delete -- confirmed. (5) x-name-prefix (64-byte cap, default amq.gen, AMQP 0-9-1 specific), x-stream-initial-offset, x-modulus-hash stability and move from rabbitmq_sharding to core, delivery-limit policy applies to existing quorum queues (default 20 on removal) -- confirmed. (6) MQTT retained store per-vhost limits, defaults 100,000 messages / 1 GiB -- confirmed. (7) STOMP: source line reads 'Following the footsteps of AMQP 1.0 and MQTT in previous years, the STOMP is now a standardlone protocol, that is, it is no longer built on AMQP 0-9-1.' The article's paraphrase ('standalone protocol implementation that is no longer built on AMQP 0-9-1, following AMQP 1.0 and MQTT in previous years') is faithful; the typo 'standardlone' was correctly interpreted as 'standalone' and not quoted. (8) Upgrade items: .sqs v2 format / .rdq v1 untouched / cannot downgrade to 4.3.x or earlier; OIDC discovery stricter validation, Cloud Foundry UAA, both opt-out keys; GET->POST /api/auth/hash_password with {"password": "..."}; passive declaration requiring configure, write or read; removed x-amqp-1.0-* headers with the '3.13 or earlier and not read since' caveat -- all confirmed. (9) Erlang: notes say 'fully supports Erlang 28 and 29 series for both new clusters and rolling upgrade scenarios' (the sentence has a dangling 'assuming that .' in the source) and 'highly recommend first upgrading to 4.3.7 or a later patch' when upgrading RabbitMQ and Erlang 28+ together -- article paraphrase faithful. The 4.4.0 notes do not state a minimum Erlang version; the 4.3.7 notes state a minimum of 27.0 for the 4.3.x series. The article claims no minimum, so there is nothing to correct. (10) Quotes: 'a new feature release.' appears verbatim in the 4.4.0 body ('RabbitMQ 4.4.0 is a new feature release.'); 'a maintenance release in the 4.3.x release series' appears verbatim in the 4.3.7 body (source formatting only adds code backticks around 4.3.x). (11) 4.3.7: x-expires timestamps lost on node restart so TTL timer did not fire if TTL outlived the restart; new consumer_timeout_response setting with default notify_consumer (sends basic.cancel to clients supporting consumer_cancel_notify, closes the channel for others) -- confirmed; the article accurately omits the close_channel option. (12) Security: grep of both raw bodies for CVE/vulnerab/security finds nothing; the article attributes no CVE or security fix to either release, which is correct. (The 4.4.0 CPRNG password-salt change and HSTS/Origin options are not mentioned in the article, a harmless omission.) (13) No contributor credits are named in either body and the article names none. No orphan URLs: every URL in the body is in article.sources.
Factual Accuracy: Every number, date, setting name, default, version and quote traces to the 4.4.0 or 4.3.7 release body. No fabricated specifics. Minor editorial characterization: 'The headline additions are...' ranks two features as headline items; the notes do not rank features, but the title and lead feature order (delayed messages listed first, Unix sockets second among enhancements) is a defensible editorial selection, not a factual claim. The summary names the delayed delivery, v2 file format that blocks downgrades and OIDC checks, all supported.
Overall Assessment: Accurate, well-structured and fully traceable to the cited first-party release notes. Title is not overstated: the features are described as shipped, with no preview or feature-flag qualifier in the source. APPROVE with no corrections.