Il 18/05/2021 15:27, Henrik K ha scritto:
Instead of \x{00E0}, you need to use \xC3\xA0 as you are matching_separate_
raw bytes. (untested, but assuming so from the url, too busy to test)
Yes, it works. I was confusing, the Spamassassin documentation is right.
I really have to use non capturing
On Tue, May 18, 2021 at 03:04:12PM +0200, Marco wrote:
>
> Hello Henrik,
>
> thank you for the hints. I didn't realized that SA doesn't support UTF8
> regex. Well. As you suggest, I would like to write rules coding independent
> in order to avoid surprises. I tried, it doesn't work...
>
> I hav
Il 17/05/2021 18:12, Henrik K ha scritto:
On Mon, May 17, 2021 at 03:02:57PM +0200, Marco wrote:
So I have to add the accented character literally.
I can't understand why. Are there any limitation in Hashbl plugin with UTF8?
Maybe I have misunderstood something.
SA doesn't support UTF8 regex.
On Mon, May 17, 2021 at 07:12:47PM +0300, Henrik K wrote:
>
> Or check the replace_tags in 25_replace.cf, there's ready templates for
> characters (but they match some commonly obfuscated variants too).
And yeah sorry, these won't work with HashBL, it's just for basic rules..
On Mon, May 17, 2021 at 03:02:57PM +0200, Marco wrote:
>
> So I have to add the accented character literally.
> I can't understand why. Are there any limitation in Hashbl plugin with UTF8?
> Maybe I have misunderstood something.
SA doesn't support UTF8 regex. It's just matching plain byte string
Hello,
I'm trying to use Hashbl plugin with bodyre function.
With that function I would like to match utf8 patterns, such as
'([\p{L}\p{M}\d\S]+[\ \t]+[\p{L}\p{M}\d\S]+)'
I'm in particular interested in accented characters, such as /[àèìòù]/.
With Perl, if I try:
```
use utf8;
use
