On 31 Jul 2015, at 13:23, Christian Jaeger wrote:
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 Viru
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
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 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
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
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 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 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 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
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
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
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
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 29 Jul 2015 20:55:55 +0200
Christian Jaeger wrote:
> Hi
>
> I've implemented (or at least so I thought) Hashcash for my outgoing
> mail (in a Perl wrapper around qmail-remote that I already had to do
> DKIM), using the `hashcash` tool as provided by Debian, using the
> `-X` command-line option
Hi
I've implemented (or at least so I thought) Hashcash for my outgoing mail (in a
Perl wrapper around qmail-remote that I already had to do DKIM), using the
`hashcash` tool as provided by Debian, using the `-X` command-line option. This
tool returns multi-line headers if the email address the
15 matches
Mail list logo
