When executing spamc I do not get output and the exit status is 74
(EX_IOERR: IO error).
For example:
$ spamc -L spam
1844399, parsed as 1844399
Oct 22 03:08:20.505 [21322] dbg: channel: current version is 1844399, new
version is 1844399, skipping channel
Oct 22 03:08:20.505
On 10/21/2018 3:15 PM, John Hardin wrote:
> I've added some more bitcoin rules.
>
> It seems the masscheck corpus is very thin on the bitcoin extortion
> spams, the rule for that probably won't publish. If anyone wants it to
> put in your local rules just grab it out of my sandbox, or contact me
>
I've added some more bitcoin rules.
It seems the masscheck corpus is very thin on the bitcoin extortion spams,
the rule for that probably won't publish. If anyone wants it to put in
your local rules just grab it out of my sandbox, or contact me directly if
it's not obvious how to do that.
On 10/21/18 4:38 PM, Henrik K wrote:
On Sun, Oct 21, 2018 at 04:28:58PM +0200, Axb wrote:
On 10/21/18 4:21 PM, Henrik K wrote:
On Sun, Oct 21, 2018 at 04:07:40PM +0200, Axb wrote:
On 10/21/18 1:25 PM, Jari Fredriksson wrote:
./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
On Sun, Oct 21, 2018 at 04:28:58PM +0200, Axb wrote:
> On 10/21/18 4:21 PM, Henrik K wrote:
> >On Sun, Oct 21, 2018 at 04:07:40PM +0200, Axb wrote:
> >>On 10/21/18 1:25 PM, Jari Fredriksson wrote:
> >>>./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
> >>
> >>would be nice to
On 10/21/18 4:21 PM, Henrik K wrote:
On Sun, Oct 21, 2018 at 04:07:40PM +0200, Axb wrote:
On 10/21/18 1:25 PM, Jari Fredriksson wrote:
./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
would be nice to have it write \b to the cf
as in
body BTC_16LU6SWU
On Sun, Oct 21, 2018 at 04:07:40PM +0200, Axb wrote:
> On 10/21/18 1:25 PM, Jari Fredriksson wrote:
> >./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
>
> would be nice to have it write \b to the cf
>
> as in
> body BTC_16LU6SWU /16LU6SwUDdLsAy7XXHSMg7BRbA1kfDoBnZ/
> body
On 10/21/18 4:07 PM, Axb wrote:
On 10/21/18 1:25 PM, Jari Fredriksson wrote:
./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
would be nice to have it write \b to the cf
as in
body BTC_16LU6SWU /16LU6SwUDdLsAy7XXHSMg7BRbA1kfDoBnZ/
body BTC_16LU6SWU
On 10/21/18 1:25 PM, Jari Fredriksson wrote:
./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
would be nice to have it write \b to the cf
as in
body BTC_16LU6SWU /16LU6SwUDdLsAy7XXHSMg7BRbA1kfDoBnZ/
body BTC_16LU6SWU /\b16LU6SwUDdLsAy7XXHSMg7BRbA1kfDoBnZ\b/
> Henrik K kirjoitti 21.10.2018 kello 10.15:
>
>
> I wonder who's going to be the first to offer public bitcoin DNS blacklist,
> I could make plugin for it. :-)
>
> In the meantime, here's something to try..
>
> ./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
>
>
I wonder who's going to be the first to offer public bitcoin DNS blacklist,
I could make plugin for it. :-)
In the meantime, here's something to try..
./btcabuse.pl >btcabuse.cf.tmp && mv -f btcabuse.cf.tmp btcabuse.cf
#!/usr/bin/perl -w
use strict;
use
11 matches
Mail list logo