Received-SPF: neutral (gmail.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
From: GandalfG8@aol.com
Message-ID: <364.2fdd160.31792638@aol.com>
Date: Thu, 20 Apr 2006 14:00:24 EDT
To: rsgb_lf_group@blacksheep.org
MIME-Version: 1.0
Subject: Re: LF: Top load coil at ground level?
Content-Type: multipart/alternative; boundary="-----------------------------1145556024"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O


-------------------------------1145556024
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

 
In a message dated 20/04/2006 17:03:50 GMT Daylight Time, WarmSpgs@aol.com  
writes:

Actually, it's a propagation problem.  Some mail systems don't like  to 
handle multiple attachments, and enclosed them in a Zip file.  Usually  this works 
fine.  Unfortunately, there's something about the  way multiple file 
attachments are encoded when passing through this  reflector that AOL doesn't seem to 
understand, so what they zip up for me is  the raw MIME-encoded attachments, 
without reconverting them to their  original formats and filenames.
 
Single files pass through OK.  Therefore, since I'm apparently not  the only 
person who encountered this, may I suggest either sending single  files per 
message, or zipping them into a single file prior to  transmission.


Hi John
 
AOL can often be a pain on this and did it to me too but, with Winzip  
anyway, the files can still be read.
When I opened the original zip file that AOL had wrapped them in there were  
the two mim files you mentioned.
Winzip sees these as compressed files too so double clicking either  from 
within Winzip, I didn't bother to extract them first, starts up another  Winzip 
session which opens up the selected file to reveal the jpg inside, which  can 
then also be opened from within the archive.
Messy yes, but it did work ok.
However, I would agree that creating a single zip file before  transmission 
is the easiest way to avoid problems.
 
regards
 
Nigel
G8PZR

-------------------------------1145556024
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In a message dated 20/04/2006 17:03:50 GMT Daylight Time, WarmSpgs@aol.=
com=20
writes:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>
  <DIV>Actually, it's a propagation problem.&nbsp; Some mail systems don't l=
ike=20
  to handle multiple attachments, and enclosed them in a Zip file.&nbsp; Usu=
ally=20
  this works fine.&nbsp; Unfortunately, there's something about the=20
  way&nbsp;multiple file attachments are encoded when passing through this=20
  reflector that AOL doesn't seem to understand, so what they zip up for me=20=
is=20
  the raw MIME-encoded attachments,&nbsp;without reconverting them to their=20
  original formats and filenames.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Single files pass through OK.&nbsp; Therefore, since I'm apparently n=
ot=20
  the only person who encountered this, may I suggest either sending single=20
  files per message, or zipping them into a single file&nbsp;prior to=20
  transmission.</DIV></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>Hi John</DIV>
<DIV>&nbsp;</DIV>
<DIV>AOL can often be a pain on this and did it to me too but, with Winzip=20
anyway, the files can still be read.</DIV>
<DIV>When I opened the original zip file that AOL had wrapped them in there=20=
were=20
the two mim files you mentioned.</DIV>
<DIV>Winzip sees these as compressed files too so double clicking&nbsp;eithe=
r=20
from within Winzip, I didn't bother to extract them first, starts up another=
=20
Winzip session which opens up the selected file to reveal the jpg inside, wh=
ich=20
can then also be opened from within the archive.</DIV>
<DIV>Messy yes, but it did work ok.</DIV>
<DIV>However, I would agree that creating a single zip file&nbsp;before=20
transmission is the easiest way to avoid problems.</DIV>
<DIV>&nbsp;</DIV>
<DIV>regards</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nigel</DIV>
<DIV>G8PZR</DIV></FONT></BODY></HTML>

-------------------------------1145556024--