0

I send out a newsletter using a PHP based mailing list manager installed on my server, which uses phpmailer to send.

For most users that I send to, they get the newsletter fine, but users who have email accounts with cox.net , windstream.net , roadrunner.com, rr.com , earthlink.net seem to emails where the message body is blank.

X-Priority: 3
X-Mailer: PHPMailer (phpmailer.sourceforge.net) [version 2.0.4]
Errors-To: catchall@mysite.com
MIME-Version: 1.0
Content-Type: multipart/alternative;

X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.mysite.com
X-AntiAbuse: Original Domain - gmail.com
X-AntiAbuse: Originator/Caller UID/GID - [504 32007] / [47 12]
X-AntiAbuse: Sender Address Domain - host.mysite.com
X-Source: /usr/local/bin/php
X-Source-Args: /usr/local/bin/php /home/mysite/public_html/newsletters/cprocessmsgs.php 
X-Source-Dir: /home/mysite


Content-Type: text/plain; charset = ""
Content-Transfer-Encoding: 8bit

Example of Newsletter Content here




Content-Type: text/html; charset = ""
Content-Transfer-Encoding: 8bit

<html><head><meta http-equiv="Content-Type" content="text/html; charset="></head><body><html dir="ltr">
    <head>
        <title></title>
    </head>
    <body>
        <p>Example of Newsletter Content here</p>
    </body>
</html>

I sent the newsletter to myself as well and then ran the email through a MIME Email Validation tool I found online, and the tool reported the following:

Errors: linebreak found, MIME syntax violation
(line 1) linebreak found
(line 1) MIME syntax violation: header field name empty ( )
(line 40) MIME syntax violation: value expected
(line 74) MIME syntax violation: value expected

I looked at line 1 and it is blank.

Here is what is on line 40: Content-Transfer-Encoding: 8bit
Here is what is on line 74: Content-Transfer-Encoding: 8bit

Any help would be greatly appreciated.
Thx,
Brandon

2
Contributors
2
Replies
3
Views
5 Years
Discussion Span
Last Post by Brandon5150
0

Why is the charset part of all Content-Type headers empty? You should either leave the charset out and let email clients/browsers fall back on their defaults, or provide a charset. If you're not sure which charset you want to be using, UTF-8 is a good choice.

By the way, all HTML documents should have a Doctype Declaration. Even HTML emails.

0

Thanks for the reply.

I was able to correct the "charset" issue. It is now set to UTF-8

Edited by Brandon5150: found how to set it

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.