https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6127
--- Comment #8 from Joel <[email protected]> 2009-06-09 19:02:35 PST --- (In reply to comment #7) > Maybe a qmail scanner issue, but definitely an issue with your SA > installations. Setting Version back to 3.1.8, according to comment 5 the code > in question obviously is not 3.2. Yes, after some poking around this is a qmail-scanner issue. The script attempts to record the version numbers in a file but this file never gets updated and hasn't been updated since the original installation nearly two years ago. I've been modifying the permissions to no avail. -> #X-Spam-Checker-Version: SpamAssassin 2.01 open(SPAS,"$spamassassin_binary -V |")||die "failed to call $spamassassin_binary -V - $\ !"; $spamassassin_eng="2.x"; while (<SPAS>) { chomp; if (/^SpamAssassin version (.*)$/i) { $spamassassin_eng=$1; } } close(SPAS); $SCANINFO .= "spamassassin: $spamassassin_eng. "; } else { #Catch-all for other ones $SCANINFO .= "$scanner: ???. "; } } $SCANINFO =~ s/ \. / /g; open(VER,">$versionfile.tmp")||die "cannot write to $versionfile.tmp - $!"; print VER $SCANINFO; close(VER); rename("$versionfile.tmp","$versionfile"); --> I verified that there is but one spamassassin executable on the system and that it is version 3.2.5. In fact, there is only one copy of every process involved. > Regarding comment 0, was that pid 1214 actually a spamd child process? Just > making sure, cause you didn't paste anything logged from the child. The pid 1214 belongs to spamd as revealed by it's uid which is 58 on my system. > Anyway, that's a segmentation fault. I believe that would be a Perl issue, > wouldn't it? Yes, it is obviously a segmentation fault that occurs in Perl. But your whole gig is written in perl and depends intimately on perl. So I believe it would be hard to wash your hands of the issue. Bug 6060 seems to make this clear. Finding the errant piece of code is my problem. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
