[Pkg-dspam-misc] Bug#632392: dspam: configuration options for LMTP delivery seem to be ignored

[Ian Zimmerman]

On Sat, 2 Jul 2011 07:39:01 +0200
Julien Valroff <julien at debian.org> wrote:

Ian> I wanted to run dspam in daemon mode but I hate to have the open
Ian> port on 2424 (which would be unused since I only want to run the
Ian> client with --classify or --stdout).

Ian> So, after reading the README, I modified /etc/dspam/dspam.conf as
Ian> follows:

Ian> DeliveryHost            /run/dspam/=delivery
Ian> #DeliveryPort           2424
Ian> DeliveryIdent           localhost
Ian> DeliveryProto           LMTP

Julien> I don't really understand what your exact objective, but you can
Julien> easily use a socket rather than a TCP port if the server and the
Julien> client run on the same machine. Use the ServerDomainSocketPath
Julien> option rather than the ServerHost and ServerPort options.

Julien> I don't close this bug for now, but it seems it is more a
Julien> question of how to configure DSPAM than a real bug.

Yes, I'm sure it's a misunderstanding caused by the weak documentation.

I thought that the TCP socket on port 2424 I was seeing was what the
Delivery* options above influenced, that is, I thought it was for the
purpose of dspam actually delivering the mail or relaying it to the MTA.
In all honesty I don't understand how that part works, and I don't want
to use dspam that way.  I want to pass the message on stdin and get it
back on stdout, just like spamassassin does.

Apparently I was wrong, and the TCP socket is for the dspam client to
dspam server communication.  My remaining question then is, where _does_
the Delivery* suite of options get into play?

-- 
Ian Zimmerman
gpg public key: 1024D/C6FF61AD
fingerprint: 66DC D68F 5C1B 4D71 2EE5  BD03 8A00 786C C6FF 61AD
Rule 420: All persons more than eight miles high to leave the court.