Record that a hold really does hold, on the live server #34

New Issue

Closed

opened 2026-08-25 16:23:08 +00:00 by jcoffey-dev · 0 comments

jcoffey-dev commented

2026-08-25 16:23:08 +00:00

Owner

README only. Scheduled send was marked "not yet exercised against the live server", and it now has been — that claim was the last thing standing between the deploy hold on 04580f2 and production.

With futureRelease set to 30d on the live 0.16.19, a submission carrying a HOLDUNTIL ten minutes out came back:

sendAt:      2026-08-25T16:32:26Z   (exactly the time asked for)
undoStatus:  pending
delivery:    250 2.1.5 Queued

rather than being sent at once. The submission was cancelled and the draft deleted, so nothing was delivered.

The entry also now says plainly that the capability is no evidence either way: it advertised maxDelayedSend: 2592000 and FUTURERELEASE throughout, including while the setting was off. That is the obvious thing to reach for and it lies — worth stating, since the whole bug is that nothing errors.

What stays mock-only is narrowed rather than dropped: the Scheduled folder reconciling on the way in, and a hold actually expiring into a delivery. Neither was exercised here.

🤖 Generated with Claude Code

Merged 2026-08-25 as coffey-labs/ihasmail@db6afb72ff

_{Rebuilt from: git history, session transcript.}

README only. Scheduled send was marked "not yet exercised against the live server", and it now has been — that claim was the last thing standing between the deploy hold on `04580f2` and production. With `futureRelease` set to `30d` on the live 0.16.19, a submission carrying a `HOLDUNTIL` ten minutes out came back: ``` sendAt: 2026-08-25T16:32:26Z (exactly the time asked for) undoStatus: pending delivery: 250 2.1.5 Queued ``` rather than being sent at once. The submission was cancelled and the draft deleted, so nothing was delivered. The entry also now says plainly that the capability is no evidence either way: it advertised `maxDelayedSend: 2592000` and `FUTURERELEASE` throughout, including while the setting was off. That is the obvious thing to reach for and it lies — worth stating, since the whole bug is that nothing errors. What stays mock-only is narrowed rather than dropped: the **Scheduled** folder reconciling on the way in, and a hold actually expiring into a delivery. Neither was exercised here. 🤖 Generated with [Claude Code](https://claude.com/claude-code) **Merged** 2026-08-25 as coffey-labs/ihasmail@db6afb72ff77 <sub>Rebuilt from: git history, session transcript.</sub>

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coffey-labs/ihasmail-github-archive#34