Yes, it is a perfectly valid uuencoded attachment. My mailer (PMMail) kindly
identified it as an attachment and gave me an icon to extract it.
However, Microsoft has apparently decided to DROP support for uuencoded
attachments in the latest releases of Outlook and Outlook Express. I find
this decision unsupportable. For at least a decade before MIME rolled
around, uuencode was the ONLY way to create attachments. The technology is
well-established and well-understood.
Microsoft is making it more and more difficult for Outlook users to
communciate with anything other than other Outlook users. That might be a
conscious decision, but it is despicable. Having at first ignored the
Internet, they now want to control it.
···
On 16 Jul 2003 17:48:04 -0400, "Roach, Mark R." <mrroach@cimplify.net> wrote:
On Wed, 2003-07-16 at 17:05, Jean-Michel Fauth wrote:
Hi,
- Here the sample code that shows my problems.
- Attached code: atextctrl.py
[snip]
begin 600 atextctrl_py
M(RTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T-"B,@871E>'1C=')L+G!Y#0HC('=I
[snip]
end
wow, I would have thought that even outlook express used proper mime
attachments, is that uuencode?
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
Well, then don't use Outlook. For the poor windows users who have to rely on
3rd party software to get basic functionality there is still stuff like
pegasus or eudora out there.
You can start yelling at me for the sarcastic remark, but truth is that MS
never implemented a standard they didn't invent correctly. Also Outlook has a
limit of 2GB mail and will fail with a stupid error message after that - that
happens when you stuff everything in one single file.
I keep all mails with all my customers and I currently have some 15GB mail -
and my mailer handles it flawlessly (Given, I wouldn't have to keep 10 year
old mails 
)
···
On Thursday 17 July 2003 10:32 am, Tim Roberts wrote:
On 16 Jul 2003 17:48:04 -0400, "Roach, Mark R." <mrroach@cimplify.net> wrote:
>On Wed, 2003-07-16 at 17:05, Jean-Michel Fauth wrote:
>> Hi,
>>
>> - Here the sample code that shows my problems.
>> - Attached code: atextctrl.py
>
>[snip]
>
>> begin 600 atextctrl_py
>> M(RTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
>> M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T-"B,@871E>'1C=')L+G!Y#0HC('=I
>
>[snip]
>
>> end
>
>wow, I would have thought that even outlook express used proper mime
>attachments, is that uuencode?
Yes, it is a perfectly valid uuencoded attachment. My mailer (PMMail)
kindly identified it as an attachment and gave me an icon to extract it.
However, Microsoft has apparently decided to DROP support for uuencoded
attachments in the latest releases of Outlook and Outlook Express. I find
this decision unsupportable. For at least a decade before MIME rolled
around, uuencode was the ONLY way to create attachments. The technology is
well-established and well-understood.
Microsoft is making it more and more difficult for Outlook users to
communciate with anything other than other Outlook users. That might be a
conscious decision, but it is despicable. Having at first ignored the
Internet, they now want to control it.
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
--
UC
--
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417