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.
Hi,
In the email security appliance C170 (8.5.6-106) we defined an Incoming Content Filter
which sends eMails from a specific sender to Quarantine and a notification to the recipient.
But in this notification a link to the quarantine is missing in c...
Hi,
We're using ESA C170 with SyncOS 7.5.2-014.
I added a content filter with "file type is": executables and expect that if an executable attachment comes in it will blocked.
But it isn't when the extension is changed to .txt, for example.
Just...
Hi,It's about AsyncOS7.5 on WSA S360.After implementing URL Filtering I have following problem:If I'd like to access amazon.de for example, there are plenty of other Web Pages referenced too.Some of them belong to allowed URL Categories and others t...
Hi,We're using AsyncOS7.5 on two WebAppliances S360 with a Configuration Master 7.5 (M160).I used one of both appliances to implement URL Filtering and now I'd like to transfer this coniguration to the the master in order to publish it to both appli...
Hi,We're using a AsyncOS7.5 on Ironport S360.When a user accesses a URL which according to URL Category Filtering is forbidden (e.g. www.mydrive.ch) then the Error Message when using http is:--------------------This Page Cannot Be DisplayedBased on ...
Hello Matthew,
Thanks for the answer.
Nevertheless, I don't completely understand the following two point :
1) "...it would GENERALLY not go to the end user spam quarantine,..."
That sounds to me like there would be a possibility to configure ...
Hi Donny,Sorry for the late answer.Now I understood the matter and I got the whole thing running!There just were no https policies defined.Thanks for your help again!Jannis
Hi Donny,Many thanks for your answer.Sounds reasonable what you're saying, though I can find where I can change the config to not "drop" but "block" https requests.And another point, which I forgot to mention, is that in the access log it says both t...
