Email Problem - Can someone tell me whats wrong?

[system]

I have a form email that sends multiple attachments. It works great and sends fine. Problem: When viewed in some User Agents (gmail, yahoo) the attachments and content don’t show up, but in Outlook 2007, hotmail, Nokia Mobile Email, all content and attachments are perfect. It is important for my clients to be able to receive these attachments no matter what email they use. Is there something wrong with the message I am sending?

[code]Headers:
From: [email protected]
Reply-To: [email protected]
Content-Type: multipart/mixed; boundary=“PHP-mixed-d45869f02bc55ebcb9126a146ee77af1”

–PHP-mixed-d45869f02bc55ebcb9126a146ee77af1
Content-Type: multipart/alternative; boundary=“PHP-alt-d45869f02bc55ebcb9126a146ee77af1”

–PHP-alt-d45869f02bc55ebcb9126a146ee77af1
Content-Type: text/plain; charset=“iso-8859-1”
Content-Transfer-Encoding: 7bit

put message here

–PHP-alt-d45869f02bc55ebcb9126a146ee77af1
Content-Type: text/html; charset=“iso-8859-1”
Content-Transfer-Encoding: 7bit

Pictures from Corkys Footwear, Inc.

put message here

–PHP-alt-d45869f02bc55ebcb9126a146ee77af1–

–PHP-mixed-d45869f02bc55ebcb9126a146ee77af1
Content-Type: image/jpg; name=“image1.jpg”
Content-Transfer-Encoding: base64
Content-Disposition: attachment

attachment

–PHP-mixed-d45869f02bc55ebcb9126a146ee77af1
–PHP-mixed-d45869f02bc55ebcb9126a146ee77af1
Content-Type: image/jpg; name=“image2.jpg”
Content-Transfer-Encoding: base64
Content-Disposition: attachment

attachment

–PHP-mixed-d45869f02bc55ebcb9126a146ee77af1–[/code]

I am reading the RFC standards on this but am not finding anything wrong.

[David]

Now I’m registered. Still not finding a solution.

[smokeys_13]

Hi there,

This problem interests me… have you tried multiple types of attachments and different files of each type (to rule out corrupted files that some clients may be better at dealing with)? In light of this I will check my PHP class that also sends multiple attachments, I don’t recall testing it with gmail or yahoo as yet…

[David]

Apparently the output buffering functions were my problem. That was is easier than writing it all as one string which is why I started with that route. But the string works.