>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]>
