Wez Furlong
5248ac2171
This is an internal timeout that applies across the `process_data` method, which encapsulates the span of time between receiving the last part of the DATA payload and responding to it. The intent here is that we will return a timeout 4xx response to the injecting client if we take too long. In most cases we can do this at the point that the deadline is reached, but there are some cases where we cannot cancel the ongoing work and instead will detect the timeout after the deadline has been reached. We will stop short of putting the message into the queue subsystem in that case, and attempt to unwind the message from the spool and emit appropriate log records. The intent here is *not* to set a firm deadline on *responding* to DATA, but rather to ensure that we don't assume responsibility for relaying the message *if* the deadline was exceeded. It is still possible for processing to exceed the deadline. This behavior is more valuable than it may seem at first glance because a client that times out waiting for the server to respond has no way to know if the send was successful, and if its strategy is to retry the message AND the server accepted responsibility for it, then the result will be a duplicate delivery each time the timeout is experienced.
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.