We use cookies to help make our site work properly and to analyze how our site is used. Some are optional, but none contain your personal information, and we don't use any for ads. You can view our cookies policy, manage your cookie preferences, or consent and dismiss this banner by clicking agree:

Agree
ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

MIME email after 1.7.1 upgrade

November 19, 2011 8:36am

Subscribe [3]

  • #1 / Nov 19, 2011 8:36am

    DeeCee

    118 posts

    This question may be related to a resolved thread.

    I upgraded to 1.7.1 from 1.6.9 last week and I am getting the same problem as above thread.

    I DO have <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>  in my HTML.

    I am using SENDMAIL as the email protocol and HTML as the email formatting.  My only addon is FreeForm.

    I tested with
    <html>
    <head>
    </head>
    as suggested in a previous thread and that did not work.

    I saw in a previous thread that this was a known bug in 1.7.0 and was suppose to be fixed in 1.7.1, but it does not look like it is fixed.


    X-Mailer: ExpressionEngine 1.7.1
    X-Priority: 3 (Normal)
    Message-ID: <[email protected]>
    Mime-Version: 1.0
    Content-Type: multipart/alternative; boundary=“B_ALT_4ec7b568c18f5”

    This is a multi-part message in MIME format.
    Your email application may not support this format.

    —B_ALT_4ec7b568c18f5
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

  • #2 / Nov 21, 2011 11:40am

    DeeCee

    118 posts

    I believe that this should be listed as a bug -

    When I resend an email that was created in EE1 and converted to EE2, the email is distorted and skewed.  When I recreate the email fresh by populating the the Message field with the html then send, it works fine.

  • #3 / Nov 21, 2011 2:02pm

    Dan Decker

    7338 posts

    Hi deecee,

    Using my local install of ExpressionEngine 1.7.1 and the following:

    <html>
<head><title>Test Email</title></head>
<body>
<h1>This is a test message</h1>

Mauris iaculis porttitor posuere. Praesent id metus massa, ut blandit odio.=
 Proin quis tortor orci. Etiam at risus et justo dignissim congue. Donec co=
ngue lacinia dui, a porttitor lectus condimentum laoreet. Nunc eu ullamcorp=
er orci. Quisque eget odio ac lectus vestibulum faucibus eget in metus. In =
pellentesque faucibus vestibulum. Nulla at nulla justo, eget luctus tortor.=
 Nulla facilisi. Duis aliquet egestas purus in blandit. Curabitur vulputate=
, ligula lacinia scelerisque tempor, lacus lacus ornare ante, ac egestas es=
t urna sit amet arcu. Class aptent taciti sociosqu ad litora torquent per c=
onubia nostra, per inceptos himenaeos. Sed molestie augue sit amet leo cons=
equat posuere. Vestibulum ante ipsum primis in faucibus orci luctus.


<b>Thank you!</b>
</body>
</html>

    I was able to successfully send html email using Sendmail and PHP Mail.

    If I understand you correctly, this was working fine before the upgrade? What is the result if your try using PHP Mail vs. Sendmail? Admin-> System Preferences-> Email Configuration

    Thanks!

     

  • #4 / Nov 21, 2011 2:39pm

    DeeCee

    118 posts

    Thanks for the quick reply, Dan.

    I should have specified that the messages that I was sending were resends of a messages built in 1.6.9 sent from the 1.7.1 Previously Sent email tab.  I just tested building the email from scratch and sending it, then I resent it, and both worked fine. 

    I can work around this issue, but there appears to be an issue in the upgrade process. 

    FYI - I am testing EE2.3.1 and found the same issue.  A resend of a EE1.6.9 message was all skewed (but it was HTML not MIME), but sending a ‘fresh’ EE2.3.1 message was ok.

    Perhaps there should be a note in the upgrade procedure not to plan to resend old messages with the new versions?

  • #5 / Nov 22, 2011 6:00am

    John Henry Donovan

    12339 posts

    Hi deecee,

    How do you mean converted? Do you mean an upgraded site?
    What version of EE1.x did you upgrade from?
    What version of EE2.x are you now currently on?

    Can you explain what you mean by distorted and skewed? Perhaps provide a screenshot?
    Do you get any errors?

  • #6 / Nov 22, 2011 7:01am

    DeeCee

    118 posts

    Hi, John! yes when I said converted, I meant upgrade.  Here is the process I went through with screen shots at each step.  If you need me to forward the actual email to you, I can.  The web version of the email is here: http://copingmag.com/cwc/eupdate/2011_Nov_15.html

    (sorry, how to I include a screenshot? zapgrab nor copy/paste seem to work)

    1. EE 1.6.9 - this is where the original email was created, sent for review and resent for the masses.  Everything looks good!

    2. Upgraded EE 1.6.9 to EE 1.7.1 - when I resend the Nov_15 email, I get:  (something seem to be missing in the first line - should be Coping with Cancer, not just Cancer)
    <pre><code>
    Cancer
    Reply-To: “[email protected]” <[email protected]>
    X-Sender: .(JavaScript must be enabled to view this email address)
    X-Mailer: ExpressionEngine 1.7.1
    X-Priority: 3 (Normal)
    Message-ID: <[email protected]>
    Mime-Version: 1.0
    Content-Type: multipart/alternative; boundary=“B_ALT_4ec7ab7500879”

    This is a multi-part message in MIME format.
    Your email application may not support this format.

    —B_ALT_4ec7ab7500879
    Content-Type: text/plain; charset=utf-8 <pre><code>

    3. I built a test directory/database using the EE 1.7.1 and tested to make sure everything was in sync. Then I upgraded the test from EE 1.7.1 to EE 2.3.1.  When I resent the Nov 15 email, for instance, there is a big gap at the top and the diamonds do not line up (lots of other format issues, too):
    In This eUpdate:
      ♦ The Role of Spirituality in Cancer Care
      ♦ Caring for a Loved One with Cancer
        ♦ What I Learned the First Five Years
        ♦ Cancer Therapy and Your Fertility

    4. Then it occurred to me that is was the upgrade process, so I recreated the email from code and sent then resent both in the EE 1.7.1 production directory and in the EE 2.3.1 test directory and they both seem fine.

    Therefore, my conclusion is that the database of existing emails did not upgrade correctly from 1.6.9 to 1.7.1 then something else happened between 1.7.1 and 2.3.1.  I can live without resending old emails (I can recreate from code if I need them), but I think it should be documented if it is a problem.

    Let me know how to create screenshots or if you want copies of the email forwarded to you!

  • #7 / Nov 22, 2011 4:45pm

    Dan Decker

    7338 posts

    Hi deecee,

    I know it doesn’t help your situation much, but I will bring this up to the Devs so that they are aware and can take it into account for future updates. I’m not sure if it is a bug, or just something they overlooked in the update process. With that in mind, is there anything else I can do to help you?

    Thanks!

  • #8 / Nov 23, 2011 4:11pm

    Dan Decker

    7338 posts

    Hi deecee,

    I merged your 2 threads, since they are conceding the exact same issue. I have brought this up to the developers and they do agree that it sounds like a bug. I have filed a bug report on your behalf. You can comment on that report to be notified of any progress or solutions that may come of it.

    With that in mind, is there anything else I can do to help you?

    Thanks!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases

© Packet Tide, All Rights Reserved. Legal Notices

Username

Password

Forgot password?
or Register