I reported this issue about a month ago and didn't receive a response. So I set about fixing it myself.
First, I edited the sa-update script to not delete the rules that it downloaded and was running lint on... I looked at those rules to see if I could spot the problem, but I couldn't... looked for control chars, ^M's, nothing... So I removed the lint check from sa-update and that allowed it to install the rules. The I ran sa-update again and a new ruleset was downloaded... and this one passed the lint check... I have no idea what was wrong with that original set but it prevented sa-update from continuing and it appears to me that sa-update seems to just "get the next released rules" rather than "get the last released rules" and that held up downing a good set to replace the bad set... I dunno if that's the case but it matches my observations. your mileage may vary... I've had no problem since and the original sa-update has been used since my one time hack. -lee Personal Técnico wrote: > Hi, > > I'm getting this error when I run sa-update: > > config: failed to parse line, skipping, in > "/tmp/.spamassassin26787Cjo628tmp/72_active.cf": mimeheader > __TVD_MIME_ATT_AOPDF Content-Type =~ > /^application\/octet-stream.*\.pdf/i > config: failed to parse line, skipping, in > "/tmp/.spamassassin26787Cjo628tmp/72_active.cf": mimeheader > __TVD_MIME_ATT_AP Content-Type =~ /^application\/pdf/i > config: failed to parse line, skipping, in > "/tmp/.spamassassin26787Cjo628tmp/72_active.cf": mimeheader > __TVD_MIME_ATT_TP Content-Type =~ /^text\/plain/i > channel: lint check of update failed, channel failed > > > > Spamassassin installed version is 3.3.1-1 in a Debian Lenny 64 bits > system. > > Why am I getting this error? > > Thanks.
