On Wed, 2 Nov 2011, [email protected] wrote:

} Thunderbird handles it fine, though if you turn off display of inline 
} attachments it will also not display the final text part (both are 
} presented as attachments); as a practical matter, unless you know the 
} capabilities of your recipient, i would avoid inline images in plain 
} text email

I think the issue is where one drags a file when composing in Mail.app. I 
have the habit of writing things, when helping friends/family, and taking 
screenshots as examples. Eg: I would include some text and say, "as the 
image below shows", and then drag a Skitch-created jpg below that text, 
then continue typing more text.

If I, instead, drag the images to the bottom of the e.mail, then Mail.app 
apparently attaches them "like normal" and the recpient sees my entire 
text and attachments. 

An "inline" image, as you stated, is just one part of a message that has 
multiple attachments. Since I mainly use Pine/Alpine [a text-based e.mail 
MUA], I often see text, then a place-holder text showing that there's an 
image, and then more text. I'm not crazy about the fact that Outlook or 
other e.mail MUAs apparently ignore any text "after" an image is attached. 
When using Postbox/Thunderbird, I've never done an "inline" image, since 
dragging a screenshot to the T-bird compose window simply opens up an 
attachment pane which the image gets placed in. [it's actually a rather 
cool feature]. 

I have VMware and a Win2k and WinXP install that I should play with and 
see which version[s] of Outlook don't like this [or if T-bird doesn't as 
well]. I'm a very anti-HTML e.mail person, so I have no intention of 
changing that setting. It just feels like that with Mail.app's ease of 
use, it seems silly to use old Gopher-style links to the images [eg: where 
I would normally put screenshot #1, insert text that says, [see 
screenshot1.jpg], and hope that the recipent pays attention to the 
filenames, as it would make matters worse if they viewed the 2nd 
screenshot, thinking it was the first!]. 

BTW, this is Mail.app with 10.6.8. My dev laptop has 10.7.1, but I've had 
so many issues with Lion that I only run XCode on it; perhaps this 
behavior with Mail.app has changed, but looking at the Apple Support 
forums, I see that even in 10.3 Mail.app was behaving the same way. :(

/vjl/
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Reply via email to