Your message dated Wed, 07 Dec 2016 00:59:47 -0500
with message-id <3770552.Oy5eqbQGIU@kitterma-e6430>
and subject line Re: /usr/bin/spfmilter:
/var/run/spf-milter-python/spfmiltersock unsafe
has caused the Debian Bug report #725974,
regarding /usr/bin/spfmilter: /var/run/spf-milter-python/spfmiltersock unsafe
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
725974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725974
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages spf-milter-python depends on:
ii adduser 3.113+nmu3
ii lsb-base 4.1+Debian12
ii python 2.7.5-5
ii python-milter 0.9.8-2
ii python-spf 2.0.8-2
spf-milter-python recommends no packages.
Versions of packages spf-milter-python suggests:
ii sendmail 8.14.4-4.1
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 23 Jun 2014 00:23:37 -0400 Scott Kitterman <[email protected]>
wrote:
> 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
Closing after two years of no response.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
