Your message dated Wed, 13 Sep 2006 01:02:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#373812: fixed in spamass-milter 0.3.1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: spamass-milter
Version: 0.3.1-1
I dectect a communication error between sendmail and spamass-milter,
if /var/run is on a tmpfs. Sendmail is started after spamass-milter
and therefor the socket cannot be created. One solution is an
alternative place for SOCKET: /var/run/spamass-milter/spamass.sock.
This could be specified in the /etc/default/spamass-milter file:
# Socket location
SOCKET=/var/run/spamass-milter/spamass.sock
And this modification in /etc/init.d/spamass-milter creates the Socket
directory, if not available:
--- spamass-milter.ORIG 2006-06-15 17:58:01.000000000 +0200
+++ spamass-milter 2006-06-15 18:10:31.000000000 +0200
@@ -52,6 +52,10 @@
start)
echo -n "Starting $DESC: "
+ # create the socket directory, if /var/run on tempfs
+ DIRECTORY=`echo $SOCKET | sed 's!/[^/]\+$!!'`
+ [ ! -d $DIRECTORY ] && mkdir $DIRECTORY
+
start-stop-daemon --start -p $PIDFILE --exec $DAEMON -- -P
$PIDFILE -f -p $SOCKET $OPTIONS
echo "${DAEMON}"
I have tested this modification and think it works. I think also this
should be done in every case, because the File System Hierarchy
Standard says:
Files under this directory [/var/run] must be cleared (removed or
truncated as appropriate) at the beginning of the boot process.
See: http://www.pathname.com/fhs/pub/fhs-2.3.html#THEVARHIERARCHY
Best regards
Herbert Straub
--- End Message ---
--- Begin Message ---
Source: spamass-milter
Source-Version: 0.3.1-2
We believe that the bug you reported is fixed in the latest version of
spamass-milter, which is due to be installed in the Debian FTP archive:
spamass-milter_0.3.1-2.diff.gz
to pool/main/s/spamass-milter/spamass-milter_0.3.1-2.diff.gz
spamass-milter_0.3.1-2.dsc
to pool/main/s/spamass-milter/spamass-milter_0.3.1-2.dsc
spamass-milter_0.3.1-2_i386.deb
to pool/main/s/spamass-milter/spamass-milter_0.3.1-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Don Armstrong <[EMAIL PROTECTED]> (supplier of updated spamass-milter package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 5 Apr 2006 13:21:11 -0700
Source: spamass-milter
Binary: spamass-milter
Architecture: source i386
Version: 0.3.1-2
Distribution: unstable
Urgency: low
Maintainer: Don Armstrong <[EMAIL PROTECTED]>
Changed-By: Don Armstrong <[EMAIL PROTECTED]>
Description:
spamass-milter - milter for filtering mail through spamassassin
Closes: 373812 378460
Changes:
spamass-milter (0.3.1-2) unstable; urgency=low
.
* Create /var/run/sendmail if it doesn't already exist to allow for
/var/run on a tmpfs (closes: #373812)
* Stop depending on sendmail, and begin recommending sendmail or postfix
(closes: #378460)
Files:
69b47d3fb29b8bfa6072cc67c7f34bb7 610 mail extra spamass-milter_0.3.1-2.dsc
f3b43444bb8963ef49770ba8f60108b9 26260 mail extra
spamass-milter_0.3.1-2.diff.gz
e64172febdc4ef68091e55e40c2c4ce2 46080 mail extra
spamass-milter_0.3.1-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFB7Y8gcCJIoCND9ARAqgyAJ9VO+r73uHPqTzaqpb3IC3Xsvk54QCgl4lJ
QL+b4iNsNgUbve5Jn0/N0QU=
=W9Of
-----END PGP SIGNATURE-----
--- End Message ---
