Customer-specific URL Rules

[Vashan Kailai]

Hi.

How i can perform Customer-specific URL rules before applying the rules in production?

[Francesco Bianchessi Barbieri]

Don't waste your time on setting up this feature. That's the most useless feature ever, LoL. I've been using it for more than a year now, and I can assure you that the rules it creates when you submit messages are completely useless: the email you receive and are blocked as spam, will continue to be blocked as spam, despite the submissions you make. Already filed several cases on this, but they say "**** the domain, submission does not work because the email changes in the time, when you write and the recipient answers, it's another email".

[alexander-smg]

Pay attention.  What smg really needs is bifurcation for inbound / outbound senders / recipients.  That's a feature we all want.  And we need to be able to bypass malware filters at will.

 

boom

[Thomas Anderson]

Yes there are limitations:  when you submit something to generate a CSR, it is going to result in a "fuzzy" hash rule (aka a signature based rule, with some latitude).  On the other hand, I would point out that 30% of the customers that are on the 10.7.5 release are currently using the feature and, based on the low number of support cases, appear to be happy with how it is currently implemented.

Not saying it is a panacea or perfect, but that it is worthy of taking a look at to see if it fits your needs.

[alexander-smg]

Don't worry about that.  We need bifurcation please.

[Francesco Bianchessi Barbieri]

@Thomas Anderson ​thanks for trying to explain, but I confirm that, despite many cases I submitted to your support in the past year, since I enabled the feature, and after letting check the config by the support team (confirming it's ok), the feature simply does not work for many messages. Let's say my colleague "A" receives a message in its quarantine, he submits it a as a false positive, then he replies to the message. The remote recipient replies again , and the message is still blocked. So my colleague submits again and so on. Hence it is useless.

Regards,
Francesco

[alexander-smg]

That is so true. I have never gotten it to work either. But it would be nice if it did.

[Francesco Bianchessi Barbieri]

It's far away from being a panacea or a perfect solution. I'd call it a little tape for a chainsaw injury.

[alexander-smg]

What are u talking about?

[Thomas Anderson]

To answer your question, let me suggest a general approach to testing new polices:
- Create a policy group, "test-policy-group" or whatever you name you like.
- Populate that group with either users who are willing to be your "beta testers" or with mailboxes that you have specifically provisioned for testing purposes (or a combination of the two).
-  Create or enable the new policy you would like to activate (in your case, you might go to the Email Spam Policies page and look at the pre-built "Customer-specific" policies and see if they fit your needs as is, or need customization"
-  Once you have the polices the way you want them, enable them for your "test-policy-group"
- validate that the policies are accomplishing what you intended, tweaking as needed.
- Once you are happy with the outcome, you can then enable the policies for your "production" policy groups.