Rob Klingsten wrote:
Ok, just when you think you have it all figured out ... :(
Thank you very much for the info, I will go back to the drawing board
for my delivery stage from dspam. Thought it was all working well.
consider running dspam in "relay" mode
http://dspam.nuclearelephant.com/text/relay-howto.txt
In your dspam.conf, you should have something like:
DeliveryHost 127.0.0.1
DeliveryPort 10025
DeliveryProto SMTP
...
ServerPort 10024
ServerMode standard
...
in main.cf, something like
content_filter = lfilter:[127.0.0.1]:10024
where "lfilter" is defined in master.cf like this
lfilter unix - - n - 2 lmtp
...
note: dspam gets mail with LMTP and passes it back to postfix with SMTP.
This is how my old server is set up, and while it works pretty well,
dspam running as a daemon loses connection to the Mysql database on the
same server and stops filtering the mail. I tried a bunch of things with
timeouts and whatnot, but I never did get it fixed other than a cron to
kill dspam and restart it every 4 hours. Yuck.
maybe you could reduce the number of simultaneous connections (the
example I posted uses "2" but you can probably increase it a little).
I don't know if dspam has a config param to make it return a failure in
such cases. Otherwise, it is possible to queue mail that wasn't filtered
and pass it back to dspam, but this requires a lot of care (to avoid an
infinite loop, and/or making the problem worse).
anyway, the dspam users list is probably a better place to get hints on
this. the dspam dev list would have been even better but it seems dead
now...
