The block is needed where one submitting party comes from several addresses and has to be limited as a whole. It does not list its members itself: each source names the group with its own source-group line.
Inside there are only two directives, and they are opposite in meaning: max-smtp-in — “no more than,” reserved-smtp-in — “no less than.” Both are about simultaneous inbound connections, and both work under the node’s overall limit total-max-smtp-in.
The engine does not check consistency: you have to check the sum of ceilings and the sum of reserves against the overall limit yourself.
# the group is declared here, and the members name it on their side <source-group localSources> max-smtp-in 10 reserved-smtp-in 5 </source-group> <source 192.168.0.30> source-group localSources </source> <source 192.168.0.40> source-group localSources </source>
3 articles
◇Accept, route, deliverA message’s path inside the node: accept, decide where, deliver — and all the settings live between these three steps.◇Four value types the whole config is written inBoolean, domain pattern, regular expression and time interval — defined once in § 3.2 and then used by all directives.◇Reloading settings versus restarting the serviceThe configuration is read at startup, and after that edits are picked up by the reload command — except for the directives the manual marks as requiring a restart.