[Dspam-user] Problems with DSPAM integration in postfix

[Holger L. <lis...@li...>]

Hi.

First at all: DSPAM rocks! I use it for many years now and it nearly
perfect. Great work.

But, as the time goes by, I will setup a new server now. With this
server switch I also expect to move from Courier to Dovecot,
especially because Dovecot support Sieve directly. The big BUT is, that
I currently filter spam via Courier's maildrop. The current maildroprc
contains the following line for filtering:

-- snip --
xfilter "/usr/bin/dspamc --deliver=innocent,spam --feature=chained,noise
 --user ${LOGNAME} --client --stdout"
-- snap --

It works quite good. But to have all the benefits of Dovecot I would
change to Dovecots deliver as the new LDA. This is why I try integrating
DSPAM into the
postfix transfer process. I try to integrate dspam with the following steps:

1. Defining a new transport "dspam" in master.cf
-- snip --

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

-- snap --

2. Set the content filter to that transport and limit the number of
users passed to dspam:
-- snip --
content_filter = dspam
dspam_destination_recipient_limit = 1
-- snap --

OK, just like described in the net. The transport is called so far, if I
deliver a new message via telnet like this:
-- snip --
ehlo localhost
mail from: one...@ex...
rcpt to: one...@my...
data
From: one...@ex...
To: one...@my...
Subject: Test
Testing...
.
quit
-- snap --

And now the transport fails with the following errors in the logs:

-- snip --
postfix/pipe[6477]: fatal: get_service_attr: unknown username: dspam
postfix/qmgr[18162]: warning: private/dspam socket: malformed response
postfix/qmgr[18162]: warning: transport dspam failure -- see a previous
warning/fatal/panic logfile record for the problem description
-- snap --

Ok, "unknown username: dspam" looks like the user defined in master.cf
transport definition does not exist. But id shows that it is out there:

-- snip --
~# id dspam
uid=111(dspam) gid=113(dspam) groups=113(dspam)
-- snap --

So, what is the problem here?

Here are the (maybe) missed basic-infos:
* Debian 5 64bit
* Postfix 2.5.5-1.1, running in the default chroot
* DSPAM 3.6.8

Hoping for help and wish you all a nice friday.

So long,
Holger