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.
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
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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