Skip to content

docs(submission): the relay sees each command as the client sends it - #235

Merged
0kaba0hub merged 1 commit into
mainfrom
docs/submission-relay-per-command
Oct 27, 2026
Merged

0kaba0hub merged 1 commit into
mainfrom
docs/submission-relay-per-command

Conversation

@0kaba0hub

Copy link
Copy Markdown
Contributor

Goes with yarilomail/yarilo#2374. The Submission page described one relay connection per message, sent at DATA. Now: one connection per transaction, opened at MAIL FROM and closed at the end of DATA, RSET, QUIT or a drop; MAIL FROM, each RCPT TO and DATA reach the relay as the client sends them and the relay's reply is the client's; a recipient the relay refuses is refused at its RCPT and the message goes to the others; an empty relay host or an unreachable relay fails MAIL FROM; the five-minute idle timeout and submission_relay_command_timeout. The RFC page is unchanged.

@0kaba0hub

Copy link
Copy Markdown
Contributor Author

APPROVED at the current head. The Submission section and the Relay section now say what #2374 does: a connection per transaction from MAIL FROM to the end of DATA, RSET or the client leaving; the relay's reply as the client's; a refused recipient alone refused; 451 at MAIL FROM without a relay; the five-minute idle bound and the per-command timeout. Build green.

@0kaba0hub
0kaba0hub merged commit ea54bff into main Oct 27, 2026
1 check passed
@0kaba0hub
0kaba0hub deleted the docs/submission-relay-per-command branch October 27, 2026 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants