All possible sources for @yahoo.com are suspended

get-help
1

Hi,
we are testing the submissions to see the deliverability after switching to -dev version, the TLS issue has been fixed, but for Yahoo we are getting this error:

all possible sources for qubox@yahoo.com are suspended

We don’t understand if the error is from Yahoo or comes from something else in kumoMta, we couldn’t find anything about it.
Sorry for the question, but I have 20k yahoo emails in queue and I don’t know how to manage them

A Thanks
Erik

3

What does kcli queue-summary output?

The “all possible sources for XXX are suspended” message means that the configured egress pool has no available sources in a working state; all of the sources in that pool are suspended. Or there are no sources in that pool.

Suspension is either something an administrator would do via kcli or the HTTP API, or you might have TSA rules configured to suspend traffic based on responses from eg: Yahoo.

It would be a good idea for you to review your transient failure logs from yahoo to see what is happening there.

4

Hi Wez, sure:
http://127.0.0.1:8008.tsa.kumomta unspecified lua:make.http://127.0.0.1:8008.tsa.kumomta 3336 0 0 0

SCHEDULED QUEUE COUNT
qubox@yahoo.com 19
qubox@yahoo.it 293
qubox@ymail.com 2

5

Perfect, so the error comes from the rules set, let’s look at it right away, maybe the times are too long and therefore it rightly gives me this answer.

Thank you Wez

6

The default rules for yahoo will suspend for 2 hours duration when a TS04 is encountered:

[["yahoo.com".automation]]
regex = "\\[TS04\\]"
action = "Suspend"
duration = "2 hours"

kcli queue-summary should indicate a suspended queue by showing a stop-sign emoji alongside it. You can more directly list the suspensions via kcli:

$ kcli suspend-list
$ kcli suspend-ready-q-list