content filter performance
I found a new issue with the content filter. The more rules I add the worst the server performance gets. I finally figured out something very important. Emails are being checked every time the are received, and when they CC or BCC some one, it gets checked again, and again. I found a simple fix to this. First content rule, add header that content filter check was started. Second content filter rule, if content filter header check exists, then skip all the other content filter rules. This has made a huge performance impact on the server, and I ask my self, why wasn't this included in the software to begin with. It seems that running the same message through the content filter 10 times because it is addressed to 10 different people seems to waste many CPU cycles. I realize that this might present some other problems, but this needs to be looked at.
Tray
shared this idea
Hello,
Thanks for sharing your idea with us. Unfortunately this is not possible. A copy of the message is created for each recipient and each copy of the message is processed by the content filter. This enables actions to be taken on a copy of a message destined for a specific recipient without affecting the copy of the message destined for the other recipients.
Thanks again,
Arron
-
Tray
commented
I do not understand why the message would be created for each recipient before being passed through the content filter. Example, I have a rule that filters bad emails. If the mail server receives a bad email with content I don't want and it has been CC or BCC to 10 other email users, why would I want the server to make 10 copies of that email and then process it 10 times!
-
Tray
commented
An example is if a message is to specific domain, and there is a rule to copy that message to another person. I am finding that the message gets copied once for every time the message is scanned through the content filter. This is showing that when a message is CC or BCC, that the message is pushed through the content filter once for each address on the message.