On 27 Jun 2005 at 12:50, Phil Daley wrote: > At 6/27/2005 12:07 PM, David W. Fenton wrote: > > >On 27 Jun 2005 at 8:18, Brad Beyenhof wrote: > > > >> On Sat, 25 Jun 2005 12:39:25 -0500, Robert Patterson wrote: > >> > Has anyone ever seen this error? I'm getting it when I try to > open a >> > file in Fin05b. My friend has sent both the .mus and the > .etf, and >> > both get the same error. >> >> I have seen that > before. It's usually fixed when I get the sender to >> resend in a > compressed file (.zip, .sit, etc.). Sometimes sending >> files > "naked" through email can slightly corrupt them, but packaged in >> a > compressed file they should be readily accessible once unzipped. > > >Only a defective email client could corrupt an attached file. > > I don't believe this is true. > > An ISP can corrupt a file, especially if they don't know what file > type it is. AOL is infamous for this.
I've never heard of such a thing. Yes, AOL can misidentify the encoding standard, or improperly encode the text boundaries, or improperly describe the content type of the attachment. But those are all problems that happen in the AOL email client, so far as I'm aware. If their email servers are looking inside the email message envelope and rewriting content, then they have really defective email servers, since that breaks all the rules about how email is supposed to be handled. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
