09-26-2023 09:42 AM
Ok, so this cropped up after our security group wanted us to require TLS incoming and outgoing instead of preferred. Not a surprise this affected customer emails as we warned them, but sometimes you just have to let them fail.
One side effect was spam emails stopped being sent to the CCSM central quarantine. Not sure why it's not supporting TLS, but even adding it as a destination control to preferer it, it did not correct the issue. Any ideas how to get the transfer working as I do not see any settings on the CCSM other than the port it's using.
They did revert the change for now after we got tickets in. The spam started going to the queue after that, so I know the TLS has something to do with it. any ideas on what/how to correct it before they ask to enable it again?
Solved! Go to Solution.
10-01-2023 04:09 AM
Kindly asking to check following options:
1. check please following doc to enable tls between ESA and SMA for SQ:
https://www.cisco.com/c/en/us/support/docs/security/secure-email-gateway/217454-how-to-enable-tls-between-esa-and-sma-fo.html
2. on ESA's destination control please add following domainname for Centralized SQ, put in right order and check:
hostname: the.euq.queue
10-01-2023 04:09 AM
Kindly asking to check following options:
1. check please following doc to enable tls between ESA and SMA for SQ:
https://www.cisco.com/c/en/us/support/docs/security/secure-email-gateway/217454-how-to-enable-tls-between-esa-and-sma-fo.html
2. on ESA's destination control please add following domainname for Centralized SQ, put in right order and check:
hostname: the.euq.queue
10-03-2023 08:18 AM
Perfect, thank you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide