Calling dspam from amavisd-new fails

Bug #554063 reported by Benjamin Börngen-Schmidt on 2010-04-02
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
amavisd-new (Debian)
New
Undecided
Unassigned
amavisd-new (Ubuntu)
Low
Unassigned
Nominated for Maverick by Dave Walker

Bug Description

Binary package hint: amavisd-new

Description: Ubuntu 9.04
Release: 9.04

amavisd-new:
  Installiert: 1:2.6.2-2ubuntu2
  Kandidat: 1:2.6.2-2ubuntu2
  Versions-Tabelle:
 *** 1:2.6.2-2ubuntu2 0
        500 http://ftp-stud.hs-esslingen.de jaunty/main Packages
        100 /var/lib/dpkg/status

Expected Result:
Nice and smooth call of dspam

Actual Result:
l amavis[18784]: (18487-01) (!)run_command: child process [18784]: run_command: failed to exec /usr/bin/dspam --debug --stdout --deliver=spam,innocent --mode=tum --feature=chained,noise --user amavis: 2 at /usr/sbin/amavisd-new line 2996, <GEN31> line 415.
 amavis[18487]: (18487-01) (!)WARN: DSPAM problem, exit 6, result=

Description:
When amavisd-new calls dspam, it uses arguments which are not supported by dspam.

See discussion on amavisd-user list http://groups.google.com/group/mailing.unix.amavis-user/browse_thread/thread/184f742018a55b45/5e78478985d1a4bc?#5e78478985d1a4bc

I attached a patch which removes the unnecessary arguments from the dspam call. Afterwards dspam works fine so far.

tags: added: patch
Mathias Gug (mathiaz) wrote :

Thanks for the patch. In Lucid there is a note about the correct option to use:

  # [ qw(--stdout --classify --deliver=innocent,spam
  # --mode=tum --tokenizer=chained,noise
  # --user), $daemon_user ],
  # # use option --feature instead of --tokenizer with dspam < 3.8.0
  # ],

It may be better to provide the correct options according to the dspam version that is used available in the archive.

Changed in amavisd-new (Ubuntu):
status: New → Confirmed
importance: Undecided → Low

According to a dSpam Developer, who posted in the discussion there has never been an option --tokenizer, so its just wrong in any case. I guess this also affects earlier Versions of Ubuntu.

Just for the record, calling dspam with the option --debug makes amavis fail to interpret to result. Also --classify does not work, since amavis can not handle the summarized report from dspam.

Dave Walker (davewalker) on 2010-08-02
Changed in amavisd-new (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers