Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.apps > #20018 > unrolled thread

Sending Images to Windows Users (and AOL)

Back to article view | Back to comp.sys.mac.apps

Contents

  Sending Images to Windows Users (and AOL) Matthew Lybanon <lybanon@earthlink.net> - 2013-12-20 12:39 -0600
    Re: Sending Images to Windows Users (and AOL) Jolly Roger <jollyroger@pobox.com> - 2013-12-20 18:59 +0000
      Re: Sending Images to Windows Users (and AOL) isw <isw@witzend.com> - 2013-12-20 22:18 -0800
    Re: Sending Images to Windows Users (and AOL) nospam <nospam@nospam.invalid> - 2013-12-20 14:17 -0500
      Re: Sending Images to Windows Users (and AOL) Barry Margolin <barmar@alum.mit.edu> - 2013-12-20 14:53 -0500
        Re: Sending Images to Windows Users (and AOL) Matthew Lybanon <lybanon@earthlink.net> - 2013-12-20 16:11 -0600
          Re: Sending Images to Windows Users (and AOL) Barry Margolin <barmar@alum.mit.edu> - 2013-12-20 17:27 -0500
            Re: Sending Images to Windows Users (and AOL) Matthew Lybanon <lybanon@earthlink.net> - 2013-12-21 10:40 -0600
              Re: Sending Images to Windows Users (and AOL) isw <isw@witzend.com> - 2013-12-21 10:59 -0800
                Re: Sending Images to Windows Users (and AOL) Barry Margolin <barmar@alum.mit.edu> - 2013-12-21 16:18 -0500
                Re: Sending Images to Windows Users (and AOL) Matthew Lybanon <lybanon@earthlink.net> - 2013-12-22 10:25 -0600
                  Re: Sending Images to Windows Users (and AOL) nospam <nospam@nospam.invalid> - 2013-12-22 14:02 -0500
                    Re: Sending Images to Windows Users (and AOL) Barry Margolin <barmar@alum.mit.edu> - 2013-12-22 23:10 -0500
                      Re: Sending Images to Windows Users (and AOL) Michael Vilain <vilain@NOspamcop.net> - 2013-12-22 20:44 -0800
                  Re: Sending Images to Windows Users (and AOL) Lewis <g.kreme@gmail.com.dontsendmecopies> - 2013-12-22 23:32 +0000
                  Re: Sending Images to Windows Users (and AOL) dorayme <do_ray_me@bigpond.com> - 2013-12-23 11:38 +1100
                Re: Sending Images to Windows Users (and AOL) Wes Groleau <Usenet@Grolea.us> - 2013-12-23 00:36 -0500
          Re: Sending Images to Windows Users (and AOL) dorayme <do_ray_me@bigpond.com> - 2013-12-21 10:33 +1100
          Re: Sending Images to Windows Users (and AOL) Wes Groleau <Usenet@Grolea.us> - 2013-12-20 21:28 -0500
            Re: Sending Images to Windows Users (and AOL) Wes Groleau <Usenet@Grolea.us> - 2013-12-20 21:33 -0500
              Re: Sending Images to Windows Users (and AOL) dorayme <do_ray_me@bigpond.com> - 2013-12-21 20:45 +1100
      Re: Sending Images to Windows Users (and AOL) dorayme <do_ray_me@bigpond.com> - 2013-12-21 09:26 +1100
    Re: Sending Images to Windows Users (and AOL) "John Varela" <newlamps@verizon.net> - 2013-12-20 21:30 +0000
      Re: Sending Images to Windows Users (and AOL) dorayme <do_ray_me@bigpond.com> - 2013-12-21 09:20 +1100
      Re: Sending Images to Windows Users (and AOL) Barry Margolin <barmar@alum.mit.edu> - 2013-12-20 17:23 -0500
      Re: Sending Images to Windows Users (and AOL) nospam <nospam@nospam.invalid> - 2013-12-20 17:26 -0500
        Re: Sending Images to Windows Users (and AOL) "John Varela" <newlamps@verizon.net> - 2013-12-22 02:43 +0000
      Re: Sending Images to Windows Users (and AOL) Patty Winter <patty1@wintertime.com> - 2013-12-20 22:27 +0000
        Re: Sending Images to Windows Users (and AOL) nospam <nospam@nospam.invalid> - 2013-12-20 18:40 -0500
          Re: Sending Images to Windows Users (and AOL) Patty Winter <patty1@wintertime.com> - 2013-12-21 02:24 +0000
        Re: Sending Images to Windows Users (and AOL) Lewis <g.kreme@gmail.com.dontsendmecopies> - 2013-12-21 06:02 +0000
      Re: Sending Images to Windows Users (and AOL) Wes Groleau <Usenet@Grolea.us> - 2013-12-20 21:43 -0500
        Re: Sending Images to Windows Users (and AOL) Michelle Steiner <michelle@michelle.org> - 2013-12-20 20:24 -0700
    Re: Sending Images to Windows Users (and AOL) Michael Vilain <vilain@NOspamcop.net> - 2013-12-20 21:03 -0800

