<html><head></head><body>Hi Bob thanks for the links. To tell you the truth if there wasn't such a catterwallin on the list the first time some dross showed up in one of my posts, I wouldn't care. I can live with a little dross myself.<br>
<br>
I note that RFC stands for request for comments.<br>
<br>
If I hadn't noticed that it appeared that charactars were being appended on send before being handled by the mail list software I might agree wholeheartedly that the list is at fault. Having made that comment, I'll also say this, if a linux hacker can't post to a hobbyist lug about making his linux device send plain text then where should they go.<br>
<br>
It's not like there's a huge enterprise relying on absolute accuracy here. If there is such a thing as absolutly uniform behaviour in cross platform applications, I hardly ever see much of that.<br>
<br>
As for taking this discussion offline, I could see that, if the list managers decide android is in fact not a linux. If it is, then we all know how to deal with list chatter we have no interest in.<br>
<br>
Respectfully,<br>
Ross<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br><div class="gmail_quote">Bob Jonkman <bjonkman-w5ExpX8uLjYAvxtiuMwx3w@public.gmane.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif">On 11-11-20 08:55 PM, waltdnes-SLHPyeZ9y/tg9hUCZPvPmw@public.gmane.org wrote:<br />> No trailing garbage at all. FYI, here's the raw message, with leading<br />> space inserted to avoid screwing up simple MUA's...<br />><br />><hr /><br />> Date: Sun, 20 Nov 2011 13:54:54 -0500<br />> Subject: [TLUG]: Sharing a news story<br />> Message-ID:<edyds3onm8mm7ul27t4a8jvb.1321815294844-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org><br />> From: Russ<rreiter91-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org><br />> To: "tlug-lxSQFCZeNF4@public.gmane.org"<tlug@ss.org><br />> Content-Type: text/plain; charset=utf-8<br />> Content-Transfer-Encoding: base64<br />> Sender: owner-tlug-BEuBXOPWo2E@public.gmane.orgg<br />> Precedence: list<br />> Reply-To: tlug-lxSQFCZeNF4@public.gmane.org<br />> X-Whitelist: Whitelisted (sender *@ss.org)<br />><br />> SGVyZSBpcyB0b2RheXMgaG9yb3Njb3BlLiBBbnkgdHJhaWxpbmcgbm9pc2U/CgpodHRwOi8vbW9i<br />>
aWxlLnRoZXN0YXIuY29tL21vYmlsZS9ob3Jvc2NvcGVzL2FydGljbGUvMTA3Nzk1NQ==<br />><br />> --<br />> The Toronto Linux Users Group. Meetings: <a href="http://gtalug.org">http://gtalug.org</a>/<br />> TLUG requests: Linux topics, No HTML, wrap text below 80 columns<br />> How to UNSUBSCRIBE: <a href="http://gtalug.org/wiki/Mailing_lists">http://gtalug.org/wiki/Mailing_lists</a><br />><hr /><br /><br />It's a wonderful illustration of the problem: The headers declare that <br />the text is Content-Transfer-Encoded with Base64 (a perfectly valid <br />encoding for e-mail), but the contents of the message body includes the <br />TLUG footer which is not encoded with Base64, thus corrupting the <br />contents of the message body.<br /><br />The problem is not the MUA that Ross is using, but the behaviour of the <br />mailing list software. If it is going to add a footer, it should first <br />decode the Base64 message body, add the footer, and then (optionally)
<br />re-encode to Base64. Or the mailing list software could re-transmit the <br />message with Content-Type set to Multi-part/mixed, with the message body <br />in one part and the TLUG footer in another part.<br /><br />It is a different problem than trying to get a particular MUA to send <br />with a particular Content-Transfer-Encoding, which seems to be what Ross <br />et al. are trying to do. Even if you find a way to suppress Base64 <br />Content-Transfer-Encoding on your MUA it does not solve the problem of <br />the mailing list software corrupting messages. Perhaps this MUA testing <br />could be taken off-line.<br /><br />--Bob.<br /><br />MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for <br />Specifying and Describing the Format of Internet Message Bodies <br /><a href="https://tools.ietf.org/html/rfc1521">https://tools.ietf.org/html/rfc1521</a><br /><br />The Base16, Base32, and Base64 Data Encodings <a
href="https://tools.ietf.org/html/rfc4648">https://tools.ietf.org/html/rfc4648</a><br /><br />--<br />The Toronto Linux Users Group. Meetings: <a href="http://gtalug.org">http://gtalug.org</a>/<br />TLUG requests: Linux topics, No HTML, wrap text below 80 columns<br />How to UNSUBSCRIBE: <a href="http://gtalug.org/wiki/Mailing_lists">http://gtalug.org/wiki/Mailing_lists</a><br /></pre></blockquote></div></body></html>