Email function spits out garbage

[kilbey1]

I've got a little e-mail function working, except when the attachment comes to me, it appears as if 'encoded' as so:

CioqKioqKjA3LzI2LzA2IDI6MTg6NDAgYW0qKioqKioKQXJyYXlUQUJMRTogbGlzdGluZ3NDSUIK
CkFycmF5VEFCTEU6IGxpc3RpbmdzQ0lCCgpUQUJMRTogbGlzdGluZ3NGQUwKCkFycmF5VEFCTEU6
IGxpc3RpbmdzQ0lCCgpUQUJMRTogbGlzdGluZ3NGQUwKCkluc2VydCBmYWlsZWQ6CklOU0VSVCBJ
TlRPIGxpc3RpbmdzRkFMKGBPZmZpY2VgLGBPZmZpY2VOYW1lYCxgTGlzdE51bWAsYEFkZHJlc3NO
dW1gLGBBZGRyZXNzRGlyZWN0aW9uYCxgU3RyZWV0YCxgUHJpY2VgLGBTdHNgLGBDb3VudHlgLGBB
cmVhYCxgQWNjZXNzMWAsYEFjY2VzczJgLGBBY3Jlc2AsYEFzc2Vzc21lbnRWYWx1ZWAsYEJhdGhz

Can someone help me to spot my error? I'm not seeing it and I've been coding like mad for hours straight, so it may be a really stupid error. Not to mention that it worked before!

function senderroremail() {

$logfile = $GLOBALS['strLogFile'];
global $logdir, $time;

$log = $logdir . $logfile;

//size limit of log in BYTES.
// This is here so we don't send out an attachment that will bog down a mail server.
$logsizelimit = "3145728";

//echo $log;

$to = "[e-mail]";
$from = "me <[e-mail]>";
$subject = "Error log attached.";

if(filesize($log) < $logsizelimit) {
	$body = "Error log attached.\n";
} else {
	$body = "Error log exceeds $logsizelimit. ";
}	
$body .= "\n\nRealty World Webmaster\n";

$fp = fopen( $log, "r");
$file = fread( $fp, filesize($log) );

/*
Encode The Data For Transition using base64_encode();
And get a 32-character hexadecimal number
*/
$file = chunk_split(base64_encode($file));
$num = md5( time() );

/*
Define the main message headers
*/
$hdr  = "From:".$from."\r\n";
$hdr .= "MIME-Version: 1.0\r\n";
$hdr .= "Content-Type: multipart/mixed; ";
$hdr .= "boundary=".$num."\r\n";
$hdr .= "--$num\r\n";

/*
Define message section
*/
$hdr .= "Content-Type: text/plain\r\n";
$hdr .= "Content-Transfer-Encoding: 8bit\r\n\n";
//$hdr .= "".$_REQUEST['comments']."\r\n";
$hdr .= "--".$num."\n";

/*
Define the attachment section
*/

//Only include attachment if it's less than the log size limit
if(filesize($log) < $logsizelimit) {	
	$hdr .= "Content-Type:". filetype($log)." ";
	$hdr .= "name=\"".$logfile."\"r\n";
	$hdr .= "Content-Transfer-Encoding: base64\r\n";
	$hdr .= "Content-Disposition: attachment; ";
	$hdr .= "filename=\"".$logfile."\"\r\n\n";
	$hdr .= "".$file."\r\n";
	$hdr .= "--".$num."--";
}

/*
Send the email
*/
mail( $to, $subject, $body, $hdr);

/*
Close the attachment
*/
fclose( $fp );
//echo "Mail sent...";

}

[bogu]

When adding attachments to the message body on a Windows system, always open the file using the binary flag option i.e. fopen("filename","rb").
If you don't then any non text attachments will be unreadable when the email is received. The binary flag is ignored if not required so it does no harm to always include it in these circumstances.

[kilbey1]

Hi! The flle attachment and e-mail process are taking place on a Unix system. Would this still apply?

Also, the attachments being sent are always in .txt format.

[Weedpacket]

Binary attachments are always encoded as text when sent by email: email is a text-only format and so can't handle raw binary (and encoding makes the format more predictable). base64 is the most common encoding, and running your sample through base64_decode() nets me this:

******07/26/06 2:18:40 am******
ArrayTABLE: listingsCIB

ArrayTABLE: listingsCIB

TABLE: listingsFAL

ArrayTABLE: listingsCIB

TABLE: listingsFAL

Insert failed:
INSERT INTO listingsFAL(`Office`,`OfficeName`,`ListNum`,`AddressNum`,`AddressDi
ection`,`Street`,`Price`,`Sts`,`County`,`Area`,`Access1`,`Access2`,`Acres`,`Ass
ssmentValue`,`Baths

In short; you want to look at the bit in your code that says

/*
Encode The Data For Transition using base64_encode();
And get a 32-character hexadecimal number
*/
$file = chunk_split(base64_encode($file));
$num = md5( time() ); 

[kilbey1]

Thanks to both of you. I revised the code entirely, making sure that the MIME encoding was tighter. It now works - at least when I send it to my Yahoo address, but looks strange when sent through my Comcast address. Same e-mail client.

While the Yahoo account comes out with the text attachment and a body, the Comcast account presents it thusly in the body of the mailer. My guess is I'm missing something that Comcast requires when processing e-mail.

Content-Type: multipart/related; type="multipart/alternative"; boundary="----=MIME_BOUNDRY_main_message"
X-Sender: <>
X-Mailer: PHP4
X-Priority: 3
Message-Id: <[e-mail]>
Date: Wed, 26 Jul 2006 11:32:07 -0400 (EDT)

This is a multi-part message in MIME format.
------=MIME_BOUNDRY_main_message 
Content-Type: multipart/alternative; boundary="----=MIME_BOUNDRY_message_parts"


------=MIME_BOUNDRY_message_parts
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


 Hello,


Error log attached.


Realty World Webmaster


------=MIME_BOUNDRY_message_parts--

------=MIME_BOUNDRY_main_message
Content-Type: application/octet-stream;
	name="uploadData.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="uploadData.txt"

CioqKioqKjA3LzI2LzA2IDExOjMyOjA1IGFtKioqKioqClRBQkxFOiBsaXN0aW5nc0NJQgoKSW5z

ZXJ0IHN0YXRlbWVudCByYW4gc3VjY2Vzc2Z1bGx5IGZvciBhbGwgZGF0YSBvbiB0YWJsZSBsaXN0

aW5nc0NJQi4KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t

------=MIME_BOUNDRY_main_message--