Page 1 of 2  [1] 2  Next page →

#20018 — Sending Images to Windows Users (and AOL)

I use Mail.app for email.  When I send image attachments, some Windows 
users complain that the images are "embedded" in the message body, not 
attachments.  Searching on the Microsoft website unearthed the 
information that, in Outlook, although image attachments APPEAR to be in 
the message body when messages are in RTF format, they are still 
attachments.  And Microsoft gives detailed instructions on how to get 
those image attachments.

Sometimes those detailed instructions don't help.  With some people, if 
they can't get the images in the way they are accustomed to, NOTHING you 
(or MIcrosoft) tell them makes any difference.  So I have learned to 
choose Make Plain Text from Mail.app's Format menu, I always check the 
Send Windows-Friendly Attachments box, and I choose Insert Attachments 
at End of Message in Edit menu/Attachments.

But even so, recently a Windows user who has AOL told me that "I got the 
images in the body of the email, but did not get any attachments."  Does 
anyone have any insight into this problem, and (even better) suggestions 
about how to deal with it?

[toc] | [next] | [standalone]

#20019

On 2013-12-20, Matthew Lybanon <lybanon@earthlink.net> wrote:
> I use Mail.app for email.  When I send image attachments, some Windows 
> users complain that the images are "embedded" in the message body, not 
> attachments.  Searching on the Microsoft website unearthed the 
> information that, in Outlook, although image attachments APPEAR to be in 
> the message body when messages are in RTF format, they are still 
> attachments.  And Microsoft gives detailed instructions on how to get 
> those image attachments.
>
> Sometimes those detailed instructions don't help.  With some people, if 
> they can't get the images in the way they are accustomed to, NOTHING you 
> (or MIcrosoft) tell them makes any difference.  So I have learned to 
> choose Make Plain Text from Mail.app's Format menu, I always check the 
> Send Windows-Friendly Attachments box, and I choose Insert Attachments 
> at End of Message in Edit menu/Attachments.
>
> But even so, recently a Windows user who has AOL told me that "I got the 
> images in the body of the email, but did not get any attachments."  Does 
> anyone have any insight into this problem, and (even better) suggestions 
> about how to deal with it?

IMO, it's not your responsibility to make other people understand how their
computer / operating system works.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#20057

In article <bhjid6Ft0bbU1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2013-12-20, Matthew Lybanon <lybanon@earthlink.net> wrote:
> > I use Mail.app for email.  When I send image attachments, some Windows 
> > users complain that the images are "embedded" in the message body, not 
> > attachments.  Searching on the Microsoft website unearthed the 
> > information that, in Outlook, although image attachments APPEAR to be in 
> > the message body when messages are in RTF format, they are still 
> > attachments.  And Microsoft gives detailed instructions on how to get 
> > those image attachments.
> >
> > Sometimes those detailed instructions don't help.  With some people, if 
> > they can't get the images in the way they are accustomed to, NOTHING you 
> > (or MIcrosoft) tell them makes any difference.  So I have learned to 
> > choose Make Plain Text from Mail.app's Format menu, I always check the 
> > Send Windows-Friendly Attachments box, and I choose Insert Attachments 
> > at End of Message in Edit menu/Attachments.
> >
> > But even so, recently a Windows user who has AOL told me that "I got the 
> > images in the body of the email, but did not get any attachments."  Does 
> > anyone have any insight into this problem, and (even better) suggestions 
> > about how to deal with it?
> 
> IMO, it's not your responsibility to make other people understand how their
> computer / operating system works.

