| Home | Register | FAQ | Members List | Search | Today's Posts | Mark Forums Read |
|
|
#1 (permalink) |
|
i am to misbehave
Join Date: Nov 2005
Location: London, UK
Posts: 9
|
base64 content transfer encoding
Not sure if this is the right place to post, but I'll give it a shot... I came across a newsletter sent out by a certain travel company recently, which contained base64-encoded images. (I think spammers use this method to get images through to your inbox, too). I also send out a newsletter to a large number of customers monthly, and would like to use the same method to add images (remotely hosted) to the emails. Encoding the image URL with base64 is no problem, but I can't get my head around content IDs and what not... anyone know of a good 'how-to' on base64 encoding/decoding for MIME? Thanks in advance. |
|
|
|
|
|
#4 (permalink) |
|
Macguyver
Join Date: Aug 2005
Posts: 10
|
The content ID has nothing to do with the encoding Base64 encoding is just a system which allows binary files such as images to be sent as plain text so that mail servers and clients don't choke on it. Content IDs are used to allow you to reference attachments from within other parts of a multi-part e-mail. The content IDs themselves just have to be unique throughout the e-mail. They can be ‘image1’, ‘image2’, ‘image3’ if you really want, though that would probably get confusing. Stick to alphanumeric characters, full stops and undercores, and if I remember rightly they're usually suffixed by whatever ‘Message-ID’ you've chosen, but that's just a convention. |
|
![]() |