On Thu, Apr 16, 2009 at 11:20 AM, Hugo Monteiro
<[email protected]> wrote:
> alexus wrote:
>>
>> On Thu, Apr 16, 2009 at 5:26 AM, Hugo Monteiro <[email protected]>
>> wrote:
>>
>>>
>>> alexus wrote:
>>>
>>>>
>>>> Apr 16 04:11:26 mx1 dspam[77779]: No such feature 'chained'
>>>> Apr 16 04:11:26 mx1 dspam[77779]: Unable to attach DSPAM context
>>>> Apr 16 04:11:26 mx1 dspam[77779]: process_message returned error -2.
>>>> delivering.
>>>>
>>>> I'm getting these messages in my /var/log/maillog
>>>>
>>>> and on top of that, instead of what it reffers to be "deliverying" I
>>>> only get this
>>>>
>>>> Return-Path: <[email protected]>
>>>> Delivered-To: [email protected]
>>>> Received: (qmail 77796 invoked from network); 16 Apr 2009 04:11:40 -0000
>>>> Received: by simscan 1.4.0 ppid: 77790, pid: 77791, t: 0.0229s
>>>>        scanners: regex: 1.4.0 clamav: 0.95/m:50/d:9244 spam: 3.2.5
>>>>
>>>> and this is my full email, I just have few lines of headers, without
>>>> even rest of headers nor body of email is MIA
>>>>
>>>> someone please help
>>>> thanks in advance
>>>>
>>>>
>>>>
>>>
>>> Hello Alexus,
>>>
>>>
>>> From the UPGRADING file, on 3.8.0 source distribution, you'll see
>>> something
>>> like:
>>>
>>> --- snip ---
>>>
>>> UPGRADING FROM 3.6
>>> ------------------
>>>
>>> 1. Add 'Tokenizer' setting to dspam.conf
>>>  The 'Tokenizer' setting in 3.8.0 replaces tokenizer definitions in the
>>>  "Feature" clause of previous version configurations. See src/dspam.conf
>>>  (after make) for more information about this seting.
>>>
>>> --- snip ---
>>>
>>>
>>> So, where you would have Feature chained, prior to 3.8.0, you should now
>>> have Tokenizer chained.
>>>
>>> Has for the crippled messages... if you set spam=no in your simcontrol
>>> file,
>>> i.e. disable dspam call, do you still observe the same? (don't forget to
>>> call simscanmk after the changes)
>>>
>>> Also please let us know how did you ./configure simscan. The way dspam is
>>> being called is rather important.
>>>
>>> Regards,
>>>
>>> Hugo Monteiro.
>>>
>>> --
>>> ci.fct.unl.pt:~# cat .signature
>>>
>>> Hugo Monteiro
>>> Email    : [email protected]
>>> Telefone : +351 212948300 Ext.15307
>>> Web      : http://hmonteiro.net
>>>
>>> Centro de Informática
>>> Faculdade de Ciências e Tecnologia da
>>>                  Universidade Nova de Lisboa
>>> Quinta da Torre   2829-516 Caparica   Portugal
>>> Telefone: +351 212948596   Fax: +351 212948548
>>> www.ci.fct.unl.pt             [email protected]
>>>
>>> ci.fct.unl.pt:~# _
>>>
>>>
>>>
>>
>> my setup is LWQ type of setup with some minor modifications/tweaks
>> here and there
>> I also use simscan, i configured simscan with following options
>>
>> ./configure --enable-per-domain --enable-attach --enable-dspam=n
>>
>
> You have just said that you DON'T want to compile simscan with dspam support
> -> "--enable-dspam=n"
>
> My personal sugestion, for the dspam related options, taking in
> consideration what you have pasted here would be something like the
> following:
>
> --enable-per-domain=y --enable-attach=y --enable-dspam=y
> --enable-dspam-path=/usr/bin/dspam --enable-dspam-user=y
> --enable-dspam-args="--client --deliver=innocent"

tried that now too dspam-args and now i'm back where I was before...

Apr 16 19:10:09 mx1 dspam[23705]: No such feature 'chained'
Apr 16 19:10:09 mx1 dspam[23705]: Unable to attach DSPAM context
Apr 16 19:10:09 mx1 dspam[23705]: process_message returned error -2.
delivering.

and my message gets cut right after, just like that...

Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 23595 invoked from network); 16 Apr 2009 19:05:41 -0000
Received: by simscan 1.4.0 ppid: 23589, pid: 23590, t: 0.0246s
         scanners: regex: 1.4.0 clamav: 0.95/m:50/d:9247 spam: 3.2.5