Depends on how much money you stand to lose because they don't ...

Isaac

[toc] | [prev] | [next] | [standalone]

#20020

In article
<lybanon-9B4621.12390820122013@70-3-168-216.pools.spcsdns.net>, Matthew
Lybanon <lybanon@earthlink.net> wrote:

> I use Mail.app for email.  When I send image attachments, some Windows 
> users complain that the images are "embedded" in the message body, not 
> attachments.  Searching on the Microsoft website unearthed the 
> information that, in Outlook, although image attachments APPEAR to be in 
> the message body when messages are in RTF format, they are still 
> attachments.  And Microsoft gives detailed instructions on how to get 
> those image attachments.

outlook is broken (no surprise there).

<http://support.microsoft.com/kb/814111>
  When you receive a message that uses the content-disposition=inline
  MIME type, Outlook renders the embedded content as an attachment.

  This behavior is by design.

if you're sending the email marked as inline and their mail client
ignores that (which outlook intentionally does), then there's not much
you can do other than tell them to stop using outlook.

> Sometimes those detailed instructions don't help.  With some people, if 
> they can't get the images in the way they are accustomed to, NOTHING you 
> (or MIcrosoft) tell them makes any difference.  So I have learned to 
> choose Make Plain Text from Mail.app's Format menu, I always check the 
> Send Windows-Friendly Attachments box, and I choose Insert Attachments 
> at End of Message in Edit menu/Attachments.
>
> But even so, recently a Windows user who has AOL told me that "I got the 
> images in the body of the email, but did not get any attachments."  Does 
> anyone have any insight into this problem, and (even better) suggestions 
> about how to deal with it?

switch to a non-broken email client. 

maybe there's a workaround, but the problem is not at your end, so you
shouldn't bother doing anything. as long as your mail is standards
complaint, you're fine.

[toc] | [prev] | [next] | [standalone]

#20022

In article <201220131417527555%nospam@nospam.invalid>,
 nospam <nospam@nospam.invalid> wrote:

> In article
> <lybanon-9B4621.12390820122013@70-3-168-216.pools.spcsdns.net>, Matthew
> Lybanon <lybanon@earthlink.net> wrote:
> 
> > I use Mail.app for email.  When I send image attachments, some Windows 
> > users complain that the images are "embedded" in the message body, not 
> > attachments.  Searching on the Microsoft website unearthed the 
> > information that, in Outlook, although image attachments APPEAR to be in 
> > the message body when messages are in RTF format, they are still 
> > attachments.  And Microsoft gives detailed instructions on how to get 
> > those image attachments.
> 
> outlook is broken (no surprise there).
> 
> <http://support.microsoft.com/kb/814111>
>   When you receive a message that uses the content-disposition=inline
>   MIME type, Outlook renders the embedded content as an attachment.
> 
>   This behavior is by design.
> 
> if you're sending the email marked as inline and their mail client
> ignores that (which outlook intentionally does), then there's not much
> you can do other than tell them to stop using outlook.

This sounds like the exact *opposite* of what the OP is reporting. He 
says he's sending non-inline attachments, and the recipients are 
complaining that they're inline.

But I question the original premise. Where in Mac Mail are you given a 
choice of whether an image should be sent as an inline or downloadable 
attachment?

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#20030

In article <barmar-D850B6.14533220122013@news.eternal-september.org>,
 Barry Margolin <barmar@alum.mit.edu> wrote:

