I'm not sure if I want to keep this, but it is currently useful for testing purposes. The previous logic was to skip opening an SMTP connection in a newly constructed Dispatcher if no messages were immediately available in the ready queue. This logic makes a lot of sense in a multi-node deployment with shared throttles, so that other nodes have an opportunity to open connections to drain their own queues, but when testing a single node it leaves some throughput on the table. This boolean option allows selecting whether we aggressively continue to open an SMTP connection even if we may not have a message ready to send yet, or, if left at the default `false` value, continue with the original more conservative logic.
KumoMTA
KumoMTA is an open-source Message Transfer Agent (MTA) designed for high-performance outbound email functionality, similar to commercial enterprise MTAs such as Momentum, PowerMTA, and Halon.
The KumoMTA project was founded by a group of email industry veterans with decades of experience building and managing high-performance On-Prem MTAs and is supported by a community of some of the largest senders in the world.
Because it is designed for high-performance sending environments, KumoMTA is for experienced email operations professionals who are accustomed to high-performance sending environments and familiar with DevOps practices.
Learn more in our FAQ.
Documentation
You can learn more about KumoMTA from the Documentation.
Community
Real-time discussion is available on Our Discord.
Developers
If you are interested in contributing/extending KumoMTA, take a look at DEVELOPERS.md. The #devel channel on Our Discord is for contributors to discuss KumoMTA development.
Reporting Bugs
See How to Report Bugs.
Getting Help
See How to Get Help.
Talk to Us
We're available to talk about the project, book us at https://cal.com/team/kumomta/talk-with-kumomta.