Just to follow up: turns out that the final problem was the known
flakiness in my cyrus onstall. Upgraded to 2.0.16 (via RPM, so it also
re-ran the setup scripts to set chattr on the files) and _everything_
seems to be running better now.
I've left the change for the end-of-headers line
Justin,
That was my thought too, but they don't showup in vim and usually
they do. Also, deleting the header-seperating line and recreating it
doesn't fix it, and make the thing search for "^[:cntrl:]*$" doesn't fix
it, and _that_ should do it.
Or atleast, that's what the manual says
Donald Greer said:
>Ok, this is just plain wierd!
>When I run a test message through spamc on 2.0, I get the above at
> the beginning of each body line and the X-Spam-Status at the bottom
> (which sorta answers my other question).
I reckon you've got ^Ms in that message. that would c
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 se
On Wed, 23 Jan 2002, Donald Greer wrote:
> Charlie Watts wrote:
> > I've never used courier.
>
> Me neither :^). I use Posfix & Cyrus.
LOL ... yeah, yeah. I'm having a braino sorta day. Getting over a 103
degree fever. Influenza is no fun. LOL.
> > I'm still surprised that you had to make th
Charlie Watts wrote:
[...]
>
> I've never used courier.
Me neither :^). I use Posfix & Cyrus.
>
> I'm still surprised that you had to make that change to begin with.
>
> Is this your mail flow?
>
> mta (which?) -> procmail -> cyrus "deliver"
Postfix->procmail->cyrus "deliver"
>
>
On Wed, 23 Jan 2002, Charlie Watts wrote:
> I've never used courier.
Oops, I meant cyrus. I use courier-imap.
Duh.
--
Charlie Watts
[EMAIL PROTECTED]
Frontier Internet, Inc.
http://www.frontier.net/
___
Spamassassin-talk mailing list
[EMAIL PROTEC
(Cc'ing sapamassassin-talk back in ...)
On Wed, 23 Jan 2002, Donald Greer wrote:
>I've been doing some playing around with my procmail recipe and I
> find that spamc is returning the message, and everything is happy now
> (since the above workaround) but now deliver (the cyrus delivery
> pro
On Wed, 23 Jan 2002, Donald Greer wrote:
>Well, I found a work-around. I don't know that it's the best way to
> fix it, but...
>If anyone wants to tell me if this is not an acceptable solution
> (e.g. it'll reject valid headers or accept invalid headers) please let
> me know.
>Otherw
Well, I found a work-around. I don't know that it's the best way to
fix it, but...
If anyone wants to tell me if this is not an acceptable solution
(e.g. it'll reject valid headers or accept invalid headers) please let
me know.
Otherwise, it seams to work, so onward and upward!
Her
Ok,
I've been banging my head against this thing, and it looks like the
line 94 in NoMailAudit.pm is not doing it's job for some reason.
The line is as follows:
if (/^$/) { last; }
Well, that seams straight forward enough!
What's puzzling is that it works FINE on the samp
Nope. I had tried that before, but I tried it again with the same
result.
Here's what I've removed:
/usr/lib/perl5/siteperl/5.6.1/spamassassin.*
/usr/lib/perl5/siteperl/5.6.1/Mail/SpamAssassin*
/usr/share/spamassassin
/etc/spamassassin*
/etc/mail/spamassassin
/root/.spamassassin*
/usr/bin/
12 matches
Mail list logo
