image embedded in an email being treated like an attachment

[highcommander4]

image embedded in an email being treated like an attachment

[GoogleCodeExporter]

Hello Dee,

Maybe it's not the same on a linux client as mac/windows, but I can't really 
"copy and paste" a picture into an email. I can only attach an image.

I suspect that when you're copy-pasting it's creating an HTML email which 
should work with Gmail Delay Send. 

Could you try one more experiment for me? Could you compose an email, add some 
colored font (doesn't matter what), attach an image then send? I'm wondering if 
the font will come out black & white.

Thanks!
-Blair

Original comment by [email protected] on 6 Nov 2012 at 4:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Every email I receive with an embedded image shows as attachment. I am unable 
to easily identify emails with 'real' attachments.

Original comment by [email protected] on 11 Nov 2012 at 10:48

[GoogleCodeExporter]

Hello, i have same issue and what i did i send two emails in different ways.
One in normal way and one with delay.
Normal way(instant) message that show image embeded and behind the message is 
looking like that:
[image: Inline image 1]

Delay way - message is showed as an attachment and behind the message is 
looking like that:

<img  
src="?view=att&th=13c90aed8ecc0334&attid=0.1&disp=emb&realattid=ii_13c90a69cb3d0
979&zw&atsh=1"  
alt="Inline image 1" width="200" height="200"><br><div><font  
face="monospace"><br clear="all"></font><div><div dir="ltr">

Using this script and label practically transform it in an html wich contain 
css(java) and gmail block some of this features - in fact they have an 
web-based application - and the images and codes could affect their frames.

Make sense?
There is a way to solve?

Thank you

Original comment by [email protected] on 31 Jan 2013 at 1:19

[GoogleCodeExporter]

"We are aware where users are having problems forwarding messages with inline 
images, as the images are not appearing for the recipients of the email.  While 
we investigate the issue, please try changing the subject line when you forward 
the message."

Original comment by [email protected] on 31 Jan 2013 at 1:39

[GoogleCodeExporter]

There's two ways inline images are inserted into an email.  

1.  There is a lab that allows you to drag and drop images directly into your 
email.  GmailApp.sendEmail used by google scripts like delay-send sends these 
images as attachments. The source address looks similar to what was noted in 
comment #4.   When you send the email directly, the images are displayed as 
expected since GmailApp.sendEmail isn't being used.

2.  You can have inline images as part of your signature.  This means that 
images are stored on google servers and the htmlbody uses the CID:imagekey as 
the source "address" for the images.  When you compose your email, the 
signature and corresponding images are included.  When you send the email 
directly, the images are displayed as expected.  Delay-send the email, the 
images aren't sent out at all or it doesn't appear to be sent.  The recipient 
receives no attachments for those images and the inline images appear as boxes 
with the red x.  So this issue resembles very closely to the forwarded message 
issue noted in comment #5 since the messages (including the images) are stored 
on google servers and then forwarded.

The link to a page below appears to address item #1.  The response from Peter 
Herrmann has the relevant code.

http://stackoverflow.com/questions/11750662/convert-a-javascript-array-into-a-js
on-object/11769858#11769858

However, I wasn't able to get it to work.

This page here -- 
https://code.google.com/p/google-apps-script-issues/issues/detail?id=1659 -- 
suggests that you need to grab the real address of the images for item #2.  Of 
course, I wasn't able to implement that, either.

Original comment by [email protected] on 16 May 2013 at 6:16

[GoogleCodeExporter]

Issue 50 has been merged into this issue.

Original comment by [email protected] on 18 May 2013 at 1:33

[GoogleCodeExporter]

Issue 131 has been merged into this issue.

Original comment by [email protected] on 26 Dec 2013 at 11:07

[GoogleCodeExporter]

Issue 122 has been merged into this issue.

Original comment by [email protected] on 21 Mar 2014 at 9:48

[GoogleCodeExporter]

Issue 147 has been merged into this issue.

Original comment by [email protected] on 21 Mar 2014 at 9:49

[GoogleCodeExporter]

This continues to be an issue, and is now an issue when using the main Gmail 
web client. 

The feature to insert an image in-line (whether via copy/paste, drag-and-drop, 
or clicking the Insert Photo button in the Compose window) has now been merged 
into the main Gmail product, and is no longer a separate Gmail Labs project.

When sending normally in Gmail, you get a img tag that shows "<img 
src="cid:xxxx" ... />", and the image is base64-encoded and added as a MIME 
part with "Content-Disposition: inline;" and "Content-ID: <xxxx>". 

When using Gmail Delay Send, inserting an inline image into a message results 
in an img tag with the alternate text "Inline image 1" being displayed in the 
sent message. The img tag has a src URL that references a non-existent 
attachment (as shown in Comment #4) and the image is never added to the email 
as a MIME part.

Original comment by [email protected] on 24 Nov 2014 at 7:38

[GoogleCodeExporter]

Unfortunately I will be unable to use this service if this doesn't get 
corrected. I was using Boomerang for awhile and this was not an issue. There 
has to be a way to get the images to show up correctly. Putting an image in the 
signature is not an option for what I need to do. 

Original comment by [email protected] on 12 Feb 2015 at 8:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

problem continue..pl solve the issue if you can.

Original comment by [email protected] on 21 Mar 2015 at 6:53

[GoogleCodeExporter]

Same issue here, email with inline images gets corrupted and even in the "sent" 
image label my mail does not show the images anymore.
There is also no error reported on this user data corruption.
It would IMHO be far better to just report an error than to send corrupted 
emails.

Is there anything we can help on with this?

Original comment by [email protected] on 14 Apr 2015 at 7:00

[GoogleCodeExporter]

Issue 206 has been merged into this issue.

Original comment by [email protected] on 8 Jul 2015 at 12:16