Olin Lathrop wrote :

> Really!!?
> 
> Can you give an example where a 80 character line gets corrupted or
> mishandled?

Sure.

Here is one example of (part of) a mail which has a encoded ZIP
file in it. The ZIP file was encoded with a tool that creates 80 char
lines. The 2'nd example is what it should look like.

I'm not sure if the lines was "corrupted" or "mishandled", but they
was split on multiple lines at least.

The tool is now changed to produce 70 char lines, and we don't get 
this
"problem" now. Best looked at using a fixed space font, of course.

I can not go into to many details, but this mail was sent from a site
of a major US electronic outsourcing contractor to a server at a
major Swedish telecom company starting on "E"...

Regards,
Jan-Erik.



Encoding of file DISK_M2T:[TMP]TRCY2006071518501000.ZIP;1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(@@QIM5R_5$LT)3VT5DTfQ%TC%%L0@#M0eSL5DCN5@SL0@CL.(URP-
SLaam@C@5ag@DP@@Dah@HA
ag@H
B@$FQA5Cb@Dam@+GCb@B<??ag@B@@Hah@Hb@m@PM1AB@5DGan@H@TKM@ATc@m@@FY9;4(8
(7-=AF
b@,d
R@@mAc@f2MVg2@CL6@3M1TSL8TCL1@CL082e!YW3dG#"$eEEDE5W+"gG(L"_%UUO3)
GOIPBZF-?7
J:IF



Encoding of file DISK_M2T:[TMP]TRCY2006071518501000.ZIP;1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(@@QIM5R_5$LT)3VT5DTfQ%TC%%L0@#M0eSL5DCN5@SL0@CL.(URP-
SLaam@C@5ag@DP@@Dah@HAag@H
B@$FQA5Cb@Dam@+GCb@B<??ag@B@@Hah@Hb@m@PM1AB@5DGan@H@TKM@ATc@m@@FY9;4(8
(7-=AFb@,d
R@@mAc@f2MVg2@CL6@3M1TSL8TCL1@CL082e!YW3dG#"$eEEDE5W+"gG(L"_%UUO3)
GOIPBZF-?7J:IF



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist