Charlie Watts wrote: [...]
> LOL ... yeah, yeah. I'm having a braino sorta day. Getting over a 103 > degree fever. Influenza is no fun. LOL. Bummer. Hope you're feeling better soon! [...] > Can you show your procmail recipes? Both the "pass-through" ones that work > and the ones that seem to be breaking at Cyrus? > > Lots of folks use SA w/ procmail ... I'm just trying to figure out what's > special about you. Here's what used to work: ========================================== :0fwr | /usr/bin/spamassassin -P :0 * ^(X-Spam-Flag):.*YES | $DELIVERTO user.dgreer_austintx_com.SPAM :0 | $DELIVERTO user.dgreer_austintx_com` ========================================== That doesn't work anymore, and neither does changing "...spamassassin -P" to "spamc". I've also cut-and-pasted the one in the docs and a few other things I found on the list just to test with. To test, I addedd: :0 ic /tmp/donsmail.log above the deliver calls to see what procmail was actually getting back from SA. That's when I found that header wierdness (see subject) and thought that was my problem. As I said, at this point, I think my problem is my flakey Cyrus installation. I think that, once I get a current backup of the mailboxes, I can simply do the upgrade (according to the cyrus docs there's nothing to convert from 2.0.12->2.0.16 ... hope they're right :^) and restart the service. If I'm lucky, the users won't even know. This is something I've been meaning to fix for months and now it's become a priority. -- -------------------------------------------------------- Donald L. Greer, Jr [EMAIL PROTECTED] System Administrator Voice: 512-300-0176 AustinTX http://www.AustinTX.COM/ All opinions are my own. Flame me directly. "I don't necessarily believe software should be free... but if you pay for it, it should work!" -- Me _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
