Wez Furlong
0e339a2b9e
Add test coverage for source_selection_rate and tidy up how we reflect being throttled due to source_selection_rate; in the first cut we made it look like the ready queue was full, but now we're a bit more deliberate: * If any of the candidate queues were full, we report that the ready queue was full so that the message can be retried again "soon". * If we hit a source_selection_rate throttle, we use the throttle delay to adjust the min delay period and if we run out of candidate sources, we'll have the same sort of return value as we would for a suspension with a definite duration; the message will log that transient failure in the same way with the same sort of retry schedule. I've revised the wording in that case to be "no sources for SITE pool=`POOL` are eligible for selection at this time" (the important part being `at this time`) to suggest at the transient nature of the unavailability. * If we exhaust all sources for other reasons, we'll treat this as the NoSources case. In practice, this should mean that the source has zero weight. We'll now report "no sources available for SITE pool=`POOL`" in this case instead of the more precise but wordy "no non-zero-weighted sources available for SITE" that we used prior to this commit.
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 and at https://kumomta.com/.
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. For paid support see https://kumomta.com/support.
Getting Updates
You can subscribe to updates at https://kumomta.com/subscribe, we send updates periodically and will never sell nor share your information.
Talk to Us
We're available to talk about the project, book us at https://cal.com/team/kumomta/talk-with-kumomta.