>> --enable-spam-passthru --enable-spam --enable-spamc-args=-U
>> /tmp/spamd.sock --enable-received --enable-regex=y
>> CPPFLAGS=-I/usr/local/include/ LDFLAGS=-L/usr/local/lib/
>>
>> and i configure dspam with following options
>>
>> ./configure --enable-debug --enable-virtual-users
>>
>
> Also here i would advise you to consider some other options. At least the
> following ones:
>
> --enable-domain-scale --enable-signature-headers --enable-daemon
> --with-storage-driver=hash_drv
>
>> the earlier problem that i've had, which is produced in
>> /var/log/qmail/smtpd/current
>>
>>
>> @4000000049e6978a0df9cc04 execve returned -1/13
>>
>>
>> i fixed, by changing permissions for /usr/local/bin/dspam
>>
>> r...@mx1 /home/vpopmail/domains/8au.net/postmaster/Maildir 571$ ls -la
>> /usr/local/bin/dspam
>> -r-s--x---  1 simscan  mail  364532 Apr 16 03:29 /usr/local/bin/dspam
>> r...@mx1 /home/vpopmail/domains/8au.net/postmaster/Maildir 572$
>>
>>
>
> I personally see no point in changing ownership of the dspam binary to the
> user simscan. You can give execution permission to everyone and then use the
> "Trust" directive in dspam.conf to fine tune who has rights to act in the
> name of others, while using the dspam --user switch.
>
>> now I'm facing new problem
>>
>> Apr 16 04:11:40 mx1 dspam[77792]: No such feature 'chained'
>> Apr 16 04:11:40 mx1 dspam[77792]: Unable to attach DSPAM context
>> Apr 16 04:11:40 mx1 dspam[77792]: process_message returned error -2.
>> delivering.
>>
>>
>
> weird to see it complain about feature 'chained' while not having anything
> like that on dspam.conf file.
>
>> this is my dspam.conf
>>
>> Algorithm graham burton
>> AllowOverride enableBNR
>> AllowOverride enableWhitelist
>> AllowOverride optIn optOut
>> AllowOverride showFactors
>> AllowOverride signatureLocation
>> AllowOverride spamAction spamSubject
>> AllowOverride statisticalSedation
>> AllowOverride trainingMode
>> AllowOverride whitelistThreshold
>> Feature whitelist
>> HashAutoExtend          on
>> HashConnectionCache     10
>> HashExtentSize          49157
>> HashMaxExtents          0
>> HashMaxSeek             10
>> HashPctIncrease 10
>> HashRecMax              98317
>> Home /usr/local/var/dspam
>> LocalMX 127.0.0.1
>> Notifications   off
>> OnFail error
>> Opt out
>> PValue bcr
>> Preference "showFactors=on"
>> Preference "signatureLocation=message"  # 'message' or 'headers'
>> Preference "spamAction=quarantine"
>> ProcessorBias on
>> ProcessorURLContext on
>> PurgeHapaxes    30          # Tokens with less than 5 hits (hapaxes)
>> PurgeHits1I     15          # Tokens with only 1 innocent hit
>> PurgeHits1S     15          # Tokens with only 1 spam hit
>> PurgeNeutral    90          # Tokens with neutralish probabilities
>> PurgeSignatures 14          # Stale signatures
>> PurgeUnused     90          # Unused tokens
>> StorageDriver /usr/local/lib/libhash_drv.so
>> SystemLog on
>> TestConditionalTraining on
>> Tokenizer word
>> TrainingMode teft
>> Trust daemon
>> Trust mail
>> Trust mailnull
>> Trust qmaild
>> Trust root
>> Trust smmsp
>> TrustedDeliveryAgent "/usr/libexec/mail.local"
>> UserLog   on
>> WebStats on
>>
>>
>
> I had no knowledge of a "word" tokenizer. I've only heared of the following:
>
> chained
> noise
> tb
> whitelist
> sbph
>
> Where is that option documented?

sorry, missed this one...

#
# Tokenizer: Specify the tokenizer to use. The tokenizer is the piece
# responsible for parsing the message into individual tokens. Depending on
# how many resources you are willing to trade off vs. accuracy, you may
# choose to use a less or more detailed tokenizer:
#   word    uniGram (single word) tokenizer
#           Tokenizes message into single individual words/tokens
#           example: "free" and "viagra"
#   chain   biGram (chained tokens) tokenizer (default)
#           Single words + chains adjacent tokens together
#           example: "free" and "viagra" and "free viagra"
#   sbph    Sparse Binary Polynomial Hashing tokenizer
#           Creates sparse token patterns across sliding window of 5-tokens
#           example: "the quick * fox jumped" and "the * * fox jumped"
#   osb     Orthogonal Sparse biGram
#           Similar to SBPH, but only uses the biGrams
#           example: "the * * fox" and "the * * * jumped"
#
Tokenizer chain

this is default vaule, so I tried changing chain to "word", and then i
don't get that message in syslog, but not sure if this is good
solution so to speak...

> (Hint: try replacing Tokenizer word for Tokenizer chained and add Tokenizer
> whitelist while you're at it)

I revese it back to chain as you suggest, but I'm not sure what you
mean by second part "add Tokenizer to whitelist"

> Regards,
>
> Hugo Monteiro.
>
> --
> ci.fct.unl.pt:~# cat .signature
>
> Hugo Monteiro
> Email    : [email protected]
> Telefone : +351 212948300 Ext.15307
> Web      : http://hmonteiro.net
>
> Centro de Informática
> Faculdade de Ciências e Tecnologia da
>                   Universidade Nova de Lisboa
> Quinta da Torre   2829-516 Caparica   Portugal
> Telefone: +351 212948596   Fax: +351 212948548
> www.ci.fct.unl.pt             [email protected]
>
> ci.fct.unl.pt:~# _
>
>



-- 
http://alexus.org/

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to