On Jan 23, 2007, at 11:40 AM, Tannis Baker wrote:
Hmmm - I definitely and positively attached 4 scripts. Not knowing
how
Mail deals with attachments I cannot suggest where to look for them
- and
can't imagine why they would not have been downloaded along with the
message body.
Did you send the attachments direct to Bill, or did you send them to
the list? The list server strips attachments from all emails, so if
sent via the list, the attachments will "vanish".
How does Mail usually deal with attachments that are not sent as
part of
the message body?
Technically no attachment is part of a message body (its all about
the MIME sections and the body text has its own section, and then
each attachment has its own section), but regardless, Mail does one
of two things, based on the way the email is formatted. It either
displays the attachment inline (for formatted emails that carry the
correct info), or just shows icons at the bottom of the message body
text for each attachment (for plain text emails, or formatted ones
that don't carry correct inline info).
In addition, in the header area, there will be a place showing how
many attachments there are, and an option to save them all to file,
so even if they aren't showing up in the body somewhere, check the
header area to be sure they really aren't there.
Finally, if you were sending Applescripts, and you didn't compress
them first, and you used a non Mac friendly encoding method (such as
Base64), then the attachments will be empty files, and Mail may have
just thrown away the references to zero length files. Applescripts
prior to later versions of OS X where entirely stored in the resource
fork of the file, so Base64, which acts only on the data fork, would
find nothing to encode and would attach a zero length file instead of
the actual applescript.
If you are going to send Applescripts, or any other Mac specific
file, via email, you MUST either compress the file first (thus
"flattening" it and moving all the information to the data fork), or
you MUST use a Mac friendly encoding method such as AppleDouble,
AppleSingle, BinHex, or MacBinary. If you have the choice, go with
AppleDouble as it just Base64 run on both the data and resource fork
halves of the file, which means it has the highest chance of getting
thru filtering systems in one piece (anything that can read Base64,
which is pretty much EVERYTHING dealing with email, can read
AppleDouble, if it doesn't know specifically what AppleDouble is, it
will just treat it as two Base64 attached files).
-chris
<www.mythtech.net>
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
