mirror of
https://github.com/KumoCorp/kumomta.git
synced 2026-09-07 16:01:25 +00:00
Wez Furlong
e5127cb24b
Previously, we would only trigger the requeue_message event in situations where we were actively working on talking to the destination. That left issues such as persistently NXDOMAIN destinations as being unable to be caught and handled by the requeue_message event, which is an issue for sites that want to fail out messages from the queue that have bogus domains before they reach max_age. This commit replaces all but one of the force_into_delayed calls with requeue_message, and makes the call out to the event unconditional (rather than dependent upon whether we were incrementing retries or not). The only case now that doesn't cause requeue_message to fire is when the ready queue is full. The rationale is that that is a transient local resource issue (rather than some external factor to which we need to react), and that is likely to be a hot event when it triggers, so we don't want to add CPU pressure with calling out to the requeue event for them. refs: https://github.com/KumoCorp/kumomta/issues/319