Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.mail.pine
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
MIME
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ivan Shmakov  
View profile  
 More options May 11 2012, 2:20 am
Newsgroups: news.misc, comp.mail.pine, comp.unix.programmer
Followup-To: news.misc, comp.mail.pine
From: Ivan Shmakov <oneing...@gmail.com>
Date: Fri, 11 May 2012 13:20:13 +0700
Local: Fri, May 11 2012 2:20 am
Subject: Re: MIME
Print | Individual message | Show original | Report this message | Find messages by this author

>>>>> 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-838b-fab08420edba@w9g2000pbm.googlegroups.com --
On May 8, 3:10\240pm, Ian Collins <ian-n...@hotmail.com> wrote:
--cut: news:eacc1bb1-6ba5-4ef0-838b-fab08420edba@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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google