3 ms·
Same here. Looking at the email source the MIME looks like it should work, but for some reason clients aren't interpreting it as HTML. Content-Type: multipa
by guelo 16y ago
Same here. Looking at the email source the MIME looks like it should work, but for some reason clients aren't interpreting it as HTML.
Content-Type: multipart/alternative; boundary=000e0cd3282edb3e4e04a04d2812
--000e0cd3282edb3e4e04a04d2812
Content-Type: text/plain; charset=ISO-8859-1
--000e0cd3282edb3e4e04a04d2812
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<img src=3D"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABJ8AAAQaCAIAAABik=
k5NAAAgAElEQVR4nOzdd1QbZ77wcZK9e7O7d7PZTbmbZN+N49gG9xLHveACmOYKGIONe6V3MO42=
- archon810 16y agoI just posted an update with some findings - basically, those "3D" and =\r\n characters that something is adding (somewhere in Gmail) are messing everything up. We're this close to a working version of this...