I have several rules relating to MIME headers but after the latest
spamassassin update yesterday two of them have failed to parse. The
rules are:
mimeheader PFSA_CONTENT_TYPE Content-Type =~
/[0-9]{8,}\.xls|.*\.js|\.cab|image/png:\sname.*\.zip/i
mimeheader PFSA_MACROENABLED Content-Type =~
/^application/msword$|macroEnabled/i
Running lint gives the following:
Jan 14 10:32:40.345 [52189] warn: config: SpamAssassin failed to parse
line, "PFSA_CONTENT_TYPE Content-Type =~
/[0-9]{8,}\.xls|.*\.js|\.cab|image/png: name.*\.zip/i" is not valid for
"mimeheader", skipping: mimeheader PFSA_CONTENT_TYPE Content-Type =~
/[0-9]{8,}\.xls|.*\.js|\.cab|image/png: name.*\.zip/i
Jan 14 10:32:40.348 [52189] warn: config: SpamAssassin failed to parse
line, "PFSA_MACROENABLED Content-Type =~
/^application/msword$|macroEnabled/i" is not valid for "mimeheader",
skipping: mimeheader PFSA_MACROENABLED Content-Type =~
/^application/msword$|macroEnabled/i
These two rules have been running for years. The point of them is that
they should DETECT invalid mimeheaders of just those constructs so I'm
not sure why the rules are invalid. Any ideas as to why they suddenly
fail, please?
