Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: MIME
11 views
Skip to first unread message
Ivan Shmakov
May 11, 2012, 2:20:13 AM5/11/12
to
>>>>> Ersek, Laszlo <la...@caesar.elte.hu> writes:
>>>>> On Wed, 9 May 2012, Scott Lurndal wrote:
>>>>> "Ersek, Laszlo" <la...@caesar.elte.hu> writes:
[Cross-posting to news:news.misc and news:comp.mail.pine, and
setting Followup-To: there.]
>>> This message is in MIME format. The first part should be readable
>>> text, while the remaining parts are likely unreadable without
>>> MIME-aware tools.
>> Was mime necessary?
> Absolutely not. Apologies.
It's my opinion that MIME /should/ always be used (and if any
non-ASCII codes are used, then it definitely /must/ be used.)
There were no reason to use multipart/* there, though.
[...]
> I don't know why it didn't work. Sorry for the inconvenience.
> Perhaps postponing the message forced MIME?...
> I doubt I wrote anything outside of 7-bit ASCII to begin with.
> Nonetheless, alpine reports my posting back to me as "ISO-8859-15"
> which I never use deliberately. It may have been triggered by
> something in Joshua's mail that I replied to.
Indeed, there was a NO-BREAK SPACE, as denoted by \240 in the
following:
--cut: news:eacc1bb1-6ba5-4ef0...@w9g2000pbm.googlegroups.com --
On May 8, 3:10\240pm, Ian Collins <ian-n...@hotmail.com> wrote:
--cut: news:eacc1bb1-6ba5-4ef0...@w9g2000pbm.googlegroups.com --
> And then "news transport software" beyond my client could have forced
> MIME. (I hope it won't happen now!)
Your follow-ups to this thread were MIME-compliant (which is
good), though not multipart/* (which is also good.)
> The NNTP server I use is "news.eternal-september.org".
--
FSF associate member #7257
>>>>> On Wed, 9 May 2012, Scott Lurndal wrote:
>>>>> "Ersek, Laszlo" <la...@caesar.elte.hu> writes:
[Cross-posting to news:news.misc and news:comp.mail.pine, and
setting Followup-To: there.]
>>> This message is in MIME format. The first part should be readable
>>> text, while the remaining parts are likely unreadable without
>>> MIME-aware tools.
>> Was mime necessary?
> Absolutely not. Apologies.
It's my opinion that MIME /should/ always be used (and if any
non-ASCII codes are used, then it definitely /must/ be used.)
There were no reason to use multipart/* there, though.
[...]
> I don't know why it didn't work. Sorry for the inconvenience.
> Perhaps postponing the message forced MIME?...
> I doubt I wrote anything outside of 7-bit ASCII to begin with.
> Nonetheless, alpine reports my posting back to me as "ISO-8859-15"
> which I never use deliberately. It may have been triggered by
> something in Joshua's mail that I replied to.
Indeed, there was a NO-BREAK SPACE, as denoted by \240 in the
following:
--cut: news:eacc1bb1-6ba5-4ef0...@w9g2000pbm.googlegroups.com --
On May 8, 3:10\240pm, Ian Collins <ian-n...@hotmail.com> wrote:
--cut: news:eacc1bb1-6ba5-4ef0...@w9g2000pbm.googlegroups.com --
> And then "news transport software" beyond my client could have forced
> MIME. (I hope it won't happen now!)
Your follow-ups to this thread were MIME-compliant (which is
good), though not multipart/* (which is also good.)
> The NNTP server I use is "news.eternal-september.org".
--
FSF associate member #7257
0 new messages