On Mon, 2 Dec 2002, Justin Mason wrote:
>
> Mark R. Cervarich said:
> > On Mon, 2 Dec 2002, Duncan Findlay wrote:
> >
> > > On Mon, Dec 02, 2002 at 11:46:26AM -0800, Ryan Clark wrote:
> > > > Security Violations
> > > > =-=-=-=-=-=-=-=-=-=
> > > > Nov 28 05:44:11 example_server spamd[7474]: bad
Mark R. Cervarich said:
> > are you guys using Razor 2.21 or 2.22? I think that was outputting
> > some noise on STDOUT which could be breaking spamc.
>
> I just upgraded to 2.22 and now it works great!!!
> (I'm not sure which version I was running before)
OK, that's it then -- anyone else seei
Mark R. Cervarich said:
> On Mon, 2 Dec 2002, Duncan Findlay wrote:
>
> > On Mon, Dec 02, 2002 at 11:46:26AM -0800, Ryan Clark wrote:
> > > Security Violations
> > > =-=-=-=-=-=-=-=-=-=
> > > Nov 28 05:44:11 example_server spamd[7474]: bad protocol: header
> > > error: (Content-length mismatch: 1
Steve, the point you are missing is that my spamassassin "gives up"
before it even scores it because of the Content Length Mismatch:
Dec 2 14:02:03 ns spamd[10870]: connection from localhost [127.0.0.1] at port9497
Dec 2 14:02:03 ns spamd[10930]: info: setuid to xxx succeeded
Dec 2 14:02:03 ns
| http://mark.cervarich.com/gb2312.spam.txt
| contains 3 sample spams that get by spamassassin every time.
I got scores of 10.7, 9.7 and 9.8 respectively for those three messages
using 2.43.
| Although I'd love it if someone told me how to stop this kind of spam
| using spamassassin.
All three
On Mon, 2 Dec 2002, Duncan Findlay wrote:
> On Mon, Dec 02, 2002 at 11:46:26AM -0800, Ryan Clark wrote:
> > Security Violations
> > =-=-=-=-=-=-=-=-=-=
> > Nov 28 05:44:11 example_server spamd[7474]: bad protocol: header
> > error: (Content-length mismatch: 1255 vs. 1241)
>
> That's an error th
On Mon, Dec 02, 2002 at 11:46:26AM -0800, Ryan Clark wrote:
> Security Violations
> =-=-=-=-=-=-=-=-=-=
> Nov 28 05:44:11 example_server spamd[7474]: bad protocol: header
> error: (Content-length mismatch: 1255 vs. 1241)
That's an error that shouldn't be happening; something must be wrong
with y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
Here's a tid bit of info for a problem I encountered when I 1st setup
Spamassassin that was breaking it.
What was happening from the content length mismatch no email was
being checked properly against spamd. Instead of performing a check
agains
