On Wed, 20 Apr 2016 06:42:07 +0800 (PHT)
Paul Goyette wrote:
> I've got a real small set-up (two users, total of maybe 500 messages
> per day), and really have no justification for adding complexity (and
> the learning curve) for sqlite or similar. So I'm just using the
> simple hash storage driv
On Mon, 11 Apr 2016 01:19:37 +0100
RW wrote:
> Content-Type: multipart/alternative;
> boundary=001a113eb6969361b20530203ac7
That should, of course, have been one line.
--
Find and fix application performance
I've noticed that DSPAM can slightly modify the mime layout when mail
is piped through it with --stdout. It's a problem if the output is
piped through another filter, such as SpamAssassin, because it
changes the DKIM body hash.
In the example below two extra blank lines are inserted, one after e
On Thu, 11 Jun 2015 19:06:50 -0400
Phil Stracchino wrote:
> On 06/11/15 16:07, Al Zick wrote:
> > At first, it looked
> > like dspam was working, but then I realized that I could not
> > retrain. After doing more research I found where people were saying
> > that you can not retrain with hash a
On Wed, 03 Dec 2014 10:39:41 +
Steve Freegard wrote:
> > you would install that seriously on a sensible server?
> > if a project is dead it should say that clear and close
> >
> >
>
> To add my voice to the others; I started using DSPAM fairly recently
> and whilst I don't use the web interfa
I'm running dspam 3.9.0 built from the FreeBSD port, and it seems to
be struggling with multi-byte UTF-8 in quoted-printable and base64 mime
sections.
I get some spam in UTF-8 Greek and, since I don't receive any legitimate
mail in Greek, it should be caught easily. What I'm seeing is that
most a
I notice that some of the tokens in the X-DSPAM-Factors header occur
multiple times.
Is this a feature or bug?
--
___
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
On Wed, 22 Apr 2009 18:48:01 +1000
Doug Laidlaw wrote:
> I am new to dspam. Mine is a simple workstation, not a server. I
> have tried white-listing, but find that it causes more problems than
> it solves. I have been running SpamAssassin, but it seems powerless
> to filter any of the current