Files
kumomta/crates
Wez Furlong eaa5da6e9e re-ehlo when using OpportunisticInsecure and STARTTLS failed
We were previously only re-doing the EHLO in the success case, but there
are some receiving implementations that seem to roll the TLS failure
error forward, returning an error during MAIL FROM:

```
TLS connection failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher (#4.3.0)
```

we want that error to show up while we're considering the connection, so
that we can fail over to the next candidate in our list, rather than
having it generate a transient failure for the message and stopping
there.

refs: https://github.com/KumoCorp/kumomta/issues/67
2023-06-21 07:03:11 -07:00
..
2023-03-12 10:59:57 -07:00
2023-06-20 22:44:47 -07:00
2023-04-04 12:36:43 -07:00