[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dspam-users
Subject:    [Dspam-user]  Dspam is not tagging spam mail
From:       Paul Goyette <paul () whooppee ! com>
Date:       2016-01-18 2:54:40
Message-ID: Pine.NEB.4.64.1601180848070.1054 () pokey ! whooppee ! com
[Download RAW message or body]

I was having this same problem.  I've verified that my configuration has

     Preference "spamAction=tag"
     Preference "spamSubject=***SPAM***"

I've verified that the user (me!) does not have any personal dspam 
preference file, so nothing to override these Preferences.

Innocent messages are getting the X-DSPAM headers added correctly.  But 
new Spam messages are NOT getting the headers, and they are not having 
the Subject line updated.

Here's a sample entry from my dspam log file:

    1453074674      S       "Grocery Coupons" <GroceryCoupons@oolent.top>
    569c28f2162181671114135 Looking  for-  ways-- to-- lower-  the-- gorcery
    - bill? Start with these coupons options.      0.016069        paul
    Tagged  <713310160060571330303349@42jwjmf1.oolent.top>

dspam is being invoked from postfix, via the following postfix transport 
entry (in master.cf)

dspam   unix    -       n       n       -       10      pipe
   flags=Ru user=dspam
   argv=/usr/pkg/bin/dspam --deliver=innocent,spam --user $user -i -f $sender --$recipient

(the last two lines, from argv= to $recipient, are really on a single 
line but my mailer insists on wrapping)

I previously had also enabled

     Preferences "tagSpam=on"

but have since removed that line based on the latest reply from Tom 
Hendrikx which said:

 	Check the README, tagSpam is for something else.

Voila!  Once I remove the errant tagSpam line from the config, it all 
starts to work correctly!

Apparently, if tagSpam is requested, but the tag file (or TxtDirectory) 
cannot be found, dspam gives up on the message and fails to apply the 
spamSubject update and fails to add the X-DSPAM headers.

To me, this sounds like a bug.  If the tagSpam file can't be found, it 
should log an error (via syslog?) and continue with the rest of message 
processing.  (At the very least, it should give an error message that is 
sufficient to identify the problem.)

:)



+------------------+--------------------------+------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
[prev in list] [next in list] [prev in thread] [next in thread]