On Thursday, October 10, 2013 15:19:20 you wrote: > Package: spf-milter-python > Version: 0.8.18-2 > Severity: normal > File: /usr/bin/spfmilter > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > > * What led up to the situation? > looking in /var/log/error > * What exactly did you do (or not do) that was effective (or > ineffective)? > tail /var/log/error > * What was the outcome of this action? > Lots of lines such as: > > Oct 10 15:13:57 nigelhorne sm-mta[15212]: r9AEDvjm015212: Milter (spf): > local socket name /var/run/spf-milter-python/spfmiltersock unsafe * What > outcome did you expect instead? > > No lines such as the above. > > *** End of the template - remove these lines *** > > spf-milter is running: > > root@nigelhorne:/var/log/syslog/local# ps ax | fgrep -i spfmilter.py > 15642 ? Sl 0:00 /usr/bin/python /usr/bin/spfmilter.py > 19074 pts/1 S+ 0:00 fgrep -i spfmilter.py > root@nigelhorne:/var/log/syslog/local# > > But /var/run/spf-milter-python/spfmiltersock doesn't exist: > > root@nigelhorne:/var/log/syslog/local# ls -l /var/run/spf-milter-python/ > total 4 > -rw-r--r-- 1 spf-milter-python spf-milter-python 6 Oct 10 15:14 > spfmilter.pid root@nigelhorne:/var/log/syslog/local# > > I have not changed spfmilter.cfg.
Do you still have this problem? As nearly as I can determine, it's generally a result of the milter not being running. In this case it is, but it looks like the socket didn't get correctly created. If this happens and you restart the milter manually, does it go away? I'm having trouble recreating the problem. Scott K
signature.asc
Description: This is a digitally signed message part.
