OQSg3Z04AuFqB2IMd+atLwUBtpAHqKdUtbwGM1BTOgA5YhBr374ZAxhAqRVLzA53 UUSCBAKAYTBwbgyGA2AgsGqo0wMh7K0YEuj0sUxRoAfqB1vycBN21Ki8vOofBndRĬ1AKgH8ETE1lBgo7O2JaU2UFAgRoDGoAXV4PD2qYagl7Vp0JDKenfwado0QCAQOQĭIcDBgIFVgYBAlOxswR5r1VIUbCHwH8HlQWFRLYABVOWamACCkiJAAehaX0rPZ1B /M//////+ZAMwAACH/C05FVFNDQVBFMi4wAwGgDwAh+QQJFAALACwAAAAAKAA8ĪAME+3DJSWt1Nuu9Mf+g5IzK6IXopaxn6orlKy/jMc6vQRy4GySABK+HAiaIoQdg This is a message with multiple parts in MIME format.Ĭontent-Type: text/plain charset="utf-8"Ĭontent-Type: multipart/related boundary="related_boundary" mbs extension): Fromįrom: HTML Messages with Embedded Pic in SignatureĬontent-Type: multipart/alternative boundary="alternative_boundary" Or, here's a multipart/alternative, multipart/related example as an mbox file (save as windows newline format and put a blank line at the end. You'd basically have a multipart/mixed, multipart/alternative, multipart/related message where the image attachment is in the related part.Ĭlients shouldn't block this image either as it isn't remote. In some clients, src="sig.png" will work too. The image should be embedded in the message as an attachment like this: -boundaryĬontent-Disposition: inline filename="sig.png"Īnd, the HTML part would reference the image like this:
0 kommentar(er)
