http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5106
--- Additional Comments From [EMAIL PROTECTED] 2006-09-25 03:53 ---
Sounds right to me. -x disables spamc covering your ass. Try host1, if the
exit code indicates that host1 didn't scan it try host2 yourself. For the next
m
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5106
Summary: multiple hosts with -d switch doesn't work when -x is
also used
Product: Spamassassin
Version: unspecified
Platform: Other
OS/Version: other
Status
*** ASF Nagios ***
Notification Type: RECOVERY
Host: spamassassin.zones.apache.org
Address: 207.7.158.200
State: UP
Info: $
Date/Time: Mon Sept 25 04:17:53 BST 2006
*** ASF Nagios ***
Notification Type: PROBLEM
Host: spamassassin.zones.apache.org
Address: 207.7.158.200
State: UNREACHABLE
Info: $
Date/Time: Mon Sept 25 04:14:31 BST 2006
*** ASF Nagios ***
Notification Type: PROBLEM
Host: spamassassin.zones.apache.org
Address: 207.7.158.200
State: UNREACHABLE
Info: $
Date/Time: Mon Sept 25 03:16:00 BST 2006
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've resorted to manually step-by-stepping thru SA (trunk, r449343)
code, tracing the cause of a 100% reproducible perl588 crash on, simply:
spamd --daemonize
i've, apparently, been unable to grok perl_debugger well enough to keep
following
*** ASF Nagios ***
Notification Type: RECOVERY
Host: spamassassin.zones.apache.org
Address: 207.7.158.200
State: UP
Info: $
Date/Time: Mon Sept 25 03:22:33 BST 2006
Bugzillia seems to be broken tonight.
The specs say that if you use spamc with multiple hosts then if the
first host fails it will try the other hosts. It does do this. But if
you user the -x switch then it only tries the first host.
spamc -d host1,host2 - works
spamc -x -d host1,host2
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5044
--- Additional Comments From [EMAIL PROTECTED] 2006-09-24 07:32 ---
Would we be open to a "--lint-with-local-config" option?
I'm still confused as to why we would ever want to install an update that isn't
going to later lint
