Oh, grow the heck up. Get used to the fact that your little closed world of 10+ years ago is gone.
And here is an except from your precious ARPANET RFCs: This RFC suggests a *proposed* protocol - Note it does not say *required* protocol.
Read the rest here, or do you also reject RFCs?:
ftp://ftp.rfc-editor.org/in-notes/rfc951.txt
Get a clue - the world has moved on and you have been left behind.
Oh, and automatic transmission works a treat! And so do microwaves. And I dare you to try HD TV, or maybe getting a color set would be a more gentle introduction to the modern world.
As for top posting, only those with short term memory loss bottom post - the rest of us remember what was posted and don't need to needlessly keep scrolling through the detritis of old conversations to remind us why we are reading the post in the first place.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact.
After furious head scratching, XS11E asked:
| "Milly Staples [MVP - Outlook]"
|
|| Sigh - where to begin. Inline works for me.
||
|| --
|
| And since you top posted the above, my newsreader tried to delete all
| below the sigdash as a good newsreader should. One more reason top
| posting is wrong.
|| After furious head scratching, XS11E asked:
||
||| "Milly Staples [MVP - Outlook]"
|||
|||| No, email should be what the user/recipients REQUIRE.
|||
||| STRONGLY DISAGREE!
|||
|||| Your opinion and mine make no difference to the people who have
|||| different requirements, such as sending contacts, etc. which
|||| require Rich Text in Outlook.
|||
||| It's not a matter of opinion, it's a matter of etiquette, the
||| rules have been established over a very long period of time.
||
|| Show me!
|
| Google will do that, start here:
|
|
http://www.iwillfollow.com/email.htm
|
| Scroll down to the formatting section.
|
|
||
|||
||| Sending contacts, pictures, etc are why there are attachments.
|||
||
|| Wrong, contacts, appointments, etc. require RTF for sending unless
|| you want garbage characters and no form.
|
| Wrong, attachments work just fine.
|
|||| Likewise, using a company stationery (a major business
|||| requirement)
|||
||| Not a requirement except in someone's over active imagination.
||
|| Tell it to the CEO who insists on branding and logos.
|
| The world is full of people who don't know better, they should be
| shown the right way to do things.
|
|||| IOW, different strokes for different folks.
|||
||| Wrong. Again, that's why there are established rules of
||| etiquette.
||
|| Again, show me. Every RFC I have ever read has been prefaced with
|| a recommendation, never a requirement.
||
|| The ball is in your court.
|
| Again, Google will show you.
|
| For those of use who began with ARPNET, rules of etiquette are long
| established because they work. You might refer to other posts in this
| discussion for additional reasons to follow the rules of etiquette,
| they don't expire, they don't grow outdated. You still shouldn't chew
| with your mouth open, interrupt others conversations, top post or use
| HTML in email or newsgroups.
|
| Because MSFT has chosen to completely ignore GNSKA in it's newsreaders
| or Outlook encourages this discourtesy to others is no reason we have
| compound the discourtesy.