Hi list

We have the case that the LOCALPART_IN_SUBJECT rule should match upon a
message, but it doesn't. After checking the message we found that if we
replace the UTF8 encoded subject header with a plain ascii containing
the relevant string for LOCALPART_IN_SUBJECT it suddenly matches.

> Subject: =?utf-8?B?...?=

and localpart name.firstname cannot be found in subject

but if we change

> Subject: [Reminder] name.firstname Your email will

the localpart is found in subject.

We're using spamassassin 3.4.2 on CentOS 7.

We had to redact the subject and localpart for this report as they
contain customers personal details.

--

tobi

Reply via email to