From owner-freebsd-questions Thu Nov 18 0:54:50 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id 3E1FD1503C for ; Thu, 18 Nov 1999 00:54:45 -0800 (PST) (envelope-from james.wilde@telia.com) Received: from tbvhks12 (t1o72p104.telia.com [62.20.150.104]) by mailf.telia.com (8.9.3/8.9.3) with SMTP id JAA19511 for ; Thu, 18 Nov 1999 09:54:43 +0100 (CET) Message-ID: <008e01bf31a2$d09a0140$8c0aa8c0@hk.tbv.se> From: "James A Wilde" To: References: <015a01bf30e8$1c8298d0$8c0aa8c0@hk.tbv.se> <19991117210813.B316@marder-1> Subject: Re: Corruption of file attachments passing late BSD relayers Date: Thu, 18 Nov 1999 09:56:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your input, Mark. > This is not corruption. M$ proprietry files are binary so they are > being uuencoded (which maps 3 bytes into 4 so that all bytes can > be represented in printable chars). This explains the 30% increase > in size and the CR/LF's as uuencode also splits the resultant file > into fixed length lines. All you need is to uudecode(1) them. > Netscape can do this and I'm sure that even M$ mail readers can as > well; we have a mix of Unix and M$ (Outlook) systems at work and > passing binary attachments poses no problems. We don't use uuencode, Mark, since mime can reputedly handle the special = characters in European languages better than uuencode. All the files = are mime encoded. What I have discovered is that all mails, both corrupt and noncorrupt = are 30% increased in size as mails. It is when one tries to save the = file to disk that the good files reduce back to the 30k file size and = the bad files remain at the 40k expanded size. WhenI examine the messages with a hex editor I can see that the two = files include exactly the same information with the exception of the = header. In the bad files this includes considerably more 'next_part' = tags, and the file ends with a 'next_part' tag. mvh/regards James Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message