Daryl C. W. O'Shea wrote: > Are you still having this issue? > yes indeed > > Wow. That's an incredibly bad idea. Allowing sa-update to install > Perl, or other, code (--allowplugins) without verifying that the code is > signed (--nogpg) is pretty risky. If a mirror gets hacked you'll run > (possibly as root) whatever code the attacker wants you to. > I used pgp keys originally, then it broke and I was unable to get it to work without --nopgp so I left it that way. I'll give some effort to getting it to work again.
> >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin46123uY1E3Ntmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_AOPDF Content-Type =~ /^application\/octet-stream.*\.pdf/i >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin46123uY1E3Ntmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_AP Content-Type =~ /^application\/pdf/i >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin46123uY1E3Ntmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_TP Content-Type =~ /^text\/plain/i >> channel: lint check of update failed, channel failed >> > > On the surface this indicates an issue with the MIMEEval plugin. > However, it appears that you're loading that plugin (see below). Maybe > verify that your version of MIMEEval is OK. > > [...@cyan Plugin]$ sha1sum MIMEEval.pm > ec62013c06d3a51d972cd02d51169221be6d51c2 MIMEEval.pm > [...@cyan Plugin]$ > $ sha1 /usr/local/lib/perl5/site_perl/5.8.9/Mail/SpamAssassin/Plugin/MIMEEval.pm SHA1 (/usr/local/lib/perl5/site_perl/5.8.9/Mail/SpamAssassin/Plugin/MIMEEval.pm) = ec62013c06d3a51d972cd02d51169221be6d51c2 matches yours. > >> Feb 26 04:15:02.614 [14130] dbg: generic: lint check of site pre files >> succeeded, continuing with channel updates >> > > That's good. A lint succeeds using minimal configuration. > > >> Feb 26 04:15:06.323 [14130] dbg: plugin: loading >> Mail::SpamAssassin::Plugin::MIMEEval from @INC >> > The MIMEEval plugin seems to be loading. > > >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin14130V3YzQDtmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_AOPDF Content-Type =~ /^application\/octet-stream.*\.pdf/i >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin14130V3YzQDtmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_AP Content-Type =~ /^application\/pdf/i >> config: failed to parse line, skipping, in >> "/tmp/.spamassassin14130V3YzQDtmp/72_active.cf": mimeheader >> __TVD_MIME_ATT_TP Content-Type =~ /^text\/plain/i >> > > These are all MIMEEval rules. I've checked and they are all wrapped in > the appropriate ifplugin statements. > > Question. How does one check if the tmp files are deleted at the end? Which ifplugin is is wrapped in? >> Feb 26 04:15:07.438 [14130] dbg: zoom: loading compiled ruleset from >> /var/db/spamassassin/compiled/5.008/3.003000 >> Feb 26 04:15:07.447 [14130] dbg: zoom: using compiled ruleset in >> /var/db/spamassassin/compiled/5.008/3.003000/Mail/SpamAssassin/CompiledRegexps/body_0.pm >> for Mail::SpamAssassin::CompiledRegexps::body_0 >> > > Hmm. This is probably a flaw in sa-update, but probably doesn't affect > your issue. For fun, try rm'ing /var/db/spamassassin/compiled/ and run > sa-update again. > > Tied that Daryl and still no good, same error Thanks for lending a hand. -lee
