Brendon Boshell

Yes, the plugin did create a post and comment. It does this in order to generate message previews — the plugin needs to create a ‘psuedo’ comment/post, to allow shortcodes to access a comment and generate a preview.

The post has a custom post type which ensures it will not show up on the front end of your blog.

Which version of outlook are you using? I tried with Outlook 2007 but could not replicate the issue.

I am aware of the issues with the CAN-SPAM act in the U.S. and some EU directives here, and will be trying to resolve this in the next release 3.1.

It should do, yes. Let me know if there are any issues.

It should work with pages, yes. Let me know if you have any issues with this.

I’m unable to replicate this issue so I cannot be certain what the problem is. But I do have a hunch that it’s something to do with line endings that are used, which would depend on which SMTP server you are using. Would it be possible for you to test the latest trunk version (download here) and report back if that fixes the issue. If it does, then I have a fix in mind.

What message are you using? Are there spaces inside the words or equals (‘=’) signs? Does this affect a specific email client (Google Mail, Thunderbird, etc) or does it appear a problem in everything you have tried?

If possible, could you post of a copy of the message source (View->Message Source from Thunderbird).

Oh, it seems that Outlook doesn’t save a copy of the original email, only the processed version.

I have replicated this issue before. I believe it was due to the mail server changing the Content-Transfer-Encoding header from quoted-printable to something else, without actually re-encoding the content. I put it down to a mis-configured mail server at the time, but I will try to find where this problem actually lies since I suspect this affects a few people.

I’ll keep you updated on this thread.

Thanks, but you should also have headers for each individual part of the message. It will be written --b1_81d2f25d141f4967d23909349e380e43 on its own line, followed by the part-specific headers. Do you have these?

When you view source, what are the headers for each part set at? It will look something like this:

–b1_11bedac19602c2f06169d0d41c427f54
Content-Type: text/plain; charset = “UTF-8”
Content-Transfer-Encoding: quoted-printable

It will appear twice — once for text/plain and once for text/html.

1. Is the HTML in the email parsed? I assume what you have posted is the source of the email, rather than what the email actually displays as in your email client?
2. Which mail server are your using (as sender)? Or, who hosts your mail server?
3. Which email client is the recipient using to view the email?

Okay, I’m not sure why you are seeing this problem since, as far as I can see, the logic is identical to that in 3.0.3 for sending emails. Unless somebody else has this issue, I recommend you stick with 3.0.3. With 100 plugins, it’s reasonable that there is a conflict somewhere. Since disabling your plugins produces a 404, it seems you setup is quite fragile anyway.

1. Does the problem occur when you disable all other plugins?
2. After upgrading, could you disable the plugin and then re-enable it. Does this fix the problem?

Could you please try 3.0.6 and see if that resolves the issue. I have reworked some code to make it more efficient and use less memory. Hopefully, this will fix the problem.

What did you change your theme to?