Milter: keep the reply code and text in delivery traces #293

Merged
jcoffey-dev merged 2 commits from fix/milter-reply-code-trace into main 2026-11-05 04:46:21 +00:00
Owner

When a milter rejects with a custom reply, the client sees the code and text but the trace only says "Reply code". This records both, so you can see why from the trace. SMTP replies don't change.

The first commit is Stefan's patch from #289, thanks Stefan. The second records the code as a number, as outbound traces do, trims the line ending, keeps the fields off the other actions, and adds the modification notice.

Closes #289

When a milter rejects with a custom reply, the client sees the code and text but the trace only says "Reply code". This records both, so you can see why from the trace. SMTP replies don't change. The first commit is Stefan's patch from #289, thanks Stefan. The second records the code as a number, as outbound traces do, trims the line ending, keeps the fields off the other actions, and adds the modification notice. Closes #289
jcoffey-dev added 2 commits 2026-11-05 04:18:21 +00:00
Populate the existing Code and Details trace fields for Milter ReplyCode actions without changing the SMTP response. Extend the existing session test to check the actual emitted event and complete reply.
Milter reply traces: numeric code, no empty fields
github/ci (branch) GitHub Actions
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
ci / github (pull_request) Successful in 5s
50fab51d51
Record Code as a number, as outbound SMTP traces do, and trim the line
ending off Details. Only the reply-code event gets the two fields, so text
logs don't show "(null)" for them on the other actions. Add the
modification notice.
jcoffey-dev merged commit 11279c6e1e into main 2026-11-05 04:46:21 +00:00
jcoffey-dev deleted branch fix/milter-reply-code-trace 2026-11-05 04:46:21 +00:00
Sign in to join this conversation.