Das stimmt, ja. Aber wenn ich mir die Whois-Daten von dieser Domain anschaue, dann sieht's danach aus, dass wirklich Amazon dahintersteckt:
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: +1.2083895740
Domain Status: clientUpdateProhibited
Domain Status: clientTransferProhibited
Domain Status: clientDeleteProhibited
Registry Registrant ID:
Registrant Name: Legal Department
Registrant Organization: Amazon.com, Inc.
Registrant Street: PO BOX 81226
Registrant City: Seattle
Registrant State/Province: WA
Registrant Postal Code: 98108-1226
Registrant Country: US
Registrant Phone: +1.2062664064
Registrant Phone Ext:
Registrant Fax: +1.2062667010
Registrant Fax Ext:
Registrant Email:
auch wenn das nicht direkt mit dem hier angesprochenen Fall zu tun hat, habe ich
auf dieser Amazon-Seite hier eine Erklärung von Verbindungsarten gesehen.
Einige weitere Punkte, die damit in Zusammenhang stehen könnten:
Amazon SES will attempt to send email with Transport Layer Security enabled, but there is not a way to guarantee messages are sent with TLS. SES uses opportunistic TLS when sending emails, which means it will attempt to send emails over TLS first, and then will fall back to regular SMTP if TLS is unavailable.
Note that the AWS note at
https://forums.aws.amazon.com/message.j ... eID=218303 refers to encrypting server-to-server communication to maintain confidentiality of the email message, is a shared characteristic of all SMTP services. This question relates to using a secure connection to the AWS SMTP server to protect the passwords used to authenticate with the AWS server.
Am 18.April 2014 gab's in einem Thread eine Bekanntmachung seitens Amazon (soweit ich das richtig verstanden habe), da hieß es:
Hello,
I would like to provide an update on the topic of Transport Layer Security (TLS) in email sent by Amazon SES.
Amazon SES now supports opportunistic TLS, which means that it sends all messages over a TLS-protected connection by default. When SES establishes an SMTP connection with a receiving mail server, SES upgrades the connection using the STARTTLS protocol if the receiving mail server supports TLS. If the receiving server does not advertise STARTTLS or if TLS negotiation fails, the connection proceeds in plaintext.
This feature is active in all regions and you don’t need to take any action to enable it. As a result, the majority of messages sent by SES are already protected by TLS.
In the future we will consider offering additional TLS controls, such as the ability to enable mandatory TLS, or pin the expected certificate for a receiving domain name. Please let us know what features are important to you in this space -- your input is crucial to us in prioritizing future work.
Hmmm...
Man gibt Geld aus, das man nicht hat, um damit Dinge zu kaufen, die man nicht braucht, um damit Leute zu beeindrucken, die man nicht mag.
)