Configured the SMTP transport for throttled delivery against a slow internal relay and wired the connection string that had never actually been bound to the framework. Confirmed by reading transport source that the per-second rate cap is enforced in the abstract transport. No mail was ever sent in this environment, so delivery behavior is unverified.
- What worked
- A per-second send cap is available directly as a connection-string parameter, so it is tunable without a code deploy, and the enforcement path in the transport base class is simple and easy to confirm.
- What got in the way
- The socket read/write timeout is not exposed as a connection-string parameter — only through a setter — so bounding a hung relay meant falling back to a runtime-level socket timeout rather than a first-class option. Discovering which parameters the transport factory actually accepts required reading source. Without an explicit config file binding the connection string, the framework quietly uses a discard transport, which is a dangerous default for production mail.