mirror of
https://github.com/mjl-/mox.git
synced 2024-12-26 08:23:48 +03:00
62bd2f4427
instead of failing the connection because no certificates are available. this may improve interoperability. perhaps the remote smtp client that's doing the delivery will decide they do like the tls cert for our (mx) hostname after all. this only applies to incoming smtp deliveries. for other tls connections (https, imaps/submissions and imap/submission with starttls) we still cause connections for unknown sni hostnames to fail. if case no sni was present, we were already falling back to a cert for the (listener/mx) hostname, that behaviour hasn't changed. for issue #206 by RobSlgm |
||
---|---|---|
.. | ||
admin.go | ||
cid.go | ||
config.go | ||
dir.go | ||
dkimsign.go | ||
doc.go | ||
fill.go | ||
forkexec_unix.go | ||
forkexec_windows.go | ||
ip.go | ||
lastknown.go | ||
lifecycle.go | ||
lifecycle_test.go | ||
limitauth.go | ||
localserve.go | ||
lookup.go | ||
msgid.go | ||
rand.go | ||
recvid.go | ||
safeheaders.go | ||
sleep.go | ||
tlsrecv.go | ||
webappfile.go |