Bug 187034

Summary: spamd doesn't start when network is down
Product: [Fedora] Fedora Reporter: David Baron <dbaron>
Component: spamassassinAssignee: Warren Togami <wtogami>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: felicity, jm, parkerm, perl-devel, reg+redhat, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-28 14:52:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Baron 2006-03-28 07:15:00 UTC 
Description of problem:  spamd doesn't start up if the network is down.

Version-Release number of selected component (if applicable):
spamassassin-3.1.0-5.fc5.2

How reproducible:
Always

Steps to Reproduce:
1. /sbin/service NetworkManager stop, /sbin/ifdown eth0, or whatever turns off
your network connectivity
2. /sbin/service spamassasin start (or restart, if it's already running)
  
Actual results:
Starting spamd:                                            [FAILED]

Expected results:
Starting spamd:                                            [  OK  ]

Additional info:

This worked fine in Fedora Core 4.

This makes it very painful to use spamd on a laptop that uses NetworkManager and
fetchmail.  After a reboot, all the spam gets through, so I had to switch back
to spamassassin, which is much slower and uses tons of CPU.

I imagine it could also be a problem on servers that reboot if the network is
down transiently (e.g., coming back after a power outage, network equipment not
fully back yet).
Comment 1 Warren Togami 2006-03-28 14:52:55 UTC 
Hmm, I agree this is a problem, however please file this in upstream
Spamassassin Bugzilla.  When it is fixed upstream we will incorporate it into
Fedora.
Comment 2 David Baron 2006-04-02 18:16:32 UTC 
Appears to be fixed in spamassassin-3.1.1-1.fc5 , actually.