> -----Original Message-----
> From: Louis LeBlanc
> I'm afraid I don't have a test server - all my work is
> production environment development, which keeps life
> interesting, and makes me very careful about any changes.
It appears that even though spamc aborts the attempted spamd connection
after 3 retries, it will not produce a non-zero exit code. Is it my recipe
or spamc?
Here is the recipe I tested:
# I set SAONOFF to be able to turn the test on or off
:0 w
* SAONOFF ?? on
{
:0
* ! ^X-Spam-Status: Yes
{
:0fw: spamassassin.lock
* < 256000
| spamc
SCANNED=$?
:0 Afw: spamassassin.lock
* ! SCANNED ?? ^^0^^
| spamassassin -a
}
}
:0 w
* ^X-Spam-Status: Yes
{
stuff
}
Before stopping spamd:
procmail: Match on "on"
procmail: Match on ! "^X-Spam-Status: Yes"
procmail: Match on "< 256000"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamc"
procmail: [12341] Wed Sep 3 22:05:34 2003
procmail: Unlocking "spamassassin.lock"
procmail: Assigning "SCANNED=0"
procmail: No match on ! "^^0^^"
procmail: Match on "^X-Spam-Status: Yes"
After stopping spamd:
maillog indicates aborted spamc connection attempt after 3 retries
procmail: Match on "on"
procmail: Match on ! "^X-Spam-Status: Yes"
procmail: Match on "< 256000"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamc"
procmail: [12412] Wed Sep 3 22:08:42 2003
procmail: Unlocking "spamassassin.lock"
procmail: Assigning "SCANNED=0"
procmail: No match on ! "^^0^^"
procmail: No match on "^X-Spam-Status: Yes"
New test:
:0 w
* SAONOFF ?? on
{
:0
* ! ^X-Spam-Status: Yes
{
:0fw: spamassassin.lock
* < 256000
| spamc
:0 efw: spamassassin.lock
| spamassassin -a
}
}
:0 w
* ^X-Spam-Status: Yes
{
stuff
}
spamd still stopped:
maillog indicates aborted spamc connection attempt after 3 retries
procmail: Match on "on"
procmail: Match on ! "^X-Spam-Status: Yes"
procmail: Match on "< 256000"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamc"
procmail: [12487] Wed Sep 3 22:24:49 2003
procmail: Unlocking "spamassassin.lock"
procmail: No match on "^X-Spam-Status: Yes"
So I decided to change my logic:
:0 w
* SAONOFF ?? on
{
:0
* < 256000
{
:0fw: spamassassin.lock
* ! ^X-Spam-Status: Yes
| spamc
# Status could be no so don't test for yes/no
:0fw: spamassassin.lock
* ! ^X-Spam-Status:
| spamassassin -a
}
}
:0 w
* ^X-Spam-Status: Yes
{
stuff
}
spamd still stopped:
maillog indicates aborted spamc connection attempt after 3 retries
procmail: Match on "on"
procmail: Match on "< 256000"
procmail: Match on ! "^X-Spam-Status: Yes"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamc"
procmail: [12728] Wed Sep 3 23:04:11 2003
procmail: Unlocking "spamassassin.lock"
procmail: Match on ! "^X-Spam-Status:"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamassassin,-a"
procmail: [12728] Wed Sep 3 23:04:20 2003
procmail: Unlocking "spamassassin.lock"
procmail: Match on "^X-Spam-Status: Yes"
Thoughts?
Regards,
Larry
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
