mixandClaude Opus 5.5 295d72e721 plan: inbound-upstream-result - the upstream's answer in the Inbound log ...

The owner, 2026-10-16: the Inbound log lacks the upstream's answer; the
result in the row only, a page per message later if needed. One stage,
2.10.0: migration 0012, the milter keeps the queue id, the tailer hands
port-25 delivery lines to the journal, an Upstream column (mockup 5348330).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 14:11:06 +03:00

..

delivery-log-storage.md

release: 2.2.0: a message's page keeps its delivery log

2026-10-12 11:59:10 +03:00

from-header-binding.md

audit: decisions of 2026-10-13/14 on what 2.4.0 left undone

2026-10-14 07:29:13 +03:00

inbound-antispam-panel.md

docs: drop the Cursor rule of the removed panel-ui mockups

2026-10-16 00:10:03 +03:00

inbound-quarantine.md

roadmap: inbound quarantine is an idea, not a candidate

2026-10-12 10:04:44 +03:00

inbound-upstream-result.md

plan: inbound-upstream-result - the upstream's answer in the Inbound log

2026-10-16 14:11:06 +03:00

panel-dkim-signing.md

entrypoint: /data/opendkim removed, as planned for the release after 2.8.0

2026-10-16 13:46:04 +03:00

panel-notifications.md

audit 4: cards ordered by number, a notification owed to each recipient

2026-10-15 11:49:50 +03:00

panel-redesign.md

notification-mail-recheck: Re-check DNS on Server › Settings

2026-10-16 13:29:54 +03:00