> In article <201220131417527555%nospam@nospam.invalid>,
>  nospam <nospam@nospam.invalid> wrote:
> 
> > In article
> > <lybanon-9B4621.12390820122013@70-3-168-216.pools.spcsdns.net>, Matthew
> > Lybanon <lybanon@earthlink.net> wrote:
> > 
> > > I use Mail.app for email.  When I send image attachments, some Windows 
> > > users complain that the images are "embedded" in the message body, not 
> > > attachments.  Searching on the Microsoft website unearthed the 
> > > information that, in Outlook, although image attachments APPEAR to be in 
> > > the message body when messages are in RTF format, they are still 
> > > attachments.  And Microsoft gives detailed instructions on how to get 
> > > those image attachments.
> > 
> > outlook is broken (no surprise there).
> > 
> > <http://support.microsoft.com/kb/814111>
> >   When you receive a message that uses the content-disposition=inline
> >   MIME type, Outlook renders the embedded content as an attachment.
> > 
> >   This behavior is by design.
> > 
> > if you're sending the email marked as inline and their mail client
> > ignores that (which outlook intentionally does), then there's not much
> > you can do other than tell them to stop using outlook.
> 
> This sounds like the exact *opposite* of what the OP is reporting. He 
> says he's sending non-inline attachments, and the recipients are 
> complaining that they're inline.
> 
> But I question the original premise. Where in Mac Mail are you given a 
> choice of whether an image should be sent as an inline or downloadable 
> attachment?

I hope I've made it clear what I do:

1.  When the message composition window comes up, I choose (Format menu) 
Make Plain Text.  This is to avoid the situation that Microsoft 
describes when Outlook receives mail in RTF format:  "  € If the message 
format is Rich Text Format (RTF), attachments will appear in the body of 
the message. Even though the file appears to be embedded in the message, 
it is actually still a separate attachment."

2.  In the Edit menu, Attachments line, I have
          Always Send Windows-Friendly Attachments
               and
          Always Insert Attachments at End of Message
both checked.

That's all.  No special tricks in the preferences or elsewhere.

When I send email I am trying to convey information to someone, so I 
don't mind taking what steps I can to make it easy on the recipient.  
Yes, in an ideal world people would know how to use their computers, but 
this isn't an ideal world.*

Even so, even after doing all these things, a Windows user who uses AOL 
for email told me that "I got the images in the body of the email, but 
did not get any attachments."  I was hoping someone could help me deal 
with this (other than telling the recipient to ditch AOL and switch to 
something better).

