Hermes Agent
GIGAZINE's Hermes email trial separates connection from delivery
GIGAZINE's September 5 Hermes trial delivered a generated news summary by email, but inbound mail remained blocked with its chosen mailbox. The hands-on report found that a Connected badge did not prove sender acceptance or the agent's use of the configured gateway, exposing two distinct setup hurdles.
GIGAZINE's latest hands-on Hermes report follows a scheduled task beyond the desktop and into an actual inbox. The September 5 article reports successful outbound delivery only after the writer explicitly directed the agent to use the connected Email Gateway. Inbound mail was a different outcome: the chosen mailbox supplied ARC authentication results, while the observed Hermes path expected an Authentication-Results header. The writer stopped that test rather than claiming two-way email worked.
The facts
- The article used IMAP and SMTP configuration in Hermes' Messaging surface and restarted the gateway after saving it. - The first inbound attempt received no reply; the writer then added the sender to Allowed users. - Inbound mail still failed, with the reported gateway log saying no Authentication-Results header. - The Sakura Mailbox message carried ARC-Authentication-Results, which the observed implementation did not use for acceptance. - For outbound delivery, the agent initially said SMTP settings were missing despite the connected gateway; explicit gateway routing produced a received message. - The earlier September 1 cron trial ran a scheduled task with Desktop closed after installing the background gateway, while the PC remained running and logged in.
Why it matters
This is useful adoption evidence precisely because it does not end at installation. There are at least three separate outcomes: a service connects, a sender passes the admission policy, and a completed result reaches the intended recipient. A green transport indicator establishes only the first. The official messaging guide documents allowed-user configuration, while the independent report supplies the concrete mailbox incompatibility and outbound routing confusion. Neither source justifies weakening inbound authentication to make a demonstration look successful.
Current
Inspected on 2026-09-07. The Hermes Agent stable-release baseline is v2026.8.31 published 2026-08-31T19:29:49Z. The main source was published September 5, 2026 when captured. Release metadata is a version boundary, not evidence that an open proposal has shipped.
Evidence
The primary source is GIGAZINE — Hermes email trial, September 5 (https://gigazine.net/gsc_news/en/20260905-hermes-agent-mail/). Supporting context comes from GIGAZINE — Hermes cron trial, September 1 (https://gigazine.net/gsc_news/en/20260901-hermes-agent-cron-automation/); Hermes docs — messaging gateway (https://hermes-agent.nousresearch.com/docs/user-guide/messaging). The linked records were inspected directly; related project records are not independent confirmations.
Operator take
Use a harmless end-to-end task to test the delivery surface you intend to depend on. Verify an actual received message separately from a scheduler's completed record, and test inbound commands with the mailbox provider that will remain in service. If the authentication headers differ, preserve the rejection and diagnose the trust path rather than accepting arbitrary mail. GIGAZINE saved the successful outbound method as a skill; that may reduce routing confusion, but it is not a replacement for transport configuration or sender validation. The cron companion also makes an important boundary visible: closing Desktop is not the same as powering off the machine or logging out.
Caveat
These are GIGAZINE's reported observations on its setup, not an independently reproduced regression or a claim about every mailbox. The page shows September 5 even though feed metadata surfaced September 4. Its inbound test remained unsuccessful, and no alternative email service was tested in that article.
These are GIGAZINE's reported observations on its setup, not an independently reproduced regression or a claim about every mailbox. The page shows September 5 even though feed metadata surfaced September 4. Its inbound test remained unsuccessful, and no alternative email service was tested in that article.