Wez Furlong
c35838bc6d
After making spool stores respect the data processing deadline, in soak testing it was interesting to see that the outliers were not actually due to spooling, but instead due to latency spikes around delays fetching data for the various lua hooks for queue and shaping helpers to enforce things like provider level shaping. This commit passes the optional deadline through to the queue insertion logic, populating it only for the initial ingress and not for the requeue or spool enumeration cases. The application of conditional timeouts pushes the size of the compiled Futures over a stack-friendly threshold which (thankfully) showed up immediately in integration tests. The remedy for those is to sprinkle Box::pin around various futures to encourage them to live in the heap instead of on the stack. I'm a bit concerned about this, as the stack usage is workload dependent: I'm not sure that I've covered off enough of these to ensure that we won't see stack overflows in the future. If you are running into a stack overflow please report it! Note that you can mitigate a stack overflow by exporting `RUST_MIN_STACK=33554432` into the environment of kumod to set a larger default size. This commit catches the timeout error and converts it into a `451 4.4.5 data_processing_timeout exceeded (insert)` instead of letting it bubble up as a 421 technical difficulties response that would also have closed the connection.
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.