Hi all,
I can't seem to train dspam for spam. I use a mail-alias s...@internal to
forward spam to, but from my mail logs it looks like dspam is looking up the
wrong signature ID. For example, I just received this spam message with in its
body:
In the logs I see right after forwarding it:
Jul 15 13:18:20 solfertje dspam[70969]: Signature retrieval for
'1,4c3eee7b286212860618039' failed
Jul 15 13:18:20 solfertje dspam[70969]: Unable to find a valid signature.
Aborting.
Jul 15 13:18:20 solfertje dspam[70969]: process_message returned error -5.
dropping message.
Jul 15 13:18:20 solfertje postfix/local[70910]: D66418053:
to=<s...@solfertje.internal>, relay=local, delay=0.36, delays=0.31/0/0/0.05,
dsn=2.0.0, status=sent (delivered to command: /usr/local/bin/dspam --user root
--class=spam --source=error)
Jul 15 13:18:20 solfertje postfix/qmgr[67598]: D66418053: removed
If I look in the dspam web-interface history, the message hasn't been marked as
spam either.
Just for the record, I've seen this behaviour (looking for the wrong signature
and not training a message as spam) in all my tests today.
Relevant virtual Uids are:
dspam=> SELECT * FROM dspam_virtual_uids WHERE uid IN (1,3);
uid | username
-----+-------------------------------------
3 | dal...@solfertje.student.utwente.nl
1 | s...@solfertje.internal
Both signatures appear to exist too:
dspam=> SELECT uid, signature, created_on FROM dspam_signature_data WHERE signat
ure IN ('3,4c3eee2e286211187712119', '1,4c3eee7b286212860618039');
uid | signature | created_on
-----+---------------------------+------------
3 | 3,4c3eee2e286211187712119 | 2010-07-15
1 | 1,4c3eee7b286212860618039 | 2010-07-15
Note: I don't know how long this error has existed in my setup, as until
recently I was forwarding spam to the wrong domain alias (wrong virtual uid)
and after I fixed that I had to teach Postfix to accept mails looping back to
itself before it would accept messages to s...@internal - I probably thought I
had it working before because the messages got at least accepted when using the
wrong domain name.
My setup uses dspam 3.9.0 as a Postfix 2.6.2 filter with PostgreSQL 8.3.11 as
backend storage. It's been migrated through several upgrades of both dspam and
Postres though, I think I started out with dspam 3.4 or 3.5 and Postgres 8.1
and I have been tweaking indexes and such in the database to improve
performance in older versions (I used to get timeouts from Postfix because
dspam took >15 minutes to process some messages, but that's years ago).
Also, the statistics in the performance tab say:
Since last reset
0 missed 0 missed
0 caught 0 delivered
100% caught 0% missed
Total processed by filter
0 missed 0 missed
0 caught 27 delivered
>From corpus
0 fed 0 fed
That can't be right! I just went through my history marking missed spam
messages by hand, this database is over a year old too! There should be
messages delivered, caught, etc.
I'm not sure this is related to the other problem - it's probably a separate
problem from the looks of it...
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:1126,4c3ef727286215484755600!
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
