Hi
I'm seeing X-Spam-Status headers from some other installation come
with =$x appended to the individual matches, which evidently helps
figuring out why a mail is being classified the way it is. I've spent
more than an hour on googling and rtfm but couldn't figure it
out. Also, grep does not turn
I've noticed Haraka (and I've used software by Matt Sergeant before,
AxKit and qpsmtpd). I'm using qpsmtpd as the SMTP daemon already
(that's how you do spam filtering in a Qmail setup, and qmail is the
original delivery backend for qpsmtpd), which has the same
architecture as Haraka (single proces
I don't have any problems with Qmail. I can code when needed for the missing
parts. The unsolved problems I have with my mail setup would not be solved by
going with another MTA. I like and know Qmail's configuration, modularity and
security track record. This way my time is spent learning how t
Hi Tom,
You write that you're using Qmail. If you'd like to implement DKIM
signing for your outgoing mail (for possibly better deliverability and
also so that you could verify incoming mail and be sure that it's not
your own by verifying the DKIM signature), then perhaps you're
interested in what
On August 2, 2015 7:36:36 PM CEST, RW wrote:
> In future start with
>
> man spamassassin
>
> which will lead you to:
>
> CONFIGURATION
>Mail::SpamAssassin::Conf SpamAssassin configuration files
I think I've actually seen this page rececntly. I also remember having looked
throug
On August 2, 2015 6:40:10 PM CEST, Reindl Harald wrote:
> no idea what you are talking about by saying
> "I can't find anything about this in the docs"
I'm talking about the bundled docs. The man / perldoc pages of
Mail::SpamAssassin::Plugin::Bayes / Mail::SpamAssassin::*Bayes* and the default
On August 2, 2015 5:15:08 PM CEST, Reindl Harald wrote:
>
> Am 02.08.2015 um 14:57 schrieb Roman Gelfand:
> > Could somebody post a successful bayes configuration?
>
> ??
>
> you just need to *train* it for ham *and* spam
I think I remember from past use of SA that it only uses the bayes datab
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 th
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 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
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
12 matches
Mail list logo
