Cisco Bug: CSCun11014 - Secure replies over TLS to google hosted domains failing TLS handshake
Jan 27, 2017
- Cisco Registered Envelope Service
Known Affected Releases
Symptom: Secure replies not received if customer is using google hosted mail, sender receives bounces saying mail is undeliverable. Bounce back email is similar to: From: CRES Do Not Reply <DoNotReply@res.cisco.com> To: firstname.lastname@example.org Date: 21/01/2014 17:53 Subject: Delivery Failure:Read: [Encrypt] test The Mail Server at prod-cres-appx.xxx.ironport.com was unable to deliver your message to some or all of the recipients. This is a permanent error; the server has given up. Below is a list of recipients and the reason the server was unable to deliver your message: Failed recipient(s): email@example.com Error message: No mail server(s) available at this time. Reporting-MTA: dns; mxnat3.res.cisco.com Received-From-MTA: dns; localhost Final-Recipient: rfc822; firstname.lastname@example.org Action: failed Status: 4.4.1 Diagnostic-Code: X-James; No mail server(s) available at this time. Last-Attempt-Date: Tue, 21 Jan 2014 11:53:44 -0800 (PST) Conditions: In CRES admin, 'Bounce Messages' chosen on TLS failure.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases