Hello Steven, Monday, August 27, 2012, 6:16:04 AM, you wrote:
>>Content-Type: IMAGE/JPEG; name="int_1.jpg" >>Content-ID: <4C67E43C.01CD8270.49246F31.44A035FC_csseditor> >>Content-transfer-encoding: base64 >>Content-Disposition: attachment; filename="int_1.jpg" SA> Thus gmail (and Eudora) were relating to the picture as an attachment. SA> This says that int_1.jpg is an attachment. I replied to your mail by embedding a picture, but it was too big for this list (unless a moderator lets it through). I also CC'ed your PM address, so you should have received it in your Inbox. SA> If TB! was sending it as an embedded graphics, the receiver would get SA> a content-disposition MIME header like this: SA> Content-Disposition: inline; filename="file name.jpg" In the mail which I BCC'ed to myself, I see the following headers in the Incoming message: > MIME-Version: 1.0 > Content-Type: multipart/mixed; > boundary="----------09D0330A23FDECB7B" > > ------------09D0330A23FDECB7B > Content-Type: multipart/alternative; > boundary="----------1050641801D5AC6BB" > > > ------------1050641801D5AC6BB > Content-Type: text/plain; charset=iso-8859-15 > Content-Transfer-Encoding: quoted-printable In the HTML part, I find this: > <span style=3D" color: #800080;"> >>Content-Type: IMAGE/JPEG; na= > me=3D"int_1.jpg"<br> > >>Content-ID: > <4C67E43C.01CD8270.49246F31.44A035FC_csseditor= > ><br> > >>Content-transfer-encoding: base64<br> > >>Content-Disposition: attachment; filename=3D"int_1.jpg"<br> > <br> And at the end, here is the picture: > ------------09D0330A23FDECB7B > Content-Type: image/jpeg; > name="Grandma listen.jpg" > Content-Transfer-Encoding: base64 > Content-ID: <7FD40B88.01CD8794.62089E6C.3B478E23_csseditor> > > /9j/4AAQSkZJRgABAgAAAQABAAD//gAEKgD/4gIcSUNDX1BST0ZJTEUAAQEAAAIMbGNtcwIQ > AABtbnRyUkdCIFhZWiAH3AABABkAAwApADlhY3NwQVBQTAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAA9tYAAQAAAADTLWxjbXMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAApkZXNjAAAA/AAAAF5jcHJ0AAABXAAAAAt3dHB0AAABaAAAABRia3B0 > AAABfAAAABRyWFlaAAABkAAAABRnWFlaAAABpAAAABRiWFlaAAABuAAAABRyVFJDAAABzAAA > AEBnVFJDAAABzAAAAEBiVFJDAAABzAAAAEBkZXNjAAAAAAAAAANjMgAAAAAAAAAAAAAAAAAA So, it's MIME encoded like an attachment, but then, every HTML mail is, isn't it? Isn't any HTML part technically an attachment? In truth, I don't know anything, just throwing these header fragements into the list to see whether this is really wrong behaviour of TB!. -- Cheers, Thomas. http://thomas.fernandez.hat-gar-keine-homepage.de/ Message reply created with The Bat! 5.2 under Windows XP 5.1 Build 2600 Service Pack 3 ________________________________________________ Current version is 4.2.42 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
