>Just prior to this, my wife's supervisor told me tonight that the >attachments started coming with the .hqx suffix on the end of the .txt >file names (thus filename.txt.hqx). Any ideas? Does .hqx mean BinHex? Why >would that be happening?
Yes, it would seem that the attachments are now being BinHexed. Verify the default encoding settings in the account setup. (or double check that you are really choosing manually AppleDouble when you send). >Today the attachments won't go through, but the text of the email does >with the following at the top of the email: > >--Emailer_-1166812974 >Content-Type: text/plain; charset="iso-8859-1" >Content-transfer-encoding: quoted-printable > >This is the error message we're getting in the log: > > ** Couldn�t complete the last command because a network stream > error occurred. Sounds like this is a SMTP server problem. If the mail server is having connection issues, it may be dropping the connection before enough of the email is sent to include the attachment. The Network Stream Error implies a dropped connection. The fact that part of the email is making thru supports that (although why it isn't disposing of the entire email I have no idea, but if the server is broken, who knows what it will do). Does your ISP have some kind of a size limit for emails? Maybe they don't allow attachments? How big of an attachment are we talking about. I would check with your ISP and see if they are having server problems. I would also double cehck that encoding setting. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
