Wez Furlong 992ffbd470 treat 3xx responses as transient failures
Following on from b64219bab4, if we
do encounter a 354 response to a message send, it must indicate
a protocol synchronization issue, so let's treat the associated
message as it had transiently failed and explicitly break the
connection (like we do for a 421).

I did consider making the associated message immediately eligible
to retry, but I worry that if that particular message is a poison
pill we might get stuck in a short cycle of retries for it.

I don't think it is likely for this particular message to be the
poison pill, because it is most likely the victim of an earlier
issue on the connection, but I still want to be cautious here.

The outcome here is still not ideal, but it is better than marking
the associated message as a permanent failure.
2024-11-18 14:31:34 -07:00
2023-03-06 07:53:27 -07:00
2024-09-11 11:00:24 -07:00
2023-02-10 16:44:10 -07:00
2024-11-13 13:50:27 -07:00
2024-11-13 13:50:27 -07:00
2023-02-21 21:18:49 -07:00
2023-02-21 21:18:49 -07:00
2023-03-09 20:56:02 -07:00
2024-09-10 08:00:06 -07:00
2024-10-28 20:45:14 -07:00
2024-07-05 09:48:20 -04:00
2023-06-22 13:50:51 -07:00
2023-02-15 06:51:59 -07:00

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.

S
Description
The first Open-Source high-performance MTA developed from the ground-up for high-volume email sending environments.
Readme
37 MiB
Languages
Rust 91.8%
Lua 6.3%
Python 0.9%
Shell 0.8%
JavaScript 0.1%