KumoMTA not always retrying delivery

get-help
1

Hi,

We noticed that since a couple of days some emails are not being retried. These have statuses like 452 4.2.2, 450 4.2.0 and should be retried.
I think it also did work before.

We’re still testing and setting up, so low volume without a lot of important traffic, so it did not caught our attention. But when we just updated to the latest March release, the pods restarted and it immediately triggered Expiration webhooks for the mails.

The odd thing is - they were not in the queue according to the Grafana logs. As you can see in the chart, this email to our test domain triggered a TransFail and immediately the queue was empty again.

We haven’t made any changes in the days before this upgrade - so I am not sure. I was hoping that this triggered some thoughts with someone who might have an idea or experience with an issue like this before so we can continue investigate it.

Thanks!

3

Latest test message just got retried successfully. Might have been fixed in the latest release then? Odd… but keeping it open just in case anyone has an idea

4

Not near enough context here to comment one way or another. I’d suggest at a minimum filtering the logs for sample messages to see their histories.

5

True. I did check one of the test messages that also got stuck - this one was tried once.

I have attached the only logs that have ever been logged for this mail. It was the only thing I could find
message.txt (10.5 KB)

6

Sadly it works again so I cannot reproduce it anymore :joy:

7

but I’ll keep an eye out

8

Better that it works.