__________
* On another occasion, I was on a committee that planned an event for an 
organization.  I designed an invitation and emailed it to another 
committee member to review.  This lady also had AOL, and had no idea 
what to do with the attachment so that she could view it.  I went to the 
AOL website and sent the lady the simple, detailed instructions I found 
there.  Sorry, that was "technical."  She had to wait for her son, who 
"knows all about computers," to come over.  Unfortunately he probably 
wouldn't be there for two weeks, and we didn't have two weeks to waste.  
Frustrating, but I had to deal with this lady.  I printed it out and 
mailed (that's mail, with an envelope and a stamp) to her, and it got 
done.

[toc] | [prev] | [next] | [standalone]

#20036

In article 
<lybanon-5C9634.16110420122013@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> 1.  When the message composition window comes up, I choose (Format menu) 
> Make Plain Text.  This is to avoid the situation that Microsoft 
> describes when Outlook receives mail in RTF format:  "  € If the message 
> format is Rich Text Format (RTF), attachments will appear in the body of 
> the message. Even though the file appears to be embedded in the message, 
> it is actually still a separate attachment."
> 
> 2.  In the Edit menu, Attachments line, I have
>           Always Send Windows-Friendly Attachments
>                and
>           Always Insert Attachments at End of Message
> both checked.
> 
> That's all.  No special tricks in the preferences or elsewhere.

None of those options imply "Send images as downloadable files rather 
than inline images".

What do you see if you look at the message source in your Sent box after 
sending it? Specifically, when you scroll down to the attachment, what 
is in the "Content-disposition:" header?

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#20070

In article <barmar-5481AA.17272720122013@news.eternal-september.org>,
 Barry Margolin <barmar@alum.mit.edu> wrote:

> In article 
> <lybanon-5C9634.16110420122013@70-3-168-216.pools.spcsdns.net>,
>  Matthew Lybanon <lybanon@earthlink.net> wrote:
> 
> > 1.  When the message composition window comes up, I choose (Format menu) 
> > Make Plain Text.  This is to avoid the situation that Microsoft 
> > describes when Outlook receives mail in RTF format:  "  € If the message 
> > format is Rich Text Format (RTF), attachments will appear in the body of 
> > the message. Even though the file appears to be embedded in the message, 
> > it is actually still a separate attachment."
> > 
> > 2.  In the Edit menu, Attachments line, I have
> >           Always Send Windows-Friendly Attachments
> >                and
> >           Always Insert Attachments at End of Message
> > both checked.
> > 
> > That's all.  No special tricks in the preferences or elsewhere.
> 
> None of those options imply "Send images as downloadable files rather 
> than inline images".
> 
> What do you see if you look at the message source in your Sent box after 
> sending it? Specifically, when you scroll down to the attachment, what 
> is in the "Content-disposition:" header?

I went back to the specific mes"sage that led to the response from the 
AOL user that I reported.  The Content-disposition:" header is

Content-Disposition: inline;
   filename=sheep_one_black_text_transp_v2.png

So despite all that I did, the attachment is inline.  I can't find 
anything in the Mail.app preferences or menus that can change that.

[toc] | [prev] | [next] | [standalone]

#20078

In article 
<lybanon-89B620.10401121122013@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> In article <barmar-5481AA.17272720122013@news.eternal-september.org>,
>  Barry Margolin <barmar@alum.mit.edu> wrote:
> 
> > In article 
> > <lybanon-5C9634.16110420122013@70-3-168-216.pools.spcsdns.net>,
> >  Matthew Lybanon <lybanon@earthlink.net> wrote:
> > 
> > > 1.  When the message composition window comes up, I choose (Format menu) 
> > > Make Plain Text.  This is to avoid the situation that Microsoft 
> > > describes when Outlook receives mail in RTF format:  "  € If the message 
> > > format is Rich Text Format (RTF), attachments will appear in the body of 
> > > the message. Even though the file appears to be embedded in the message, 
> > > it is actually still a separate attachment."
> > > 
> > > 2.  In the Edit menu, Attachments line, I have
> > >           Always Send Windows-Friendly Attachments
> > >                and
> > >           Always Insert Attachments at End of Message
> > > both checked.
> > > 
> > > That's all.  No special tricks in the preferences or elsewhere.
> > 
> > None of those options imply "Send images as downloadable files rather 
> > than inline images".
> > 
> > What do you see if you look at the message source in your Sent box after 
> > sending it? Specifically, when you scroll down to the attachment, what 
> > is in the "Content-disposition:" header?
> 
> I went back to the specific mes"sage that led to the response from the 
> AOL user that I reported.  The Content-disposition:" header is
> 
> Content-Disposition: inline;
>    filename=sheep_one_black_text_transp_v2.png
> 
> So despite all that I did, the attachment is inline.  I can't find 
> anything in the Mail.app preferences or menus that can change that.

I have no proof, but a strong suspicion, that dragging an image into an 
open mail document produces variable results (i.e. Mac users have no 
problem either way, but for PC folks it sometimes works and sometimes 
doesn't).

I have thought that if the image is dragged into the body of the message 
it goes inline, while if it is dragged below the last line it goes as an 
attachment. But I'm not sure about that.

Anyhow, I get the most reliable results when sending to PCs by using 
Menu/File/Attach files ... and being sure "Windows-friendly" is checked 
(what does that even mean?).

Most reliable of all, IME, is to ZIP the file(s) and then attach the 
ZIP. That seems to guarantee that it'll go as an attachment, and prevent 
less-than-clever mail clients from messing with it.

Isaac

[toc] | [prev] | [next] | [standalone]

#20080

In article <isw-458789.10591621122013@[216.168.3.50]>,
 isw <isw@witzend.com> wrote:

> Most reliable of all, IME, is to ZIP the file(s) and then attach the 
> ZIP. That seems to guarantee that it'll go as an attachment, and prevent 
> less-than-clever mail clients from messing with it.

I was just about the post the same suggestion, so I'll just second this.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#20110

In article <isw-458789.10591621122013@[216.168.3.50]>,
 isw <isw@witzend.com> wrote:

Š
> 
> Most reliable of all, IME, is to ZIP the file(s) and then attach the 
> ZIP. That seems to guarantee that it'll go as an attachment, and prevent 
> less-than-clever mail clients from messing with it.
> 
> Isaac

Thanks for the suggestion.  I like that idea.  It would probably work.  
The only problem is, since the people who complain "It's in the body of 
the message, not an attachment." even though it is an attachment are the 
least computer-savvy, they may not have any idea what to do with a zip 
file (or be terrified).

If anyone has any suggestions for how to prevent Mail.app from making an 
image attachment inline (since "Windows-friendly," "make plain text," 
and "Insert Attachments at End of Message" don't accomplish that), 
please pass them along.

[toc] | [prev] | [next] | [standalone]

#20114

In article
<lybanon-E4F8A7.10253122122013@70-3-168-216.pools.spcsdns.net>, Matthew
Lybanon <lybanon@earthlink.net> wrote:

> If anyone has any suggestions for how to prevent Mail.app from making an 
> image attachment inline (since "Windows-friendly," "make plain text," 
> and "Insert Attachments at End of Message" don't accomplish that), 
> please pass them along.

there's nothing you can do.

how something is displayed is up to the receiving client, not the
sending client.

you said the images are tagged as inline, so you've done all you can do.

[toc] | [prev] | [next] | [standalone]

#20129

In article <221220131402320211%nospam@nospam.invalid>,
 nospam <nospam@nospam.invalid> wrote:

> In article
> <lybanon-E4F8A7.10253122122013@70-3-168-216.pools.spcsdns.net>, Matthew
> Lybanon <lybanon@earthlink.net> wrote:
> 
> > If anyone has any suggestions for how to prevent Mail.app from making an 
> > image attachment inline (since "Windows-friendly," "make plain text," 
> > and "Insert Attachments at End of Message" don't accomplish that), 
> > please pass them along.
> 
> there's nothing you can do.
> 
> how something is displayed is up to the receiving client, not the
> sending client.
>
> you said the images are tagged as inline, so you've done all you can do.

Although that's the opposite of what he wants.

So the real question is: how can you get Mail.app to tag images as 
attachments rather than inline? It appears that there isn't any way to 
do that.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#20131

In article <barmar-F6B075.23102722122013@news.eternal-september.org>,
 Barry Margolin <barmar@alum.mit.edu> wrote:

> In article <221220131402320211%nospam@nospam.invalid>,
>  nospam <nospam@nospam.invalid> wrote:
> 
> > In article
> > <lybanon-E4F8A7.10253122122013@70-3-168-216.pools.spcsdns.net>, Matthew
> > Lybanon <lybanon@earthlink.net> wrote:
> > 
> > > If anyone has any suggestions for how to prevent Mail.app from making an 
> > > image attachment inline (since "Windows-friendly," "make plain text," 
> > > and "Insert Attachments at End of Message" don't accomplish that), 
> > > please pass them along.
> > 
> > there's nothing you can do.
> > 
> > how something is displayed is up to the receiving client, not the
> > sending client.
> >
> > you said the images are tagged as inline, so you've done all you can do.
> 
> Although that's the opposite of what he wants.
> 
> So the real question is: how can you get Mail.app to tag images as 
> attachments rather than inline? It appears that there isn't any way to 
> do that.

AFAIK, that's correct. The "implementation" of how you embed images 
(drag/drop vs. attaching via the File menu) is left to the application. 
There's now way to specify how it's done.

That's why I send stuff more and more through the Gmail web client. 
Regular text-based email is fine for Apple Mail, but I got something 
funny I want to send out to friends, I use Gmail.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]

[toc] | [prev] | [next] | [standalone]

#20124

In message <lybanon-E4F8A7.10253122122013@70-3-168-216.pools.spcsdns.net> 
  Matthew Lybanon <lybanon@earthlink.net> wrote:
> In article <isw-458789.10591621122013@[216.168.3.50]>,
>  isw <isw@witzend.com> wrote:

> Š
>> 
>> Most reliable of all, IME, is to ZIP the file(s) and then attach the 
>> ZIP. That seems to guarantee that it'll go as an attachment, and prevent 
>> less-than-clever mail clients from messing with it.
>> 
>> Isaac

> Thanks for the suggestion.  I like that idea.  It would probably work.  
> The only problem is, since the people who complain "It's in the body of 
> the message, not an attachment." even though it is an attachment are the 
> least computer-savvy, they may not have any idea what to do with a zip 
> file (or be terrified).

Then Send them a link to the file on Dropbox, Copy, Google Drive, S3, or
any of the legion of other online repositories.

> If anyone has any suggestions for how to prevent Mail.app from making an 
> image attachment inline (since "Windows-friendly," "make plain text," 
> and "Insert Attachments at End of Message" don't accomplish that), 
> please pass them along.

I stopped caring about Outlook users a long time ago.

-- 
'It's a lovely morning, lads,' he said. 'I feel like a million dollars.
Don't you?' There was a murmur of reluctant agreement.  'Good,' said
Cohen. 'Let's go and get some.' --Interesting Times

[toc] | [prev] | [next] | [standalone]

#20127

In article 
<lybanon-E4F8A7.10253122122013@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> If anyone has any suggestions for how to prevent Mail.app from making an 
> image attachment inline (since "Windows-friendly," "make plain text," 
> and "Insert Attachments at End of Message" don't accomplish that), 
> please pass them along.

I already made a suggestion that is foolproof for the most dozy of 
windoze users.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#20133

On 12-21-2013, 13:59, isw wrote:
> Most reliable of all, IME, is to ZIP the file(s) and then attach the
> ZIP. That seems to guarantee that it'll go as an attachment, and prevent
> less-than-clever mail clients from messing with it.

And allow mail clients that think they're clever to discard it because 
it "might contain malware."

-- 
Wes Groleau

    “The American Republic will endure until the day Congress discovers
     that it can bribe the public with the public’s money.”
                       — Alexis de Tocqueville

[toc] | [prev] | [next] | [standalone]

#20043

In article 
<lybanon-5C9634.16110420122013@70-3-168-216.pools.spcsdns.net>,
 Matthew Lybanon <lybanon@earthlink.net> wrote:

> When I send email I am trying to convey information to someone, so I 
> don't mind taking what steps I can to make it easy on the recipient.  
> Yes, in an ideal world people would know how to use their computers, but 
> this isn't an ideal world.*
> 
> Even so, even after doing all these things, a Windows user who uses AOL 
> for email told me that "I got the images in the body of the email, but 
> did not get any attachments."  I was hoping someone could help me deal 
> with this (other than telling the recipient to ditch AOL and switch to 
> something better).

What is the objection to the pics being in the body? That they are 
downloaded against the wishes of the recipient? That the recip[ient 
prefers to see pics in his or her own apps? If the latter, they still 
can surely drag them off from their email?

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#20046

On 12-20-2013, 17:11, Matthew Lybanon wrote:
> Even so, even after doing all these things, a Windows user who uses AOL
> for email told me that "I got the images in the body of the email, but
> did not get any attachments."  I was hoping someone could help me deal
> with this (other than telling the recipient to ditch AOL and switch to
> something better).

No guarantees, but try this:

Preferences, Composing tab.

For sending, select plain text.

For responding, turn OFF the option to copy their format.

At work, I've had Outlook on XP and Win 7 for years.  I have NEVER had 
any trouble with Mac's inline images sent to myself from home.

-- 
Wes Groleau

   “What you see and hear depends a good deal on where you are standing;
    it also depends on what kind of person you are.”
                                                       -- C.S.Lewis

[toc] | [prev] | [next] | [standalone]

#20047

On 12-20-2013, 21:28, Wes Groleau wrote:
> At work, I've had Outlook on XP and Win 7 for years.  I have NEVER had
> any trouble with Mac's inline images sent to myself from home.

If they see an image inline, AND do not see it in the attachments bar
AND are unable to find attachments in the menus, then tell them to grab 
the image and drag it to desktop.

I applaud your efforts to help people understand things, but one can 
only go so far with folks who choose to PRETEND that they are stupid.

-- 
Wes Groleau

   Nutrition for Blokes: Re-engineering your diet for life
   http://www.phlaunt.com/quentin

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.mac.apps

csiph-web