Is there any workaround to avoid the limitation of regex size is less than 7 bytes

[bijilesh.k]

hi ,

We have requirements to block some keywords which are less than 7 bytes in size,device has limitation to use the keyworks(regex ) with less than 7 byes in size .

Is there any workaround or alternate solutions to block some keywords with less than 7 bytes .

Thanks,

BIJILESH

[winwan]

unfortunately , the answer is no .

[NGS_SOC]

No, this is a huge limitation by stream based design . Also 7 bytes/characters have to be continuous.

(ABCDEFG) is accepted

() is not accepted.

I hope in the future this can be avoided due to strong limitation in regex pattern creation.

Regards

[SimmSimm]

Whilst we are talking about the 7 byte limit on regex - can it contain spaces ? I have some very annoying spam bounce problems at the moment, the only identifying feature appears to be the subject line - "Can i turst you?" (caps & spelling as in the email) - Ive created a data pattern "Can i turst you\?" which I would expect to match these mails which commits but does not appear to work. Any ideas ?

[winwan]

Have you try this format "Can\ i\ turst\ you"

[SimmSimm]

Thanks for the suggestion - strangely it now works as above, without escaping the spaces so perhaps it was something else in the data filter it didnt like. Its all a bit of a mystery, but the spam is all being rejected now.