Your message dated Thu, 30 Aug 2012 15:57:22 +0200
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #679491,
regarding [fetchmail] Spamassassin-Fetchmail depedenty boot order needs fixing
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.)
--
679491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679491
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fetchmail
Version: 6.3.21-4
Severity: normal
--- Please enter the report below this line. ---
I am including verbatum a posting and answer about this problem:
> The new sysv-rc assined K01 symlinks to fetchmail.
>
> However, I want to have spamassassin and its rules up beforehand. I have
been
> doing this explicitly in what is now rc.local. Fetchmail did not like the
> duplicated start and my mail wored only after I restarted fetcmail.
>
> There must be a more correct way to do this.
>
> ( Meanwhile, I removed the symlinks to allow my rc.local to start fetchmail.
> The next upgrades will restore them unless I divert. The sysv-rc gave K03
> symlinks to spamassassin which would mean starting after fetchmail and there
> is not menion of the rules. )
Looking at the fetchmail init script:
### BEGIN INIT INFO
# Provides: fetchmail
# Required-Start: $network $local_fs $remote_fs $syslog
# Required-Stop: $remote_fs
# Should-Start: $mail-transport-agent exim4 $named
# Should-Stop: $mail-transport-agent exim4
# Default-Start: 2 3 4 5
# Default-Stop:
# Short-Description: init-Script for system wide fetchmail daemon
### END INIT INFO
and spamassassin:
### BEGIN INIT INFO
# Provides: spamassassin
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Should-Start: $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
### END INIT INFO
So you just need to have
Should-Start: spamassassin
in the fetchmail script. And/or
X-Start-Before: fetchmail
in the spamassassin script. Then re-run insserv.
I would suggest filing a bug against the fetchmail package asking them
to do the former.
While the dependency info was missing in this case, this is actually
the nice thing about the dependency based boot. The fetchmail-
spamassassin dependency is implicit with sequence numbers, and not
immediately obvious. As above, it's explicit and obvious with the
dependencies--it just needs adding!
--- System information. ---
Architecture: i386
Kernel: Linux 3.2.0-3-686-pae
Debian Release: wheezy/sid
500 unstable ftp.us.debian.org
500 testing ftp.us.debian.org
100 experimental-snapshots qt-kde.debian.net
1 experimental ftp.us.debian.org
--- Package information. ---
Depends (Version) | Installed
====================================-+-================
libc6 (>= 2.11) | 2.13-33
libcomerr2 (>= 1.01) | 1.42.4-3
libgssapi-krb5-2 (>= 1.10+dfsg~) | 1.10.1+dfsg-1
libkrb5-3 (>= 1.6.dfsg.2) | 1.10.1+dfsg-1
libssl1.0.0 (>= 1.0.0) | 1.0.1c-3
debianutils (>= 1.7) | 4.3.1
adduser (>= 3.34) | 3.113+nmu3
lsb-base (>= 3.2-13) | 4.1+Debian7
Recommends (Version) | Installed
==============================-+-===========
ca-certificates | 20120623
Suggests (Version) | Installed
===================================-+-===========
fetchmailconf | 6.3.21-4
default-mta |
OR mail-transport-agent |
resolvconf |
--- End Message ---
--- Begin Message ---
Closing this bug report. Imho this report is bogus and there has been no
further activity.
--
Nico Golde - http://www.ngolde.de - [email protected] - GPG: 0xA0A0AAAA
pgpHZdaQpe8dA.pgp
Description: PGP signature
--- End Message ---
