Domain content filters proceeding to user filters

Idea shared by James Ratliff - 6/19/2019 at 5:16 PM

Under Consideration

Today we attempted to implement a domain-level content filter that added a header to e-mails coming from specific domains.

Once we activated this filter, user-level filters are apparently no longer being processed.

The domain-level filter is working correctly and user-level filters that DON'T match the domain-level filter are working correctly.

However, e-mails that match the domain-level content filter do not appear to "continue on" to be processed by the user-level filter.

Are we doing something wrong? Is there a setting to say, "Proceed to the user-level content filters once the domain-level filter has been processed"?

If not, that's pretty frustrating. It means that any e-mail manipulated at the domain-level can't be filtered by the user-level content filters.

Any suggestions?

2 Replies

Reply to Thread

Employee Replied

6/20/2019 at 4:27 PM

Employee Post

Hi James,

I'm sorry you're having some trouble with content filtering. I went ahead and created a ticket for this issue. I'll update this post when there is a resolution.

Employee Replied

6/21/2019 at 8:17 AM

Employee Post

James,

The way filters work is that only one filter will run on a message. So if a spam filter moves a message or appends the message with "Spam-Low", then the domain filter and user filters will not run on it. If a message meets the conditions of a domain filter, then the user filter will not run on that messages. The logic behind this was to prevent end users from being able to override a domain level filter.

A feature request has been submitted to give domain admins a toggle to allow or not allow end users to override domain level content filters.

Back to Community Threads

Reply to Thread

Enter the verification text