Files
kumomta/docs/reference
Wez Furlong 9e757c36d3 add max_connections limit to esmtp_listener
Previously we'd go as far as the OS would let us.

This introduces the ability to set an upper bound, and our default for
this is 32k connections, or half of the possible u16 port space.  I
picked half because the ideal for an MTA is using half of its resources
to receive and the other half to send.  The math for that is more
complex for multi-homed machines or systems using proxies, but it feels
like a reasonable default; not too low that it will be painfully
surprising for existing users to discover on upgrade, and not so high
that new installations are as easily overwhelmed in the face of high
incoming traffic.

A new total_connections_denied counter is added that is bumped
whenever this or the over-memory limit are reached and we turn
away a session with a 421. The idea is that the operator may
want to investigate these events, and we don't otherwise have
a stream of information about them because they are deliberately
not logged to the normal delivery logs.
2024-08-10 08:28:04 -07:00
..
2024-07-09 15:09:09 +00:00
2024-06-10 09:30:17 -07:00
2023-08-11 21:44:40 -07:00
2024-06-10 09:30:17 -07:00
2024-08-08 15:16:19 -07:00
2023-05-09 15:28:01 +00:00
2024-06-10 09:30:17 -07:00
2024-08-09 20:56:05 -07:00
2024-06-21 17:20:04 -07:00
2024-07-09 16:50:48 -07:00
2023-02-25 10:50:58 -07:00
2023-08-03 19:05:50 +00:00
2024-01-05 15:15:11 -05:00