abqdavid;10996758 wrote:The "template code" does send the email and data.
No it doesn't - it just defines some template. That template itself doesn't actually do anything - something else has to parse that template and actually do the sending of the e-mail.
abqdavid;10996758 wrote:Several people posted how they spoke with ComCast tech support who said they block PHP email() Function.
Two possibilities come to mind:
The support rep was talking about hosted websites using Comcast to send mail, in other words they're saying that you can't run a website on their servers and use PHP's mail() command to send mail.
The support rep had no idea what he/she was talking about. (No surprise here given the number of "technical support representatives" which are really nothing more than idiots reading from a prompt and clicking Yes/No response buttons. 😉)
abqdavid;10996758 wrote:If the email is going through to other accounts, I would assume the problem is not on my end? Am I assuming wrong here?
Just because you've managed to get through the spam filters of one domain doesn't mean you're guaranteed to do the same for the filters of another domain. In fact, it doesn't even mean you'll get through those same filters tomorrow or next week.
Like I said, I would try to figure out why your e-mails are getting blocked by Comcast. See if Comcast is providing "bounce" messages that explain why the message was rejected, or perhaps see if Comcast support would be willing to investigate why your messages are getting blocked.
Without seeing the actual PHP code (not template text which, again, doesn't do anything at all) that sends the e-mail, I can only throw out random suggestions, such as:
Don't use user-supplied e-mail address in the 'From' header, or, if you do, supply an e-mail address on the domain from which you are sending the e-mails in the form of a 'Sender' header.
Try to send an e-mail to yourself so that you can view the raw headers of the message. Post those headers here for us to see.
Make sure your message doesn't "look" like spam by ensuring all of the most common e-mail headers are set, such as: MIME-Version, Content-Type, Content-Encoding, Reply-To (optional).
Make sure your domain has a valid SPF record that permits your outgoing mail server to send mail on behalf of your domain. Creating a record for a domain that does not have one at all can also help improve your chances of making it past spam filters.
EDIT: Also forgot...
[indent]5. Make sure your domain isn't on any RBLs (here is one place to do this).[/indent]