Am 04.03.2014 09:49, schrieb Robert Schetterer: > an acceptable workaround, your "man made problem" was no suprise.
Nobody said it's a surprise. And: It's not a spurprise and not a "man made problem", but an interesting new use-case where we can provide additional mailadresses with TLS-encrypted SMTP (next hop)-transfer to/from the recipient's provider. The forced use of TLS-encryption can by triggered by the user who knows, what he's doing. But the user need's a fast DSN if the enforced TLS is not possible. > And however you have tls working ,you can only promise secure send next > best mx hop, you will never have have full control of the whole "mail > pass chain". Thanks for the explanation, but I'm not stupid AND I know Postfix VERY well. I know that. > So promise users "secure mail" is always problematic, you > can only serve mail as secure as possible, everything else is just > marketing speak. I agree. That's why we do NOT promise anything else. Otherwise I'd be stupid. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin
signature.asc
Description: OpenPGP digital signature
