I am new to dspam and have a very old and spammy test account with a
mail delivery path like so:
postfix-transport -> dspam -> dovecot-deliver
The postfix transport is only used for my test account which is a 10+
year old email account that is all spam.
This is what I'm seeing in all the heade
On Wed, 12 May 2010 12:27:33 -0700
Alex wrote:
> Hello folks,
> In the previous versions of Dspam I had it working with Postfix and MySQL
> to train for falsely identified spam/innocent messages.
>
> When I installed newest Dspam 3.9.0
> I'm getting these messages in /var/log/dspam.log
> 21400:
Hello folks,
In the previous versions of Dspam I had it working with Postfix and MySQL
to train for falsely identified spam/innocent messages.
When I installed newest Dspam 3.9.0
I'm getting these messages in /var/log/dspam.log
21400: [05/12/2010 11:47:11] Signature retrieval for '%s' failed
21400
>> (...)
>> if (x > h) x = NULL [2]
>> ---
>>
>> For this last line [2], I understand that the goal is to ignore any
>> "spam-" or similar, if it is "after" a double CRLF ("empty line"), which
>> is probably intended to encode the headers/body boundary.
> Hi all,
>
Hello,
> I'm afraid I found kinda bug in the code which handles the detection of
> "spam-...@domain", to trigger retraining to false positives/negatives.
>
> Remember I had been struggling around this for days? Dspam was never
> considering my forwards to spam-cyri...@xxx, just doing
