Blocked files problem

[#1]

Hi! We have a 200 with the latest firmware. I have added *.exe (and about 40 other file types) to the list of blocked files. In Protection Profile I have a profile named " scan" in which File Block for SMTP is set. In the SMTP policy for the mail server I have set " scan" as the protection profile. You guess it: Incomming emails with .exe attachments are not blocked by the firewall. Can someone please help?!? Cheers Oliver

[rschulz]

Although this is slightly left of centre, and may not solve the particular problem/s; it is of interest to this discussion. I have noticed that there are a few sites out there that allow files to go through, even though the file types are blocked in the “Antivirus/File Block” (only a v.small percentage). For example, the Antivirus/File Block of *.zip will block nearly all downloads of zip files, except from – www.netcomm.com.au (support downloads) Have also noticed this with phenomenon with *.exe from ato.gov.au, (this download has since been removed from the web site) In both cases the problem was resolved with a Antivirus/File Block of *.zip* and *.exe* In the Netcomm case, it uses some sort of php download function, and I tried to produce the same bypass problem in smtp, but could not replicate the problem (not enough time, or knowledge, or maybe it just works!) Tony, do all your blocked files come through?, if so then this would look like a individual firewall policy issue, or the position order of your particular smtp or http firewall policy and against some other policy that is letting the files through rob

[#3]

Can you tell me what is the file size for the passthrough attachment? and what is the oversize limit in your fortigate? check from antivirus->config->config on GUI. van

[#4]

Sorry, I was a few days off. Our problem with SMTP got solved (as it seems) by setting splice to the " wrong" status and then back to the " right" status to get rid of blocked attachments. Maybe it is just an coincidence ... Oliver

[#5]

My issue was fixed too. It turns out in the Scan profile, I didn' t have the proper items checked. Fixed thanks to Fortinet support team. Thanks guys.