Borking Outlook Express
Johannes writes: "Swedish Gnuheter has a story on Nick Moffitt arranging with his X-headers in way that makes it impossible to read his email with Microsoft WebTV or Outlook Express. Moffitt states: 'The folks using Outlook Express have locked themselves into a
limited subset of the information that can flow over the Internet, and
are blaming me personally for not limiting my transmissions to that
outlook-centric subset.'
See also original email (in English). Immoral? Or just right?" Looks like Moffit's "Who, me?" attitude is tongue in cheek, but the creative header changes here are hilarious.
From the site now:
/data/html/gnuheter/mainfile.php on line 17
/data/hacht-ema-el/gnuheter/mainafiler.peea-haich- a-pee on der lingna sevetoon. Der databesa ist "BORK BORK BORK".
Warning: Too many connections in
Unable to select database
Shouldn't that be
"Werniga: Esha tue amany conecctionsa in der
"Depression is merely anger without enthusiasm." - Anonymous
I have the same problem with this as any pro-my-agenda-over-yours approach. If what we are seeking is equality/respect, resorting to the same tactics are unlikely to legitimately modify behavior. It's not through lynchings and beatings that the civil rights movement succeeded. It's not through imperial conquest that India became an independent state.
And it isn't going to be through holier-than-thou rhetoric couched in do-unto-others-as-they-do-unto-you that the open source/free software movements are going to make converts.
What was our reaction to MS disabling access to the MSN sites?
Blazing anger.
And this is different exactly how?
When a Linux person does it, it's 'funny' (+1).
This is immature and childish.
True that.
I hope he comes to his senses and refrains from this kind of petty vendettas.
When people start ignoring his email (message->block sender), maybe then he'll get the idea: being a jackass to other people might be funny for roughly two seconds, but no longer than that.
[o]_O
So he wants people to be able to use any kind of software to read email, and is annoyed that he gets documents from Windows users which are unreadable in his email program. So his response is to make sure that other people cannot necessarily read his email messages, and he expects others to adjust their computing environment to read what he sends. How is this any different from his adjusting his own computing environment to read what they send? Or is it that he just believes that the Internet should be mutually unintelligible (I mean, more than it already is)?
-- Two men say they're Jesus. One of them must be wrong. - Dire Straits
As he pointed out, Outlook users send people unreadable, non-standard attachments all the time. What's the difference? Why do non-Outlook users always have to be the ones to conform to what Outlook users do?
Need a Python, C++, Unix, Linux develop
This post is in reply to your "exclude microsoft users" post, and the attitude in the article exemplified by this quote: ``It's true that I run a mailing list that does not allow posting from Windows users. Many people complain about this, but in my mind I see it as no different than a restaurant or dance hall having a dress code.''
When did we become such elitists? When users are arbitrarily excluded and abused in the name of "free software," I begin to think that pehaps these same people now toting the supremacy of their operating system might in another time promote the supremacy of their language, nationality, or race.
I see nothing productive in this article or the attitude of its creator. The point of our movement is to produce good, useful software, and to make it available to everyone. The point is not to force them to use it, or to punish those who don't. Where's the freedom in that?
You are confusing two different issues. One is the auto-killfile that I perform on myself, not allowing anyone using outlook to read my mails. The second is the "dress code" for posting to a mailing list I run. They're two different efforts.
The first says "I don't care if windows users can't read my mail"
The second says "I don't want windows users posting to my mailing list"
There is a distinction.
--
I noticed
It's getting about time to leave everywhere
and
I probably don't agree with what he is doing, but I can see that it is in some ways a good idea to punish people whose email programs do not follow the RFC's, because that may be the only way to get people to put pressure on the vendors to provide correct software.
Remember, part of MS strategy is to make life difficult for people who don't use MS software and want to interact with those who do. Selling clients that don't follow the RFC's is just a part of this. Maybe this will make a few users complain to microsoft that they can't read a properly formated email using their MS email clients and force MS to change its practices.
Anyway, the time will come when I'm the one to post results. I'll use Gnumeric, I think. I have been toying with the idea of actually posting a Gnumeric XML file to the list... Revenge!!! ;-)
Well, I'm not going to do it just for the revenge. It has to be illustrating some point.
This got me thinking: Since Gnumeric's native file format is based on XML, it should be possible to have it sensibly parsed and displayed in a browser that does support XML, including IE, given....?
OK, so this is the question: What would it take for people to get a readable table on their browser, straight from a Gnumeric XML file?
If this would work, it would illustrate a major point: How much more flexible these products are. Those who have experienced all M$ lock-ins and unreadable documents can suddenly access a document in a format they've never heard of.
Employee of Inrupt, Project Release Manager and Community Manager for Solid
--
I noticed
It's getting about time to leave everywhere
And this is different exactly how?
He is not a monopoly. Microsoft is. What he did (if intentional) was not illegal. What Microsoft did (if intentional) is.
GreyPoopon
--
Why is it I can write insightful comments but can't come up with a clever signature?
BTW, read this:
c e. html
.. )
http://free.bluemountain.com/home/ImportantNoti
There is evidence that MS has actually done something along the lines of what this gentleman did on purpose as a means of retribution to a company that opposed being bought out (or some other interest of MS's
"Old man yells at systemd"
First of all he is not being a petulant child. He points out a perfectly valid way of making a PLAINTEXT email message illegigible to Outlook users: start a line with the word begin. I would be pretty miffed if the provider of my mail client of choice has made decisions that dictate the manner in which I compose the body of an email. I think most rational Windows users would regard this "innovative" feature to be a flagrant abuse of power on the part of my email client vendor. The other tricks he plays are less insightful but bring to light a common complaint of non-Microsoft software vendors: Microsoft blatantly disregards many standards an hijacks others for personal gain. The second point, exclusion of Outlook clients from his mailing list is also not without precedent. If I wish to create a locale where like minded people can gather I will definitely put up some simple barriers to entry for people who cannot share my opinions. In this case, he has made some decisions about how email clients should work and he only wishes to share his list with those with similar points of view. Since it is his list and not a general public utility it is his right.
I recieve a LOT of mail. Much of it is from Windows users.
Those users expect me to be able to read their Word format files without complaint. (Like I am going to pay almost $400 for a word processor for 1-2 documents a week.)
They expect that I read their html formatted mail with bizzare IE-only extensions.
These are the same people who become totally baffled if I send them a ASCII document with Unix line wraps.
At some point you get tired of dealing with people who expect the world to conform to their expectations and platform while making *no* effort to adapt to anything outside of their narrow world-view.
My method of dealing with people who send Word documents is to return the favor by sending them Star Office format. It is amazing how much they complain about it. They expect me to install a very expensive package, but are totally unwilling to install something that costs them next to nothing. ($50 if they buy the boxed version.)
What I find even more interesting are the people who seem to be backing the Outlook user in this "fight". The Outlook bug that is being exploited is quite old. Not only has Microsoft refused to fix it, it appears that they have removed the work-around. (I still do not see why people continue to use Outlook. The only reason that I hear from people is because they need the calendaring support and shared folders. There are other programs that do similar things. They are just being lazy.)
Part of the "PC" movement in this country is the unwillingness (in fact that absolute abhorence) to tell someone when they are being stupid. Error-correction is no longer tolerated because someone's feelings might get hurt. Since when did the most sensitive and stupid gain control of what should or should not be done?
"Trademarks are the heraldry of the new feudalism."
Come on. Get over yourself. Equating OS/software "religious" wars to real-world racism and intolerance is a bit of a stretch. They are completely different issues. I don't hear you crying "elitism" about all the websites out there that are unusable with any browser except IE, or that require Flash.
Actually, I see this kind of strategy as a Good Thing -- it's a good way to raise people's awareness of the general Suckiness of M$ and their products. Broken software, free or propriatary, needs to be rooted out and destroyed.
The dress code analogy is a good one -- it's his list to do with as he pleases. If he wants to exclude M$ users, that is his perogative. For a technical mailing list, it's not that bad an idea at all to force prospective users to have enough clue to have to exersize their craniums a little to be able to join. Just think of how many idiots we could get rid of here on
Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
I read the english e-mail and he explains his position (I don't quite understand the hack though)
The hack is to begin the message body with
begin
Outlook interprets this as starting a uuencoded section, and turns perfectly readable text into gobbly-dy gook.
The other hack is to change the Reply-To: header as Outlook usually does when it marks the messages read. Then he adds a novel X header that seems to imply his email was actually censored somewhere along the way. So, the Outlook user sees gobblydy gook instead of a message bbdy if he sees the message at all, and if he tries to diagnose the problem will be immediately be misled by the novel X header into thinking he was censored. Whereupon he goes to his sysadmin, who will read the email in plain text, and laugh heartily. Or cry.
This has nothing to do with advocacy, monopolies, anti-this or that. Its good clean schlap-stick fun.
My personal X-headers include... /dev/null
X-Apparently-From: mars
X-Complaints-To:
Hmm.
grep -E '^X-[^:]+:' < read-messages| sort -u Should give me some more fodder. Hmm, those Importance and Priority headers might do something entertaining.
How free is it if you make him conform to your idea of what is normal?
We aren't "forcing him to conform", we're forcing him to write in a format usable by all (you know, free means free across all boards, including proprietary).
Didn't RMS recently write an article about convincing people to not use Word attachments in email??
Isn't this the OPPOSITE?
Funny how you view things on the other side, isn't it?
If someone sends you a word doc, and you can't read it, its a big issue and everyone is serious.
If someone sends something that only linux users can read, its funny, and lets all shout "hurray!"
Think about it. And if you still think the second point, then you are, in fact, elitest.
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
I understand the purpose of the ">" is to escape the "From " that separates emails. But I never understood why it was not unescaped upon reading the email.
By the way the problem is so common that the LaTeX manual has an index entry called, "From, line beginning with", and calls the problem "a bit of fossilized stupidity".
What was our reaction to MS disabling access to the MSN sites? And this is different exactly how?
In one case, case Microsoft software denied the user the ability to view content.
In the other case Microsoft software denied the user the ability to view content.
Hmm, I guess I see your point.
Start posting messages with pr0n attachments that cannot be viewed in Outlook Express. OE's market share will collapse.
pr0n - keeping monitor glass spotless since 1981.
To workaround this problem:
That's pretty funny.
>Its ok to say "Use anything except outlook" when
>you are on the linux side.
>
>What would you say, if I said use a program that
>can read Word docs [slashdot.org]??
The point about these anti-Outlook headers is that they're still perfectly conformant with RFCs 821, 822, et al. Any conformant mail-reader can read these messages just fine.
But there is no RFC for Word .doc format. In either case, the underlying message is "use a mail client that conforms to open standards (the RFCs)."
When Microsoft releases an RFC for .doc format, then this position will be hypocritical. But until then, it's perfectly consistent. (Alternatively, they could make Outlook obey the RFCs... then Mr. Moffitt's header hacks won't bother it any more.)
Kai MacTane: Web developer for hire in San Francisco
I know of Ubizen, a Belgian security firm, that filters out all of the Outlook posts from its incoming mail for al of its users. They simply send the message back, including an explanation to the sender that it isn't quite safe to use Outlook and that they're only allowing mail from other mail-clients. Considering this comes from a renown security firm, a lot of people take this advise very seriously. Of course, this isn't quite the same thing but it still is an interesting way to look at the 'Outlook Problem'.
this explains it
Anonymous posts are filtered.
What would you say, if I said use a program that can read Word docs??
I'd ask which RFC that's specified in so I could verify compliance. Email, unlike Word documents, is a real standard that was written specifically for ease of implementation and interoperability (even between machines with different ideas of character set).
The world welcomes MS to inspect the relevant RFCs and implement a compatable product. MS doesn't seem to have published a description of Word format anywhere.
Word is a proprietary format (not at all standard) that shifts like sand in the desert with no consideration of interoperability or safe interchange of data.
Outlook internally is one of the most poorly-engineered systems ever created. Its security model is a complete crock of shit that has several times nearly brought down the Internet. Microsoft's "programmers" wrote the attachment parsing code several times, each time being different and broken. (Proof: certain attachments aren't shown to the user because that broken code doesn't properly parse them, but if the user does "File->SaveAttachment" they *can* be saved because the saving code *does* properly parse them.)
You're free to bathe in a sewer if you want, but that doesn't mean people have to let you into their clubs.-- ;-)
Kuro5hin.org: where the good times never end.
This "attack" is nothing more than starting a line with the word
begin. Nothing more.
As the guy pointed out in his comments, they discovered it because someone on a mailing list happened to
begin a line with the magic word and *bam* every Outlook user who wasn't connected to an Exchange server (which sounds like a typical MS bug "fix") found the message to be garbled.
When MTAs and NNTP server had a from bug (where any line starting with
From was capitalized by the transport software, everyone agreed it was a bug. A nasty one, since it there were reasons it couldn't easily be fixed, but the message was still readable.
But suddenly we're "elitists" for saying that it's a bug - a critical bug - when MS Outlook interprets *any* line beginning with "begin" as the start of a UUENCODED block? Even though this produces unreadable garbage? And the latest versions of Outlook apparently don't even have an option that will allow the user to view the original message?
I agree there are some bloody annoying elitist attitudes on full parade here, but it seems to me that the elitists are the people who think every person on the planet should check their messages for any text that triggers Outlook bugs (e.g., lines beginning with "begin", any HTML keyword which will trigger the mandatory interpretation of the message as HTML, etc.) instead of MS admitting that they screwed the pooch on this one and issuing a quick patch.
They don't even have to use the same standards I demand of my own code - simply checking for a pattern where the "begin" is followed by an octal number would eliminate most of these false hits.
For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
You could, of course, avoid writing emails that would not exclude Outlook users, but you would have to be careful not to
begin any lines of your message wrong, which means that having your mailer arrange the line-breaks for you won't work.
Obviously, working around all of the bugs in software which people might use is a pain, and shouldn't be your
responsibility. After all, it is local mail delivery programs that deal with lines that start with "From". It would suck to
end up having to carefully tune your content to broken implementations. And if you've decided not to support broken mailers
why not trigger the bug intentionally, so people don't read part of your conversation before running into a message
they can't read? I think that people using mailers which don't understand the MIME format shouldn't stop you from using
attachments. If a message conforms to all applicable standards, it's fine by me. Attaching a Word document is perfectly
legitimate, although the document itself doesn't conform to any Internet Standards other than "binary data".
In related news, future versions of all Microsoft products will autocorrect any occurance of the word "begin" with a suitable replacement.
No word on when the riots by visual basic programmers furious that the new version of that language requires start/end blocks instead of begin/end blocks will end.
For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
If you can get your high horse to slow down long enough to step off it for a minute or two, you could install any of a zillion open source tools to modify your headers as messages pass in/out of your network, solving the problem and allowing you to use any MUA you please.
His point was that he wanted people to have to do a little work before they could be a part of the list. Ways of assessing that are imperfect, and his is just one. You can demonstrate you've done it by installing a non-default OS and/or MUA on your machine, or you can do as I've suggested above. Either way, you then pass, and are free to play.
"Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS