Is it worth opening a bug on making uuencoded messages work properly? Textcat apparently thought a message was Japanese instead of a uuencoded .csv file: [22957] dbg: message: ---- MIME PARSER START ---- [22957] dbg: message: parsing normal part [22957] dbg: message: ---- MIME PARSER END ---- [22957] dbg: message: no encoding detected [22957] dbg: textcat: classifying, skipping: yi sco lv is bs sl la ga sa eu et rm cy eo fy gd lt [22957] dbg: textcat: language possibly: ja.iso-2022-jp [22957] dbg: textcat: X-Languages: "ja.iso-2022-jp", X-Languages-Length: 6318
The body is encoded with classic uuencoding, no MIME type: begin 644 recalls_email.03.30.csv M"DU%5$527TE$(" @(" @(" @(" @+$5.5%)97T1!5"Q23U5412 @(" @(" L M551)3$E465])1" @(" @(" @(" @(" @("Q!1$1215-3(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @(" @+$-)5...@4u0@6DE0(" @(" @(" @(" @ I dug through bugzilla, and found four or five WON'T FIX bugs opened about similar issues in the past.[1] -- Daniel J McDonald, CCIE #2495, CISSP #78281, CNX Austin Energy http://www.austinenergy.com [1]: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1123 https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1409 https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3278 https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1564
signature.asc
Description: This is a digitally signed message part