Roundcube Community Forum

 

Issue: Some emails display only headers instead of body

Started by zambuka42, May 31, 2015, 04:51:42 PM

Previous topic - Next topic

zambuka42

Some incoming emails do not show the body of the email, instead they show the headers only as if the headers WERE the body. However, if you go to MORE -> SHOW SOURCE, you WILL see the body at the end of the source. These emails are being served by an hmailserver. I have verified that other email clients retrieving the emails from the hmailserver will display properly, so the issue is with roundcube. Below I will post the source information for an email that DOESN'T work, and one that DOES. Any advice would be greatly appreciated...




SOURCE OF EMAIL THAT DOES NOT DISPLAY PROPERLY
Return-Path: [email protected]
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on atllsx-PC
X-Spam-Level:
X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_MSPIKE_H3,
RCVD_IN_MSPIKE_WL,SPF_PASS,TVD_SPACE_RATIO autolearn=ham autolearn_force=no
version=3.4.0
X-hMailServer-ExternalAccount: atllsx
Delivered-To: [email protected]
Received-SPF: Pass (zoho.com: domain of [email protected] designates 182.50.144.112 as permitted sender using best guess )  client-ip: 182.50.144.112
Return-Path: <[email protected]>
Received: from sg2plwbeout19-2.prod.sin2.secureserver.net (sg2plwbeout19-2.prod.sin2.secureserver.net [182.50.144.36]) by mx.zohomail.com
with SMTPS id 14331040370281007.447052609836; Sun, 31 May 2015 13:27:17 -0700 (PDT)
Received: from localhost ([182.50.144.112])
by sg2plwbeout19-2.prod.sin2.secureserver.net with bizsmtp
id akTE1q0012Rj2se01kTEcd; Sun, 31 May 2015 13:27:14 -0700
Received: (qmail 23582 invoked by uid 99); 31 May 2015 20:27:14 -0000
X-SID: akTE1q0012Rj2se01
MIME-Version: 1.0
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: [email protected]
From: [email protected]
Subject: lkjlkj
Date: Sun, 31 May 2015 13:27:14 -0700
Message-Id: <20150531132714.fb1c08b889b8af5386e9c5950cc0ab74.23516b9394.mailapi@mobilemail19.asia.secureserver.net>
X-Originating-IP: 71.204.43.94
User-Agent: MailAPI
X-Sender: [email protected]
X-ZohoMail: SS_1 SFPD SFPP UW2468 UB2468 PIW  SF_SOIPH1_5 COSF  NDL   SGR3_1_08055_702
X-ZohoMail-Owner: <20150531132714.fb1c08b889b8af5386e9c5950cc0ab74.23516b9394.mailapi@mobilemail19.asia.secureserver.net>+zmo_0_<[email protected]>
X-ZohoMail-Sender: 182.50.144.112
X-Zoho-Virus-Status: 2
X-EsetId: 37303A2908176F61647564

test





SOURCE OF EMAIL THAT DISPLAYS PROPERLY
Return-Path: [email protected]
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on atllsx-PC
X-Spam-Level:
X-Spam-Status: No, score=-0.0 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,
RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS autolearn=ham autolearn_force=no
version=3.4.0
X-hMailServer-ExternalAccount: atllsx
Delivered-To: [email protected]
Received-SPF: Pass (zoho.com: domain of [email protected] designates 209.85.215.50 as permitted sender )  client-ip: 209.85.215.50
Return-Path: <[email protected]>
Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mx.zohomail.com
with SMTPS id 1433104103234964.2485765489146; Sun, 31 May 2015 13:28:23 -0700 (PDT)
Received: by laat2 with SMTP id t2so88185947laa.1
        for <[email protected]>; Sun, 31 May 2015 13:28:20 -0700 (PDT)
Received: by 10.25.30.12 with HTTP; Sun, 31 May 2015 13:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=/pv3qrPFvepqFLezS6C5UkYsHehhmgn2Ffs3zrpKY4Y=;
        b=aIoXoJYy02ZQPnDhrwwKlPsKbiU8Fz2RXfrgGd2Y9JPmZ+ieA2NXgROK6yrQP9rkPp
         cB1unTBQjrqL6WJ/KVbVf/OiAy5h4fzoxD6/5ZhZHypD+X28sV+PoKlYrYiYH2ZM8BW2
         F5sVbbDYiKKCr5rr+rQrkYy7IdMfuR/q9yJsbvk2snJRya2GMtymew+4GN91z5yMCc83
         sLg0pULzw6/ba3rxCdYemrM5cWcN8QWXT0JpDdXyrunryTIDOKJyk4DclRUW0+dmJzXX
         36rpUg/hjQkX4nQjHu5vBIJ08xjXfIG0MVceWC2IKRvVIkGe0VeR5rX6+Fad1WloRej/
         wqnQ==
MIME-Version: 1.0
X-Received: by 10.112.25.39 with SMTP id z7mr4392277lbf.102.1433104100270;
Sun, 31 May 2015 13:28:20 -0700 (PDT)
Date: Sun, 31 May 2015 16:28:20 -0400
Message-ID: <CA+OeJ8dTb7KKqLp8RcHsvOVT_gmSFBY2RMZMMMLFGc-Z3BgO3A@mail.gmail.com>
Subject: test
From: Testing Testing <[email protected]>
To: [email protected]
Content-Type: multipart/alternative; boundary=001a11c3f310d2a9860517668c85
X-ZohoMail: SS_6 SFPD SFPP UW2468 UB6248 FMWL SFP_WHTLST JMID COSF  ODL   SGR3_1_08055_16
X-ZohoMail-Owner: <CA+OeJ8dTb7KKqLp8RcHsvOVT_gmSFBY2RMZMMMLFGc-Z3BgO3A@mail.gmail.com>+zmo_0_<[email protected]>
X-ZohoMail-Sender: 209.85.215.50
X-Zoho-Virus-Status: 2
X-EsetId: 37303A2908176F61647564

--001a11c3f310d2a9860517668c85
Content-Type: text/plain; charset=UTF-8

test

--001a11c3f310d2a9860517668c85
Content-Type: text/html; charset=UTF-8

<div dir="ltr">test<br></div>

--001a11c3f310d2a9860517668c85--


zambuka42

I've figured out that this is happening on all emails with a content-type: of text/plain. I'm going to start a new post directed at that issue and if an answer is forthcoming, I'll post it here to make the issue/fix better searchable.