Hi Justin, Just a note to say I *think* your mods have worked... they're currently running on a backup SA server and appear to be behaving as expected.
I'm including the off list posts below so any others that hit this problem stand a chance of getting an answer. Again, many, many thanks for your time and patience. Apologies to all for top posting. Best to all Nigel >yep, unfortunately it'd take a manual build. if you're not comfortable >doing that already, it may not be a good idea to start now, it >can be a little tricky to get the hang of. :( >If you want to give it a try anyway, it goes like this: > > wget http://.../Mail-SpamAssassin-3.2.2.tar.gz > tar xvfz Mail-SpamAssassin-3.2.2.tar.gz > cd Mail-SpamAssassin-3.2.2 > [that patch command] > perl Makefile.PL PREFIX=/usr > make > sudo make install > >--j. > >Nigel Frankcom writes: >> Ahh - so I'm guessing I need to pull the tar.gz and run a manual >> build? My install came down from yum so AFAI can see there's no src >> dir (at least locate Mail-SpamAssassin-3.2.2 came back a blank). >> >> My sincere apologies for taking up your time like this. If you are >> aware of any reference material I can use I'm happy to do that rather >> than waste more of your time. >> >> Kind regards & many thanks for your patient help thus far. >> >> Nigel >> >> On Mon, 30 Jul 2007 16:23:04 +0100, [EMAIL PROTECTED] (Justin Mason) >> wrote: >> >> > >> >in the source directory ("Mail-SpamAssassin-3.2.2"), run >> > >> > patch -p0 < filename.patch >> > >> >Just apply the 2nd and 3rd attachment, not the 1st. >> > >> >--j. >> > >> >Nigel Frankcom writes: >> >> Please excuse an embarrassingly dumb question, but, how do I apply >> >> that patch? I've never applied one to anything before now. Also, do I >> >> need to install all 3? >> >> >> >> Red-faced >> >> >> >> Nigel >> >> >> >> On Mon, 30 Jul 2007 15:36:24 +0100, [EMAIL PROTECTED] (Justin Mason) >> >> wrote: >> >> >> >> > >> >> >could you try adding the 3.2.2 patch from >> >> >http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574 ? it could >> >> >be some buggy error-handling code is being triggered. >> >> > >> >> >--j. On Mon, 30 Jul 2007 15:36:24 +0100, [EMAIL PROTECTED] (Justin Mason) wrote: > >could you try adding the 3.2.2 patch from >http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574 ? it could >be some buggy error-handling code is being triggered. > >--j. > >Nigel Frankcom writes: >>I'm top posting this since bottom posting is pointless. As far as I >>can tell each mail is being dealt with twice. I'm really unsure what >>to do; whether my mailserver is the problem or SA. Or, more >>accurately, what change in the way SA handles headers has caused this >>problem to appear on my server now (I'm assuming it's idiosyncratic to >>my server since the list isn't deluged with HELP messages). >> >>I tried dropping back to 3.2.1 but couldn't find a port for it >>anywhere. I'll keep digging and see if I can find one since that >>didn't exhibit this issue with my server. >> >>Any help at all would be massively appreciated since I have a good few >>customers who are a tad concerned (not least of which being me). >> >>I did manage to pull a 3.1.9 version to test but that pretty much >>'blew up' and refused to accept any connections at all even though it >>--lint's clean. >> >>I really am at a loss and desperately in need of some advice. >> >>If you look at the stuff below this bit you'll see pretty clearly the >>problem I've got. If the dev's need to see raw messages (before SA >>gets them, let me know) >> >>TIA >> >>Nigel >> >> >>On Mon, 30 Jul 2007 11:56:53 +0100, Nigel Frankcom >><[EMAIL PROTECTED]> wrote: >> >>>Hi All, >>> >>>This morning I upgraded to 3.2.2 on CentOS 64 via yum. >>> >>>I'm now getting a copy of all email headers inside the body of the >>>email. >>> >>>Everything --lint's clean and apart from this it's working fine. As an >>>example I've copied in a list post below I received since the upgrade. >>> >>>Any help or workaround suggestions would be greatly appreciated. >>> >>>Kind regards >>> >>>Nigel. >>>
