begin <5f303kw5dgr7$.23nakdbl9h7c$ XXXX@XXXXX.COM >,
Edwin < XXXX@XXXXX.COM > writes:
Here's a link, one of many, that simply explains the format of
There is also the uuencode 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:
To workaround this problem:
* Do not start messages with the word "begin" followed by two
* Use only one space between the word "begin" and the following
* 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.