My post to this list: Date: Tue, 8 Jul 2014 22:11:51 +1000 Subject: Re: Android/PC editing Message-ID: <20140708121151.GA1928@ratatosk>
came back from the listserver as: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 <=== !!!! **** Sender: [email protected] But my local copy of what went out confirms that it was: Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit and sure enough, the body is plain text, rather than the ghastly base64 lump which came back from the list. Given that internode flagged the list echo as: X-SpamDetect: : -7.000000 IronPort SPAM scanned=-10.0, Whole message is base64 encoded=1.0, Message text disguised using base-64 encoding=2.0 it seems reasonable to infer that the luv-main listserver did the munging. The message has only been seen by internode servers and tainted.luv.asn.au, according to the headers. The other posts on the thread have not been similarly abused, including my earlier post. It was only turned into: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit What can be happening? Did others receive it munged? (Or did their spam filters dump it?) Erik -- "You know, it's at times like this when I'm trapped in a Vogon airlock with a man from Betelgeuse and about to die of asphyxiation in deep space that I really wish I'd listened to what my mother told me when I was young!" "Why, what did she tell you?" "I don't know, I didn't listen!" - Douglas Adams, "Hitchhiker's Guide to the Galaxy" _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
