On Thu, 28 Jun 2018, Zinski, Steve wrote:
I see that a lot in sextortion emails. So far, I’ve seen the word “bitcoin”
encoded (obfuscated) the following ways:
bitc%D0%BEin
bit%D1%81oin
bit%D1%81%D0%BEin
And the word “wallet” as:
w%D0%B0ll%D0%B5t
These sextortion scammers are clever. So, ins
I see that a lot in sextortion emails. So far, I’ve seen the word “bitcoin”
encoded (obfuscated) the following ways:
bitc%D0%BEin
bit%D1%81oin
bit%D1%81%D0%BEin
And the word “wallet” as:
w%D0%B0ll%D0%B5t
These sextortion scammers are clever. So, instead of filtering on the word
“bitcoin”, I n
On 6/28/2018 1:46 PM, users-digest-h...@spamassassin.apache.org wrote:
Subject:
Re: Using UTF-8 characters to avoid spam filter rules.
From:
RW
Date:
6/26/2018 12:12 PM
To:
users@spamassassin.apache.org
On Tue, 26 Jun 2018 00:33:11 -0400
Mark London wrote:
Hi - Some of the words in the spam
On 27 Jun 2018, at 22:17, J Doe wrote:
I went back to “man Mail::SpamAssassin::Conf” and can see mention
of the shortcircuit plugin . . . is there more documentation (perhaps
in another man or perldoc), where the shortcircuit keyword is
mentioned ?
perldoc Mail::SpamAssassin::Plugin::Shortci
On 28/06/2018 04:17, J Doe wrote:
I went back to “man Mail::SpamAssassin::Conf” and can see mention of the
shortcircuit plugin . . . is there more documentation (perhaps in another man
or perldoc), where the shortcircuit keyword is mentioned ?
I'd say a good starting point would be
https://
