Please scroll down to my response to Chris' answer made Re:
Emailer & 10.4.11
(Some of the content of this Digest has been deleted)
>----------------------------------------------------------------------
>emailer-digest Digest Volume 2008 : Issue 10
>
>Today's Topics:
> Re: bum attachement causes [ "M. A. Nezami"
><[EMAIL PROTECTED]> ]
> Re: Emailer & 10.4.11... [ "H. Halverson"
><[EMAIL PROTECTED] ]
> Re: Emailer & 10.4.11... [ [EMAIL PROTECTED] ]
> Re: bum attachement causes [ Bill Williams
><[EMAIL PROTECTED]> ]
> Re: Emailer & 10.4.11... [ cb <[EMAIL PROTECTED]> ]
>>
>------------------------------
>
>Date: Tue, 22 Apr 2008 18:34:11 -0700
>From: "H. Halverson" <[EMAIL PROTECTED]>
>Subject: Re: Emailer & 10.4.11...
>
>
>>Wondering if anyone who's already updated has had particular problems
>>with Classic or Emailer on 10.4.11?
>
>I have a G5 Quad running 10.4.11. In fact, I've run CE with OS10.2 and
>10.3 under classic with generally no big problems.
>
>But....of late I have an intermittant and seemingly random problem where
>recpiants get the email but it only has part of the content in the body
>of the email. It was as if part of the email gets "cut off" during
>transmission.
>
>I haven't been able to fix that.
>
>
>cYa
>Hib Halverson =95
>
>
>
>------------------------------
>
>Date: Tue, 22 Apr 2008 21:58:34 EDT
>From: [EMAIL PROTECTED]
>Subject: Re: Emailer & 10.4.11...
>
>
>I have had problems recently with this version of emailer and Mac OS...
>Emailer will get stuck at: Checking Password
>That's even when there are incoming emails. The only solution I have
>found is to quit Emailer and relaunch it followed by doing a Connect Now.
>Sometimes I have to repeat this procedure seven or eight times until it
>finally succeeds in connecting. The actual number of repetitions seems
>random. If it connects successfully one time, it will do so every time
>after that (other than the longtime reading 1 of 0 problem when there's
>nothing to read).
>
>I don't think the latest problem is the fault of 10.4.11, as emailer ran
>fine a few months ago.
>
>Anyone have any clues?
>
>Charlie Stillman
>------------------------------
>
>Date: Wed, 23 Apr 2008 15:44:05 -0400
>From: Bill Williams <[EMAIL PROTECTED]>
>Subject: Re: bum attachement causes
>
>
>In emailer Digest V2008 #9, the person identified as Dan K
><[EMAIL PROTECTED]> thoughtfully said:
>
>>Hi, ye remaining [EMAIL PROTECTED] users,
>>
>>Just wondered if anyone had seen this (from my connection log) before:
>>
>> ** A part of the MIME encoded message =B3<MailID: 81322> CMS 1500 Claim
>>Form=B2 could not be extracted because an unknown error (-120) occurred.
>>The entire message is included.
>>
>> ** Couldn=B9t complete the last command because an unknown error (-120)
>>occurred.
>>
>>My insurance co. tried to send a claim form PDF file attached to an email=
>>(twice!!), but all I got was the above. In fact, now every time I get any=
>>new mail I get the above error message (twice!!)
>
>Don't think I've had a PDF attachment for [EMAIL PROTECTED] to deal with, but
>if/when this happens I'd just use WebMail to get the message and
>attachment. Seems like I =3Dhave=3D seen the unknown error (-120) on
>occasion, but don't recall the reasons.
>>
>>I can't seem to get rid of the pesky thing. The actual mail doesn't show
>>up in my in box (nor anywhere else I can see) so I haven't any idea how
>>to get rid of it.
>
>Chris probably has the answer for this. Have you used WebMail to delete
>the original from your ISPs server so [EMAIL PROTECTED] doesn't keep trying to
>download it?
>
>
>
>Selah!
>BWms
>Subject: Re: Emailer & 10.4.11...
>
>
>On Apr 22, 2008, at 9:34 PM, H. Halverson wrote:
>
>> But....of late I have an intermittant and seemingly random problem
>> where
>> recpiants get the email but it only has part of the content in the
>> body
>> of the email. It was as if part of the email gets "cut off" during
>> transmission.
>
>
>I used to see that as well. I *think* I finally tracked it to an odd
>issue of line wrapping an where it broke in relation to the end of a
>sentence. What happens is, you write your email, and if you are like
>me, you insert blank lines between paragraphs (which based off your
>email, this appears to be the case).
>
>Emailer then wraps the lines as needed when sending the data to the
>mail server. If the wrap happens to flow to a point where the period
>for the end of your sentence/paragraph is wrapped as the only
>character on a line, then that is seen by the server as the end of
>the email (the end of data marker is CRLF . CRLF, or exactly what is
>sent to put a period on a line all by itself).
///////////////////////////////////////////////////////////////////////////
////////
Sheafe Ewing responds beginning here:
Well, this random clipping is something I noticed a long while ago.
It would bug me to have people send me back, my message, which
was broken up . It occurred with regularity also with other earlier
versions of OS 9, OS X, etc.
I asked about this (I think) here, and was told that Emailer wraps
messages at 70 spaces. So I adapted my composition of mails and
to manually Return at about 70, as I composed. This seems to
have worked well for me.
And, when I have a something lengthy.... perhaps something I copy
and want to include...... something which obviously has lines which
are longer, and I want to tidy everything up so as to avoid clipping,
then I use TextSoap.... which is more trouble than most people
want to go to, but assures me that the text gets cleaned up to
look (initially at least) the way I want it to look.
TextSoap is a handy little application for just such purpose.
>
>As for fixing it, I never did "fix" it for me, I just accepted it as
>an annoying occasional event. However, I do seem to recall someone
>had an applescript that would pre-wrap an email and make sure a
>period was not on a line by itself. This script may be on Fog City's
>web site.
>
>-chris
><www.mythtech.net>
Sheafe Ewing
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
