On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote:
>
> How about using 'backslashreplace' instead of 'replace' to encode to
> list's preferred language in Mailman/Handlers/SpamDetect.py ?
That's an interesting idea. I'll look at doing that for the next release.
--
Mark Sapiro The highway is
> Le 9 juil. 2016 à 17:41, Mark Sapiro a écrit :
>
> On 7/9/16 1:24 AM, Manuel Goepfert wrote:
>>
>> Looking at some documentation I found out that this was a known problem and
>> that it was addressed in on e of the mailman version. So I upgraded to
>> 2.1.18 that included that fix but I?m s
On 07/09/16 10:04, I wrote:
> How about using 'backslashreplace' instead of 'replace' to encode to
> list's preferred language in Mailman/Handlers/SpamDetect.py ?
>
> Then, desirable pattern in this case seems to be
>
> ~Subject.*(\\u[0-9a-f]{4}){4}
^Subject:.*(\\u[0-9a-f]{4,5}){4}
(CJK Unified
Hi,
On 07/07/16 04:41, Mark Sapiro wrote:
> That should be
>
> ^Subject:.*[list of all Chinese characters here]
>
> except that if your list's preferred language is English and you haven't
> changed Mailman's character set for English from ASCII to UTF-8, the
> text you are matching against won'
On 7/9/16 1:24 AM, Manuel Goepfert wrote:
>
> Looking at some documentation I found out that this was a known problem and
> that it was addressed in on e of the mailman version. So I upgraded to 2.1.18
> that included that fix but I?m still facing this problem.
>
> Do you guys have the same iss
Hi All,
I’m facing since a few weeks if not even more some issue when a registered user
using yahoo.com email address sends an email to one of the list that mailman
manages.
As the list is configured to send emails on behalf of the user to the members
of the list, this triggers some anti spam