On July 30, 2015 2:40:35 AM CEST, RW wrote:
> The plugin is on by default and use_hashcash defaults to 1, but you
> need to set hashcash_accept to an appropriate value
That's disappointing. For me that barely counts as "on by default". I was
thinking that implementing hashcash would help get m
On Fri, 31 Jul 2015 13:36:21 +0200
Christian Jaeger wrote:
> On July 30, 2015 2:40:35 AM CEST, RW
> wrote:
> > The plugin is on by default and use_hashcash defaults to 1, but you
> > need to set hashcash_accept to an appropriate value
>
> That's disappointing. For me that barely counts as "on
Am 31.07.2015 um 16:37 schrieb RW:
On Fri, 31 Jul 2015 13:36:21 +0200
Christian Jaeger wrote:
On July 30, 2015 2:40:35 AM CEST, RW
wrote:
The plugin is on by default and use_hashcash defaults to 1, but you
need to set hashcash_accept to an appropriate value
That's disappointing. For me t
nevermind, envelope recipient, but that's also easy and contained in the
Received headers
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by mail-gw.thelounge.net (THELOUNGE GATEWAY) with SMTP id 3mjWRW6GLQz1l
for ; Fri, 31 Jul 2015 16:37:43 +0200 (CEST)
Am 31.07.2015 um 16:4
On 31 Jul 2015, at 7:36, Christian Jaeger wrote:
On July 30, 2015 2:40:35 AM CEST, RW
wrote:
The plugin is on by default and use_hashcash defaults to 1, but you
need to set hashcash_accept to an appropriate value
That's disappointing. For me that barely counts as "on by default". I
was
On Fri, 31 Jul 2015 16:47:34 +0200
Reindl Harald wrote:
> nevermind, envelope recipient, but that's also easy and contained in
> the Received headers
>
>
> Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
> by mail-gw.thelounge.net (THELOUNGE GATEWAY) with SMTP id
> 3mjWRW6GLQz1
On July 31, 2015 4:37:14 PM CEST, RW wrote:
> SA usually gets envelope information from headers. Since there are
> several headers that could contain the envelope recipient, it would
> need to be configured, so still wouldn't work by default.
That's why I mentioned RECIPIENT. The MTA knows where
On July 31, 2015 4:51:02 PM CEST, Bill Cole
wrote:
> John Levine wrote a definitive debunking of e-postage schemes
> including
> hashcash over a decade ago (http://www.taugh.com/epostage.pdf) and
> published an update (substantively unchanged) via Virus Bulletin in
> 2009
> (https://www.virusb
On 31 Jul 2015 17:57:28 +0200
Christian Jaeger wrote:
> On July 31, 2015 4:37:14 PM CEST, RW
> wrote:
> > SA usually gets envelope information from headers. Since there are
> > several headers that could contain the envelope recipient, it would
> > need to be configured, so still wouldn't work by
I run spamassassin -r from cron nightly. Last night I got this output:
Jul 30 23:00:11.830 [31065] warn: reporter: no reporting methods
available, so couldn't report
Jul 30 23:00:11.830 [31065] warn: spamassassin: warning, unable to
report message
Jul 30 23:00:11.830 [31065] warn: spamassassin: f
On July 31, 2015 9:13:03 PM CEST, RW wrote:
> On 31 Jul 2015 17:57:28 +0200
> Christian Jaeger wrote:
>
> > On July 31, 2015 4:37:14 PM CEST, RW
> > wrote:
> > > SA usually gets envelope information from headers. Since there are
> > > several headers that could contain the envelope recipient, it
Christian Jaeger wrote:
> On July 31, 2015 9:13:03 PM CEST, RW wrote:
>> On 31 Jul 2015 17:57:28 +0200
>> Christian Jaeger wrote:
>>
>>> On July 31, 2015 4:37:14 PM CEST, RW
>>> wrote:
SA usually gets envelope information from headers. Since there are
several headers that could contain
On Fri, 31 Jul 2015 12:38:00 -0700
Ian Zimmerman wrote:
> I run spamassassin -r from cron nightly. Last night I got this
> output:
>
> Jul 30 23:00:11.830 [31065] warn: reporter: no reporting methods
> available, so couldn't report
> Jul 30 23:00:11.830 [31065] warn: spamassassin: warning, unabl
On Fri, 31 Jul 2015, RW wrote:
[snip..]
I'd also
like to clarify more generally what spamassassin -r does. From a
recent thread here I learned that it also does the equivalent of
sa-learn --spam. Right? So presumably it doesn't consider this a
"reporting method" or how could it be not availa
On 2015-07-31 18:28 -0500, David B Funk wrote:
> >Reporting is separate from learning.
>
> It is the case that "spamassassin -r" is supposed to report and learn.
> However it isn't quite the same as "sa-learn --spam" in that unlike
> "sa-learn --spam" it won't override the spam learn prohibition
On Fri, 31 Jul 2015, RW wrote:
On Fri, 31 Jul 2015 16:47:34 +0200
Reindl Harald wrote:
nevermind, envelope recipient, but that's also easy and contained in
the Received headers
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by mail-gw.thelounge.net (THELOUNGE GATEWAY) with
16 matches
Mail list logo
