Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We have a customer that is migrating to Office365.
Emails are received as Relay from O365, since there are users on both the old and new system and emails need to flow back and forth. However also emails from other domains to the customer domain come...
One of our FMC's is not providing a Notes popup field when issuing a deployment.We use this Notes field to enter our change# among other things.
Where is the setting to enable this popup?(I now had to go into the Deployment history to update the Note...
Curious why this is, as it's possible on the ESA's. We also connect usually by mgmt IP, so our internal certificates accommodate those. But for customer access public certificates do not allow for IPs in SAN fields... Therefore it is very useful to h...
The problem with O365 is that the SenderGroup for O365 is the same for traffic from different SenderDomains.Traffic for my customer's SenderDomain should be treated as Relay and the rest should be treated as Inbound. However multiple SenderDomains ar...
First of all there is no Exchange server in play here. (The legacy server is a Domino server and will be retired.)
Secondly, the ESA remains to be used for O365 outbound verification.
Regardless of the amount of listeners, O365 can only be detected b...
Yes, we only have one listener interface. Though I don't see that making a difference for receiving emails from O365.
The "fall over" reference is in regards to when configuration changes are done on O365 and unintended traffic flow is activated. We ...
In our case the ESA is used both for inbound and outbound security.
So far we have traffic being delivered correctly for the customer's domain both ways.I'm just concerned with external traffic coming from O365 destined to the customer, that is not c...
