The relay-wide port 25 session cap from inbuxa-server 27.1-rc.28 (maxSmtpSessions, default 1000) gets a field on the relay settings form, under Taking mail in. It is sent only when changed, must be a whole number above 0, and stays hidden for a relay on an older server.
Tests: typecheck, lint, i18n check, npm test (1108, 1 new), the shell checks and the build pass locally. Not checked in a browser: it needs a linked relay on 27.1-rc.28.
The relay-wide port 25 session cap from inbuxa-server 27.1-rc.28 (`maxSmtpSessions`, default 1000) gets a field on the relay settings form, under Taking mail in. It is sent only when changed, must be a whole number above 0, and stays hidden for a relay on an older server.
Tests: typecheck, lint, i18n check, npm test (1108, 1 new), the shell checks and the build pass locally. Not checked in a browser: it needs a linked relay on 27.1-rc.28.
inbuxa-server 27.1-rc.28 gave the relay a relay-wide cap on port 25 sessions, maxSmtpSessions (default 1000), settable only over JMAP until now. The relay settings form shows it under Taking mail in, sends it only when changed, and refuses 0 or anything but a whole number. A relay on a server before 27.1-rc.28 has no such setting, and the field stays hidden.
Test: model.test.ts reads 1000, sends 250, refuses 0 and text, and leaves an older relay alone; failed before (no maxSmtpSessions in the form), passes now.
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.
The relay-wide port 25 session cap from inbuxa-server 27.1-rc.28 (
maxSmtpSessions, default 1000) gets a field on the relay settings form, under Taking mail in. It is sent only when changed, must be a whole number above 0, and stays hidden for a relay on an older server.Tests: typecheck, lint, i18n check, npm test (1108, 1 new), the shell checks and the build pass locally. Not checked in a browser: it needs a linked relay on 27.1-rc.28.