Chris,
I have the same problem that my attachments are frequently
not able to be read by the recipient. I have been lead to believe that
it is because the receiver has an older version of the software - usually
Word and Excel. To overcome this problem I have decided the best
course of action is to use my new computer with Claris 2.2 and all the
bells and whistles of Tiger for a group I run. That is where I use
attachments more frequently. I think the way to do this is to have
a different address for that group to use but I am not sure what the
settings should be in Easy Setup. At the moment they are both set up
as follows:
Email account: earthlink
SMTP Server: adelphia
Email address: earthlink
I presume from what you say below that SMTP is for outgoing mail. I tried
changing
the Email Account and Email address to adelphia that that didn't work?
Could
this have something to do with the Account Name or User Name? Both
Earthlink
and Adelphia are both the same at the moment.
To explain, I am having reduced service from Earthlink to keep sending my
mail, but want to eventually change over to adelphia as my regular
address.
At the moment I am paying for cable service from Adelphia which means I
should be able to send and receive that way (that is, on one computer
only) ?
Hope I'm not overdoing my welcome - I am in the transition stage at the
moment with my new computer and trying to get my ducks in a row so lots
of new questions come up as I become more familiar.
Your help is most appreciated,
Bea
[EMAIL PROTECTED]
>>I have an issue with the read before and SMTP version where any
>>attachements
>>I send cannot be read by the receiving party. The attachment seems to
>>end up embeded in the mail instead of being an attachment.
>
>I assume you are talking about the hacked version of Emailer that changed
>the POP/SMTP order so it checks mail before it sends mail.
>
>Are you sure the error you are seeing doesn't also happen on an unhacked
>version of Emailer? I can't think of anything I changed in the hack that
>should effect attachments (or any other part of an email for that
>matter). I'm not saying I didn't break something else, just that off the
>top of my head, I don't see why my hack would cause the problem you are
>seeing.
>
>You can simulate the effect of the hacked version by simply running a
>regular version. Do a manual check of the email and immediately follow it
>with a send of your new email. Do that and see if the attachment problem
>still exists.
>
>Otherwise, give me more details by exactly what you mean when you say the
>attachment ends up embedded in the email.
>
>Technically, all attachments are embedded in the email. They are encoded
>into a bunch of text and markers are placed at the start and end of the
>encoded text section, then the whole lot is stuck onto the end of your
>body text when the email is sent. The receiving email client reads the
>giant body portion of the email, sees the markers denoting an attachment,
>and converts the portion between the markers back to a file, and then
>"attaches" it to the email when it adds the email to its database.
>
>So depending on what you are seeing, it could be either Emailer isn't
>putting the markers in correctly, or the receiving client isn't reading
>the markers correctly. If you can give a little more detail over what you
>are seeing happen (and who it is happening with... such as AOL users, all
>bets are off and I'll pretty much right now say it is an AOL problem...
>they live in their own world when it comes to email and they do strange
>things on a regular basis). Also, what kind of attachments is this
>happening with? If you are sending a plain text file, and you don't
>specify and encoding type (leave it as Service Default), then if Emailer
>realizes it is plain text, it may decide to attach the text to the end of
>the email instead of encoding the file. The recipient will get it as if
>you just pasted the text into the email body. Some mail clients will do
>the same thing on receipt of a file attachment that is marked as plain
>text, rather than turning it back into a file, it just removes the
>markers and leaves the text as part of the body (Emailer has been known
>to do this as well on occasion).
>
>And of course, tell me what kind of file you are sending, and what kind
>of encoding type you are using. I'm going to go out on a limb here and
>say it isn't the hacked version of Emailer that is at fault. It could be
>Emailer in general, but I'm going to guess it is going to be some
>combination of the encoding type you are using and the client the
>recipient is using.
>
>-chris
><http://www.mythtech.net>
>
>___________________________________________________________________________
>To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
><[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
>
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
