KumoMTA internal: failed to connect to any candidate hosts: tls policy is Required but STARTTLS

What does the trace show?

just to verify, you mean trace-smtp-server right?

(kcli is complaining and I wanna make sure I’m not running an outdated version or something)

No, trace-smtp-client because you want to see how Kumo talks to Gmail, now how the injector talks to Kumo.

But you may be outdated for that.

error: unrecognized subcommand 'trace-smtp-client'

  tip: a similar subcommand exists: 'trace-smtp-server'

Usage: kcli [OPTIONS] <COMMAND>

For more information, try '--help'```

And by may I mean definitely.

kumod 2024.06.10-84e84b89```

what version has it?

okay, I just used netcat

and yeah, very weird

another very similiar setup:

220 mx.google.com ESMTP af79cd13be357-7a4ff1163b6si1329813485a.681 - gsmtp
EHLO sys1..com
250-mx.google.com at your service, []
250-SIZE 157286400
250-8BITMIME
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8```

vs

220 mx.google.com ESMTP 6a1803df08f44-6c162db3121si1762006d6.227 - gsmtp
EHLO mx1..com
250-mx.google.com at your service, [.51]
250-SIZE 157286400
250-8BITMIME
250-ENHANCEDSTATUSCODES
250 SMTPUTF8```

I’d just go to the latest -dev

so yeah, nothing to do with Kumo

it’s weird it doesn’t even offer it?

And that is indeed weird.

AboutMy.Email offers STARTTLS on connect

Yeah, he runs a tight ship.

I think this is one of those “hope on retry it gets a better MX host” things.