After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618912 - forwarded message is not shown correctly
forwarded message is not shown correctly
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-05-17 18:32 UTC by Benedict Stein
Modified: 2011-04-21 11:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
message source modified but as text upload (2.68 KB, text/plain)
2010-05-17 18:41 UTC, Benedict Stein
Details
evo-fail-look.png (90.68 KB, image/png)
2010-05-19 15:08 UTC, Benedict Stein
Details
gmail-working-look.png (95.44 KB, image/png)
2010-05-19 15:09 UTC, Benedict Stein
Details
gmail_message_source.txt (47.19 KB, text/plain)
2010-05-20 12:09 UTC, Benedict Stein
Details

Description Benedict Stein 2010-05-17 18:32:10 UTC
" MIME structure looks valid. the attachment is a message/rfc822"


Message Source:
   1.
      Delivered-To: <<<mymailadress>>>
   2.
      Received: by 10.142.239.2 with SMTP id m2cs137710wfh; Mon, 17 May 2010
   3.
       01:02:47 -0700 (PDT)
   4.
      Received: by 10.213.44.5 with SMTP id y5mr2195480ebe.62.1274083366434; Mon,
   5.
       17 May 2010 01:02:46 -0700 (PDT)
   6.
      Return-Path: <<<sendermailadress>>>
   7.
      Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [<<<SenderIP>>>]) by
   8.
       mx.google.com with ESMTP id 19si4603832ewy.41.2010.05.17.01.02.44; Mon, 17
   9.
       May 2010 01:02:45 -0700 (PDT)
  10.
      Received-SPF: neutral (google.com: 81.169.146.161 is neither permitted nor
  11.
       denied by best guess record for domain of <<<Sender Domain>>>)
  12.
       client-ip=<<<some IP>>>;
  13.
      Authentication-Results: mx.google.com; spf=neutral (google.com:
  14.
       81.169.146.161 is neither permitted nor denied by best guess record for
  15.
       domain of <<<sender adress>>>) smtp.mail=<<<sender adress>; dkim=pass
  16.
       (test mode) header.i=@<<<sender-domain>>>
  17.
      DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1274083364; l=47658;
  18.
       s=domk; d=<<<sender domain>>>;
  19.
       h=Content-Type:Subject:CC:To:MIME-Version:From:Date:X-RZG-CLASS-ID:
  20.
       X-RZG-AUTH; bh=mWi307pQuktP62eQ1bfuLPB1ioA=;
  21.
       b=ED2eFGeb1ZkCibXUQjrhCGzgh4kYoyMKm+6WClEdWQnKMZQkMPRfK/sxs8fRqT/NleF
  22.
       VMqOTcGVkU5sFkzjXpumQPG1+C9MD9WWgL2qrJuDlOJgbw0LLW7Ex209UhF/xtCRbsJkl
  23.
       sYleV0LBQvmrAlEd302HDLf1Xf6xFymVeCI=
  24.
      X-RZG-AUTH:
  25.
       :KWoDVVSgdPIcdaAUun2z5u8O6nQfZz8If8GQaCdpW9VtK+r5Qs49x4sqo3MdHMU=
  26.
      X-RZG-CLASS-ID: mo00
  27.
      Received: from [0.0.0.0] (<<<sender network with IP<<<) by
  28.
       post.strato.de (mrclete mo19) (RZmta 23.0) with ESMTP id C00cbam4H7E73c ;
  29.
       Mon, 17 May 2010 10:02:42 +0200 (MEST)
  30.
      Message-ID: <4BF0F81D.3070509@thomas-klein.de>
  31.
      Date: Mon, 17 May 2010 10:02:37 +0200
  32.
      From: <<<name + mail
  33.
      User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
  34.
      MIME-Version: 1.0
  35.
      To: <<<mymail + 3 others>>>
  36.
      CC: <<<another mail>>>
  37.
      Subject: [Fwd: =?ISO-8859-1?Q?Verbesserungsvorschl=E4ge_Internetauftrit?=
  38.
       =?ISO-8859-1?Q?t_EFG=5D?=
  39.
      Content-Type: multipart/mixed; boundary="------------060902090103060708080601"
  40.
      X-Evolution-Source: imap://<<<my IMAP>>>
  41.
       
  42.
       
  43.
      --------------060902090103060708080601
  44.
      Content-Type: text/plain; charset=ISO-8859-1; format=flowed
  45.
      Content-Transfer-Encoding: 8bit
  46.
       
  47.
      <<<<Text body>>>>
  48.
       
  49.
      --------------060902090103060708080601
  50.
      Content-Type: message/rfc822; name="=?ISO-8859-1?Q?Verbesserungsvorschl=E4ge_Internetauftritt_EFG=2Eeml?="
  51.
      Content-Transfer-Encoding: 7bit
  52.
      Content-Disposition: inline; filename*0*=ISO-8859-1''%56%65%72%62%65%73%73%65%72%75%6E%67%73%76%6F%72; filename*1*=%73%63%68%6C%E4%67%65%20%49%6E%74%65%72%6E%65%74%61%75%66%74; filename*2*=%72%69%74%74%20%45%46%47%2E%65%6D%6C
  53.
       
  54.
      From:
  55.
      Date: Mon, 17 May 2010 20:17:52 +0200
  56.
      Subject: No Subject
  57.
      Message-ID: <1274120272.3157.11.camel@vaio-fe31m>
  58.
      Mime-Version: 1.0
Comment 1 Benedict Stein 2010-05-17 18:41:24 UTC
Created attachment 161252 [details]
message source modified but as text upload
Comment 2 Matthew Barnes 2010-05-18 17:31:01 UTC
A similar bug (bug #618994) mentioned some irregularity regarding "eml" attachments and cache directory permissions.  Worth taking a quick look while addressing this bug.
Comment 3 Matthew Barnes 2010-05-18 22:15:28 UTC
Your message source attachment is missing a terminating MIME boundary, which I assume was in the original message but accidentally got snipped.  I appended the following lines before importing:

---8<------8<------8<------8<------8<------8<------8<---

<<<Attachment Body>>>

--------------060902090103060708080601--

---8<------8<------8<------8<------8<------8<------8<---

The attached "No Subject" message was readable, but there were two attachment "arrow buttons" where there should have only been one.  The first appeared as expected in the outer message as type "email message attachment" (filename.eml), but the second one appeared unexpectedly in the inner message as type "plain text document attachment" (filename.eml) and clicking the arrow did nothing.  Both filenames were the same.

Is this approximately what you're seeing?
Comment 4 Benedict Stein 2010-05-19 15:08:51 UTC
Created attachment 161455 [details]
evo-fail-look.png
Comment 5 Benedict Stein 2010-05-19 15:09:28 UTC
Created attachment 161456 [details]
gmail-working-look.png
Comment 6 Benedict Stein 2010-05-19 15:10:24 UTC
I suppose to have it as a embedded forwarded message but the file as PDF download as attachment available - see gmail screenshot
Comment 7 Matthew Barnes 2010-05-19 22:28:24 UTC
Where did the PDF part come from?  Did GMail generate that itself?  It's not shown anywhere in the message source you posted.

The message source you posted shows the following MIME structure:

    multipart/mixed
        text/plain
        message/rfc822
Comment 8 Benedict Stein 2010-05-20 12:09:06 UTC
Created attachment 161543 [details]
gmail_message_source.txt

Hi Matthew, I'm sure the PDF was within the forwarded message - as i ddin't have it before.

The PDF is the only reason why I reported this bug - i don't care about the text, but i do regarding the attachment


attached the gmail source viewe
Comment 9 Milan Crha 2011-04-21 11:18:00 UTC
Thanks for a bug report. I fixed this recently (in time of 2.91.91) by two commits, commit 2533e52b and commit 9a6f182c0, in evolution. There is no bug reference for it, as I did it when I faced it. Your attached gmail message is shown correctly, after the import, in a message view, the PDF file is accessible, when I try this with current stable, which is 3.0.0.