The "begin bug" is not a bug [was The "begin bug" is a bug]

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Edwi » Sat, 18 Sep 2004 02:23:07



Once again, viewing message source shows the reply:






Showing off how really clever you are, do you?
Now ask yourself how long anyone else here knew about this already
And ask why *anyone* else who does not use OE can read the messages just
fine without any additional hoopla


As I told you before (and you snipped) this is no "bug" triggered by a
"typo." You inserted your "begin" and two spaces ahead of the attribution
generated by the news reader. This is nothing more than you making
malicious use of your knowledge of how OE works.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Rick » Sat, 18 Sep 2004 06:00:48


... becaus ewe use newsreaders that work.


Uh, no. This is m$ refusing to fix a bug in its newsreader.

--
Rick

 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Edwi » Sat, 18 Sep 2004 07:08:08


Your spell checker doesn't seem to work all that well.


No, it's what I wrote above.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Rick » Sat, 18 Sep 2004 07:11:56


at the moment, it doen't. So what?


Uh, no. This is m$ refusing to fix a bug in its newsreader.

--
Rick
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Uncle Fest » Sat, 18 Sep 2004 07:50:31

begin On Thu, 16 Sep 2004 17:23:07 GMT, "Edwin" < XXXX@XXXXX.COM >







Waaaaah!



Uncle Fester
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Edwi » Sun, 19 Sep 2004 02:46:23


Go complain to who wrote it.


No, it's not a bug. It's not accidental behavior that OE treats what
follows "begin," then two spaces, as an attachment, it's designed to work
that way.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Edwi » Sun, 19 Sep 2004 05:33:52


No it's not. A bug is not intentionally coded behavior, as I said above.


It's not a bug because you don't give it your approval for the way to mark
an attachment.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by GreyClou » Sun, 19 Sep 2004 06:06:11


It's a bug. Claim that any other newsreader has this problem.

--
---------------------------------
The Golden Years Sux.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Edwi » Sun, 19 Sep 2004 07:29:16

n Fri, 17 Sep 2004 15:06:11 -0600, GreyCloud wrote:


Reread above.


Irrelevant. And it's only a problem amongst those who choose to make it a
problem.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Rick » Sun, 19 Sep 2004 08:39:02


It is designed to affect uuencoded files, not text. The other newsreaders
get it right. m$ hasn't.

--
Rick
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Sinister M » Sun, 19 Sep 2004 10:06:11

On 2004-09-17, Edwin < XXXX@XXXXX.COM > sputtered:



Rescored.

Previously: -7171 for 40tude whatever.
or -8200 for MICROS~1 Outhouse Excess
Currently: -9999 for being obtuse.

There are a couple of others down there with you now. Say hi to Relf,
Bailo, SCOoke, Kadachadda Kiddie, etc.

--
SirCam - Innovative Microsoft peer-to-peer software.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by rgc » Sun, 19 Sep 2004 10:57:14

begin <5f303kw5dgr7$.23nakdbl9h7c$ XXXX@XXXXX.COM >,
Edwin < XXXX@XXXXX.COM > writes:


Here's a link, one of many, that simply explains the format of
uuencoded data:

http://www.yqcomputer.com/

There is also the uuencode[5] man page. Now show me any link for
uuencode that says 'begin text' indicates start of uuencode data?
Whether the windows programmer who implemented it misread the spec
or just coded it badly is irrelevant. It is a bug. MS cannot be
bothered to fix it. Their 'workaround' is just pathetic:

< http://www.yqcomputer.com/ ;

WORKAROUND
To workaround this problem:

* Do not start messages with the word "begin" followed by two
spaces.
* Use only one space between the word "begin" and the following
data.
* Capitalize the word "begin" so that it is reads "Begin."
* Use a different word such as "start" or "commence."

Now lets say you received an important email which had a line which
started 'begin '. I've already posted an article on how this can
happen. So you reply to the sender with the MS 'workaround' and ask
them to resend the email with the offending 'begin ' changed to not
trigger the bug. You are going to look like a real prat to the sender
in the same way you look like a real prat on COLA.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by GreyClou » Sun, 19 Sep 2004 11:41:59


Edwin wrote:


So? It's still a bug. Matter of fact, OE 6 is the only one that screws
it up.

--
---------------------------------
The Golden Years Sux.

 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Quantum Le » Sun, 19 Sep 2004 12:03:01


Last time I looked uuencoded file were text, it just depends on if the
newsreader checks to see if it a valid attachment, OE assume the turkey is
sending a file, and most of the rest check it if the idiot screwed up.
 
 
 

The "begin bug" is not a bug [was The "begin bug" is a bug]

Post by Linu » Sun, 19 Sep 2004 21:05:27

Error BR-549: MS DRM 1.0 rejects the following post from Roy Culley:


I can't be arsed to check out the specs for attachments, but my Inbox
shows that message parts are demarcated in a special way:

------_=_NextPart_001_01C47E04.7C5A0851
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

And those frickin' messages sent from Microsoft mailers have another
feature to indicate that a message has attachments:

X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:

So basically, Microsoft programmers can't even be bothered to check
for their own X tags. Or maybe they simply rely on checking the
value of "X-MS-Has-Attach".

Idiots.

I thought Microsoft hired only smart people?

I now think that Microsoft hires only people who talk a good story with
perfect-seeming confidence.

--
[X] Check here to always trust content from Linut