r headers that could possibly get standardized in future.
Kind regards
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail:l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz der Gesellschaft: Darmstadt
Registergericht: Amtsgericht Darmstadt
Handelsregisternummer:
e a good choice, for this situation. So you might need
to modify it a bit. ;-)
Kind regards,
Lars Kollstedt
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz der Gesellschaft: Darmstadt
Registergericht: A
ext years.
[...]
> Your best bet is to simply not configure any client certs, you don't
> need them to get the mail delivered.
[...]
With the current state of implementation, yes.
Thank you for your answers. :-)
Many thanks for the time to read and answer this. ;-) :-)
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz der Gesellschaft: Darmstadt
Amtsgericht Darmstadt, HRB 9484
Geschäftsführer: Andreas Ebert
Am Freitag, 22. November 2019, 23:08:39 CET schrieb Ralph Seichter:
> * Lars Kollstedt:
> > is there a clean way to optionally present a client certificate to a
> > Postfix MX [...]
>
> I hope I don't misinterpret your question here.
[...]
> However, I don't see
this is to have a fully verified transport trust chain within
the header when all postfix servers on the transport do this.
Any ideas?
Kind regards
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz d
entative.
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz der Gesellschaft: Darmstadt
Amtsgericht Darmstadt, HRB 9484
Geschäftsführer: Andreas Ebert
ter that long time. And this should IMHO be documented in some way, since it
will take some time until this change spreads to the common distributions. ;-)
But the default to disable ESMTP is IMHO dangerous, if TLS enforcement is
done. I don't think I'm the last one who stumbled into this
stfix not Ubuntu specific, and in my case occured with a postfix
3.1.0-3ubuntu0.3, but I would expect this to happen with all versions, from
the documented behavior.
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraß