On 06/15/2011 09:27 PM, Wietse Venema wrote:
> JKL:
>> On 06/15/2011 06:17 PM, Scott Kitterman wrote:
>>> On Wednesday, June 15, 2011 10:43:40 AM J4K wrote:
>>>> Hi there,
>>>>
>>>> Spamass-milter has stopped processing messages from Postfix. I have
>>>> tested the milter socket and it works. To test that it worked I used :-
>>>> http://www.itg.uiuc.edu/itg_software/milter_watch/ and Spamass-milter
>>>> rejected the spammy messages.
>>>> The spam threshold on the spam milter is 11, and it seems that any
>>>> message is getting through. However, the backend SpamAssassin is
>>>> correctly tagging the messages as spam.
>>>>
>>>> My objective of mailing this list is to either rule out Postfix config
>>>> problems or not.
>>>>
>>>> Now I think I know that the milter is functioning, I would like someone
>>>> to check my config to ensure that is it correct. If some one has the
>>>> time:-
>>>>
>>>> # postconf -n | grep milter
>>>> milter_default_action = tempfail
>>>> non_smtpd_milters = unix:/dkim-filter/dkim-filter.sock
>>>> smtpd_milters = unix:/clamav/clamav-milter.ctl,
>>>> unix:/spamass/spamass.sock, unix:/dkim-filter/dkim-filter.sock
>>> Debian ships postfix running in a chroot by default. You either need to
>>> change
>>> master.cf to have it not run in the chroot or arrange to have both these
>>> sockets available within the chroot. This is (IME) generally easier to
>>> manage
>>> with TCP sockets than with Unix sockets.
>>>
>>> Scott K
>> Hi Scott,
>>
>> This is not a new set-up. The system has been running unchanged
>> since January this year.
>>
>> The server, with the three milters, was running perfectly well until a
>> few weeks ago. All milters sockets are inside a place where Debian
>> postfix can get to.
> When something stops working, then something has changed. You need
> to find out what has changed. Postfix does not change spontaneously.
>
> Wietse
You are quite correct. Something did change, but I don't recall making
the change. Hence the desire to check the configuration.
