Re: +net help line.




"pmj" <post@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:fRa%f.52158$wl.1920@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Your eMail Client *should* have not shown you the MIME Headers,
but should have Interpreted it all, showing you the Contents
of each "MIME Part"according to what's specified *by* those Headers...

Well it wasn't just the bit I quoted, the whole e-mail was like that -
gobbledegook


I dunno why they are using "Base64" Content-Transfer-Encoding
for a MIME Part that has a "Content-Type" of "text/plain" though!!!
That seems a bit weird, but it's perfectly possible.

Anyway, the way the MIME Headers get Interpreted by the Mail Client,
but *only* if they are Syntactically Correct & properly Formatted.

*Leading* Spaces at the beginning of Lines make a big difference.
If there is no Leading Space, then the Line will be counted as another
Header, but if there *is* a leading Space, it will be counted as a
"Continuation" of the previous Header Line.

If you Copy & Paste what's below, which I have Copied from what you
Posted, (inbetween, but not including) the <quote></quote> Lines,
into a *Text* File & then Save/ReName it as an .eml File, it will
actually then Open up OK as an eMail in OutLook Express - notice the
Leading Space(s) at the beginning of the "boundary=" Lines, which
seem to be missing from what you Posted

Yes, well I didn't post the whole lot cos it went on quite a bit

I just doing that & from that we can see that all that "dXNlcm5h..."
etc, stuff actually Translates (when *Un*Base64 Encoded<g>) into...

<quote>
username: theholt


PlusNet is evolving - in an evolving
</quote>

The EMail Client does the Base64 handling stuff Automagically,
by itself, provided the MIME Headers are correct.

Well it didn't, so I guess they weren't

Did you look at the eMail using the "View Message Source" Window?
or by Opening it up in the Preview Pane (or normal Message Viewing
Window)?

I double clicked on the message to open it and also looked at it in
message source - just the same

Doesn't look as if I missed much though

--
Barb








.



Relevant Pages

  • Re: Displaying from email address?
    ... > The best you can do is Ctrl+F3 to see the Message Source. ... only by closing the window (e.g. by pressing Alt-F4 and NOT by Esc) ... Source window which used to bite me too often but still might be seen ... Message Source window was showing pressing Alt-F4 initiated a shutdown ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: OETool--starting in W98
    ... Sometimes when I click on the message source button, ... window opens and an OE Tool message window that says OE Tool. ... > Once you run OETool, it sits in the system tray, where you can right click ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Norton Internet Security adds spam warning info to the subject line
    ... them to the same Notepad window without closing the Notepad window. ... displaying its Message Source for in the first place. ... thinking I'm closing Message Source that I will lose the parent window ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: +net help line.
    ... Just had an email from Plusnet entitled 'Plusnet is evolving'. ... Your eMail Client *should* have not shown you the MIME Headers, ... Anyway, the way the MIME Headers get Interpreted by the Mail Client, ...
    (uk.people.silversurfers)
  • Re: combine & decode multipart message
    ... When sending from OE to OE the receiving OE should automatically put all ... corrupted the MIME headers. ... Look at the Message Source (Ctrl-F3) for each of the message parts. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)