On 2014-11-14, Heiko Schlittermann <[email protected]> wrote: > > --===============6048627209023239470== > Content-Type: multipart/signed; micalg=pgp-sha1; > protocol="application/pgp-signature"; boundary="sXc4Kmr5FA7axrvy" > Content-Disposition: inline > > > --sXc4Kmr5FA7axrvy > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Jeremy Harris <[email protected]> (Fr 14 Nov 2014 11:34:24 CET): >> --- Comment #2 from Jeremy Harris <[email protected]> 2014-11-14 10:= > 34:23 --- >> As of sixteen years later, with no action, I'm not convinced there are en= > ough >> broken SMTP implementations out there for this to be worthwhile. > > I think, we had some similiar discussion already. Some kind of acl for > outgoing connections, e.g. drop the connection if there is an unexpected > certificate, drop the connection if there is an unexpected SMTP banner, >=E2=80=A6
We have EXPREIMENTAL_TPDA It can do some of that, (and several other things) but it's implementation in the config file was, last time I looked, somewhat untidy, with several different features going thopugh only two interfaces. -- umop apisdn -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
