We were getting hammered with unwanted messages that companies are using Amazonses.com to send their messages. What we did was drop alll messages with @amazonses.com in the Sender field. However we have found there are legitimate messages that originate from @amazonses.com so I need to be able to allow them through.
I tried adding an Incoming Content Filter at the top of the filters and put in a keyword to bypass further filters. This has worked with messages from Constant Contact because the sending address has a consistant piece of the address I can use as the key word. However what I have found is the Amazon messages are always different.
The messages are coming from Right Signature and should have a from address of firstname.lastname@example.org but I am not seeing that any were in the message details. I removed the filter to block @amazonses.com messages and received a test message in Outlook and when I look at the header information it shows the From: address as email@example.com so i need to figure out how to filter for that information that Ironport is not showing in the message details.
Attached are the message details for one the was blocked and one that was received.
I noticed in your message tracking example the mail-from is from XXXXXXXX @email.amazonses.com
So, if I'm understanding correctly you should be able to add '@email.amazonses.com to the same mail policy as constantcontact.com specifying @email.amazonses.com as a sender. This regular expression will match any address with that ending...
I tried to filter for rightsignature when it is in the Sender field but that does not work. I tired this because when I remove @amzonses.com from content filter messages come through and when I looked at the header of the message in Outlook it showed that in the From: field.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :