Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 38 subscribers
  • Views 2023 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos XG WAF Exchange 201x, Problem with attachment size greater 1 MB

B|Cyber|Security 
Hello,

when will this finally be solved? I already have 2 customers who have this problem. And it is always a chore to explain to the support what they have to do.
I'm slowly cursing the day I switched to V18.

regards
BCS


This thread was automatically locked due to age.
Parents
  • 0

    This will not be resolved shortly as this change is a modsecurity change in the new version. Therefore the new modsecurity version is blocking attachments bigger then 1 MB. To increase this filter on a global scale would be a to high risk for most customers. Therefore the solution is to implement a switch within the product to be able to adjust this. There are roadmap items to adjust this but actually from my experience, this change should be done within minutes. How do you address this issue with the support? Maybe the community team can help you with the opening of such a case by reviewing both cases. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    The thing with the switch is exactly what I'm thinking of, I would change the position with the apache modsecurity myself if I had root rights on the box (.. and not endanger my guarantee;)).
    The current status is that case 1 has already been resolved, but only after I escalated it. Case 2 is still open. What annoys me is that this thing is known but the support either doesn't know it or doesn't want to know it. Today I got a KB entry as a solution in which howto control the SMTP scan size in the MTA .. ???

Reply
  • 0 in reply to LuCar Toni

    The thing with the switch is exactly what I'm thinking of, I would change the position with the apache modsecurity myself if I had root rights on the box (.. and not endanger my guarantee;)).
    The current status is that case 1 has already been resolved, but only after I escalated it. Case 2 is still open. What annoys me is that this thing is known but the support either doesn't know it or doesn't want to know it. Today I got a KB entry as a solution in which howto control the SMTP scan size in the MTA .. ???

Children
Unfiltered HTML