Menu ▾ ▴

NO PLAIN TEXT MESSAGE BODY FOUND

Help
Travis Baseflug
2010-10-28
2014-04-04

  • Travis Baseflug

    Travis Baseflug - 2010-10-28

    I am sending a HTML email to my windows service - evey email that comes in says "NO PLAIN TEXT MESSAGE BODY FOUND " and the original is attached (html email) - why?  Shouldnt I be able to read encoded html emails?

     

  • Corey Trager

    Corey Trager - 2010-10-28

    By design, I don't show the html emails because there's not a way to do that safely, easily.    Click on "view images inline" to see them in iframes.

     

  • Travis Baseflug

    Travis Baseflug - 2010-10-28

    The weird thing is that at some point - the email was coming over with at least the comment/email body stripped of HTML tags and the original html email attached as text.html - not it is just bypassing the html strip process and attaching it.  Or in some cases - it is including the html in the email body just not decoded…  Just a bunch of html in the body of the email notice and in the comment field…

     

  • Corey Trager

    Corey Trager - 2010-10-28

    btnet_service_exe.config has a setting for capturing the raw text of an incoming message and dumping it to a file:  "MessageOutputFile".    The file is what I need to see to investigate the problem.

     

  • Dong

    Dong - 2010-11-05

    Same problem with this message:

    +OK
    Received: from mx01.solcon.nl () by ms1.gvdongen.local with Microsoft SMTPSVC(6.0.3790.4675);
    Fri, 5 Nov 2010 15:20:39 +0100
    Received: from  (helo=mailrbl02.solcon.nl)
    by mx01.solcon.nl with esmtp (Exim 4.69)
    (envelope-from <helpdesk@artsystems.nl>)
    id 1PEN9m-0003yE-Dx
    for helpdesk@vandongen.eu; Fri, 05 Nov 2010 15:20:42 +0100
    Received: from  (helo=mail-ww0-f46.google.com)
    by mailrbl02.solcon.nl with esmtp (Exim 4.71)
    (envelope-from <helpdesk@artsystems.nl>)
    id 1PEN9l-0000GS-DT
    for helpdesk@vandongen.eu; Fri, 05 Nov 2010 15:20:41 +0100
    Received: by wwd20 with SMTP id 20so3595663wwd.27
            for <helpdesk@vandongen.eu>; Fri, 05 Nov 2010 07:20:41 -0700 (PDT)
    Received: by 10.216.70.8 with SMTP id o8mr1138582wed.24.1288966841563;
            Fri, 05 Nov 2010 07:20:41 -0700 (PDT)
    Received: from SBEHEER (D4B27342.static.ziggozakelijk.nl )
            by mx.google.com with ESMTPS id x23sm864021weq.10.2010.11.05.07.20.40
            (version=TLSv1/SSLv3 cipher=RC4-MD5);
            Fri, 05 Nov 2010 07:20:40 -0700 (PDT)
    Message-ID: <4cd412b8.17edd80a.2944.37a2@mx.google.com>
    Sensitivity: Normal
    Importance: Normal
    MIME-Version: 1.0
    From: Helpdesk Art Systems <helpdesk@artsystems.nl>
    To: helpdesk@vandongen.eu
    Reply-To: Helpdesk@artsystems.nl
    Date: Fri, 05 Nov 2010 07:20:40 -0700 (PDT)
    Subject: RE:berekening niet goed, schrijft Duitse km, niet geweest ?????????????
    (CALLNR:3447) (DO NOT EDIT THIS:20003)
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: base64
    X-SPAMSCORE: Hits by Solcon spam-filter: 2.8 points by spam03
    pts rule name              description
    -- --------------- ---------------------------------
    0.1 RDNS_NONE              Delivered to trusted network by a host with no rDNS
    0.0 HTML_MESSAGE           BODY: HTML included in message
    1.7 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts
    1.1 HTML_MIME_NO_HTML_TAG  HTML-only message, but there is no HTML tag
    Return-Path: helpdesk@artsystems.nl
    X-OriginalArrivalTime: 05 Nov 2010 14:20:39.0375 (UTC) FILETIME=

    QmVzdGUgQXJqZW4sPGJyPjxicj5IZXQgYmVyZWtlbmVuIHZhbiBkZSByaXR0ZW4gd29yZCBp
    biBkZSB2b2xnZW5kZSB1cGRhdGUgYWFuZ2VwYXN0Ljxicj48YnI+Uml0bnIgMTc3NzIgaGVi
    IGlrIHpvanVpc3QgaGFuZG1hdGlnIG9wbmlldXcgYmVyZWtlbmQgZW4gaXMgbnUgZ29lZC48
    YnI+PGRpdj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiBzbWFsbDsiPjxmb250IGZhY2U9InRh
    aG9tYSI+TWV0IHZyaWVuZGVsaWprZSBncm9ldCw8L2ZvbnQ+PC9zcGFuPjwvZGl2PjxkaXY+
    PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogc21hbGw7Ij48Zm9udCBmYWNlPSJ0YWhvbWEiPiZu
    YnNwOzwvZm9udD48L3NwYW4+PC9kaXY+PGRpdj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiBz
    bWFsbDsiPjxmb250IGZhY2U9InRhaG9tYSI+R2VyYnJhbmQgTGVuc2VuPC9mb250Pjwvc3Bh
    bj48L2Rpdj48ZGl2PjxzcGFuIHN0eWxlPSJmb250LXNpemU6IHNtYWxsOyI+PGZvbnQgZmFj
    ZT0idGFob21hIj5BcnQgU3lzdGVtczwvZm9udD48L3NwYW4+PC9kaXY+PGRpdj48c3BhbiBz
    dHlsZT0iZm9udC1zaXplOiBzbWFsbDsiPjxmb250IGZhY2U9InRhaG9tYSI+aGVscGRlc2tA
    YXJ0c3lzdGVtcy5ubDwvZm9udD48L3NwYW4+PC9kaXY+PGRpdj48c3BhbiBzdHlsZT0iZm9u
    dC1zaXplOiBzbWFsbDsiPjxmb250IGZhY2U9InRhaG9tYSI+VGVsLiAwNTAtNTQ0NTEwNTwv
    Zm9udD48L3NwYW4+PC9kaXY+PGRpdj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiBzbWFsbDsi
    Pjxmb250IGZhY2U9InRhaG9tYSI+RmF4LiAwNTAtNTQ0NTEwNDwvZm9udD48L3NwYW4+PC9k
    aXY+PGJyPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJy
    PkJpaiZuYnNwO3JpdCZuYnNwOzE3NzcyJm5ic3A7KGJlZHJpamYmbmJzcDsxKSZuYnNwO3dv
    cmRlbiZuYnNwO2VyJm5ic3A7ZHVpdHNlJm5ic3A7dG9sa29zdGVuJm5ic3A7bWVlZ2Vub21l
    bi4mbmJzcDtEaXQ8YnI+dGVyd2lqbCZuYnNwO2RlJm5ic3A7cml0Jm5ic3A7bmlldCZuYnNw
    O2Rvb3ImbmJzcDtkdWl0c2xhbmQmbmJzcDtsb29wdC48YnI+PGJyPjxicj5NZXQmbmJzcDt2
    cmllbmRlbGlqa2UmbmJzcDtncm9ldGVuLDxicj48YnI+QXJqZW4mbmJzcDt2YW4mbmJzcDtE
    b25nZW48YnI+PGJyPklUJm5ic3A7VmFuJm5ic3A7RG9uZ2VuJm5ic3A7VHJhbnNwb3J0Jm5i
    c3A7Qi5WLjxicj5EaXJrc2xhbmQ8YnI+d3d3LnZhbmRvbmdlbi5ldTxicj48YnI+KioqJm5i
    c3A7R3JhYWcmbmJzcDtoZXQmbmJzcDtjYWxsbnVtbWVyJm5ic3A7dWl0Jm5ic3A7ZGUmbmJz
    cDtvbmRlcndlcnBzdGVrc3QmbmJzcDt2YW4mbmJzcDtkaXQmbmJzcDtiZXJpY2h0PGJyPm92
    ZXJuZW1lbiZuYnNwO2JpaiZuYnNwO3ZlcmRlcmUmbmJzcDtjb21tdW5pY2F0aWUmbmJzcDti
    ZXRyZWZmZW5kZSZuYnNwO2RpdCZuYnNwO29uZGVyd2VycC4mbmJzcDsqKio8YnI+PGJyPioq
    KiZuYnNwO1BsZWFzZSZuYnNwO3Rha2UmbmJzcDtvdmVyJm5ic3A7dGhlJm5ic3A7Y2FsbG51
    bWJlciZuYnNwO2Zyb20mbmJzcDtzdWJqZWN0Jm5ic3A7ZmllbGQmbmJzcDtvZiZuYnNwO3Ro
    aXMmbmJzcDttZXNzYWdlLDxicj5hdCZuYnNwO2Z1cnRoZXImbmJzcDtjb21tdW5pY2F0aW9u
    Jm5ic3A7Y29uY2VybmluZyZuYnNwO3RoaXMmbmJzcDtzdWJqZWN0LiZuYnNwOyoqKjxicj48
    YnI+

    +OK

     

  • Corey Trager

    Corey Trager - 2010-11-06

    By design.    If there's a text/plain part, I show that inline.    If there is a text/html part, I treat it like an attachment.    If you click on "show images inline", I show the html in iframes.    It takes a lot of logic to make the html payload of an email safe enough to display inline.    What gmail and yahoo mail do is not easy.

     

  • Steve Lindley

    Steve Lindley - 2010-12-21

    I had the same problem after installing SP3 rolloup 1 on Exchange 2007.  Check out these aritcles to fix it (this update changes the retrieval behavior settings, which causes this problem).  After changing my POP3 Retrieval Behavior settings to "HTML and alternate text," then restarting the POP3 service, everything worked again.

    http://technet.microsoft.com/en-us/library/gg491244(EXCHG.80).aspx
    http://technet.microsoft.com/en-us/library/aa997869.aspx

    Good luck!

     

  • Travis Baseflug

    Travis Baseflug - 2010-12-21

    What settign did you exactly change?  Where in the code?

     

  • Steve Lindley

    Steve Lindley - 2010-12-22

    The change wasn't in the coding, it was on the email server (Microsoft Exchange 2007, to be exact - I don't know if it applies to other versions of MS Exchange or not, but it does apply to MS Exchange 2007).  This article sums it up better than I can (http://technet.microsoft.com/en-us/library/gg491244(EXCHG.80).aspx).  I noticed that the hyperlink for this link in my above post did not include the last part, so you may need to copy and paste my link.

    Basically, there is a setting within MS Exchange under the POP3 and also the IMAP4 settings that was changed with the Service Pack 3 rollup 1 update.  That article explains it better than I can.

    The second link above explains in detail how to change this setting back (http://technet.microsoft.com/en-us/library/aa997869.aspx). 

    1.In the console tree, navigate to Server Configuration > Client Access.

    2.In the work pane, click the POP3 and IMAP4 tab.

    3.Select POP3 (or IMAP4, if using IMAP4) and then, in the result pane, under POP3 (or IMAP4, if using IMAP4) , click Properties.

    4.On the POP3 (or IMAP4, if using IMAP4) Properties page, click the Retrieval Settings tab.

    5.Under Message Retrieval, select a message format from the drop-down list under Message MIME format.

    6.Click Apply, and then click OK to save your changes.

    7. Restart the POP3 (or IMAP4, if using IMAP4) MS Exchange service

    I use POP3 only, so I just change my POP3 setting, not the IMAP4 setting, then restarted the POP3 service.

    You mentioned that it was working, then it stopped and started giving the "NO PLAIN TEXT MESSAGE BODY FOUND."  Based on the date of your post, I just guessed that you might be using MS Exchange (2003/2007/2010) and recently installed the Exchange 2007 SP3 Update Rollup 1 Microsoft Update.  Since I was having the same problem after installing that updated (it took me a week to figure out that was the problem), I was able to get it fixed a few minutes before posting.  If you're not using MS Exchange as your email server, but it was working before, then I'd check your email server settings.  Hopefully one of those articles will help troubleshoot your email server (if it's not MS Exchange).

    Hopefully that makes sense!

     

  • Warrickg

    Warrickg - 2013-09-17

    We are using btnet version 3.6.2 which uses a gmail account for the emails that come in, there emails then create the bugs in the system.

    Everything works wonderfully, except when users send emails that are in plain text format. When this happened the system was creating or adding onto bugs and all the bug said was "NO PLAIN TEXT MESSAGE BODY FOUND". I went through the code and found that on the insert_bug.aspx file that if "text/plain" or "text/html" was not found in the email then it just inserted the line "NO PLAIN TEXT MESSAGE BODY FOUND". So I updated the code do be as it is below. If the code did not find "text/plain" or "text/html" then I just used the body of the mime_massage object.

    This seems to be working fine so far. Even though some of text in the body is not 100%, for example it adds "=20" to some of the lines and a few other things, but the guys looking into the bugs can read what is in the emails and carry on working.

    I hope this can help someone else.
    Here is the code I changed:

    string comment = MyMime.extract_comment_text_from_email(mime_message, "text/plain");
    if (comment == null)
    {
    comment = MyMime.extract_comment_text_from_email(mime_message, "text/html");
    }
    if (comment == null)
    {
    //comment = "NO PLAIN TEXT MESSAGE BODY FOUND";
    comment = mime_message.Body;
    }

     

    Last edit: Warrickg 2013-09-17

  • Corey Trager

    Corey Trager - 2013-10-26

    Probably not till 2014, but the focus of the next release will be on parsing incoming emails. I know it's not perfect.

     

  • Corey Trager

    Corey Trager - 2014-04-04

    Warrick Goetsch's fix is in version 3.6.3 which I posted today. I would have given Warrick credit for the fix, but I didn't see his post until now.

    There are two problems here. The second problem is the one mentioned by Travis Baseflug and also here: https://sourceforge.net/p/btnet/bugs/800/

    The fix is I commented out some code as mentioned here: https://sourceforge.net/p/btnet/bugs/800/

    That fix will be in the next version.

     

Log in to post a comment.