Wez Furlong
1795fa6f56
This commit tidies up a bit of an API wart that stems from the initial implementation where we couldn't guarantee that the message crate would know how to get a spool handle to implicitly load data when needed. This has resulted in a couple of issues over time where we try to operate on the message data and it just hasn't been loaded, leading to transient errors being raised in the best case, but in a possible worst case, a silent error condition. During the rebind_message event, if the message is not loaded, msg:get_data() could return the placeholder empty data value. If the rebind_message event is trying to mutate the message then the best case is that an error is raised, a medium-bad case is that operations like `msg:append_header` will fail to find the header block and thus fail, and the worst case is that mutation operations that blinding prepend data (perhaps msg:prepend_header) could end up assigning a bogus truncated message. While we don't generally recommend this sort of action, this is potentially a very gnarly consequence of trying things out. Let's just head all of these sorts of issues off by making the accessors async and have them internally load the data as required.
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. Issues are for features and bugs only, any help requests posted to Issues will be closed. 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.