6.0.0-git
2019-04-25

[#4606] Forwarding Messages from Horde
Summary Forwarding Messages from Horde
Queue IMP
Queue Version 4.1.3
Type Bug
State Resolved
Priority 2. Medium
Owners
Requester dbritt (at) columbusinternational (dot) com
Created 2006-11-01 (4558 days ago)
Due 11/01/2006 (4558 days ago)
Updated 2006-11-20 (4539 days ago)
Assigned 2006-11-03 (4556 days ago)
Resolved 2006-11-10 (4549 days ago)
Milestone
Patch No

History
2006-11-20 14:14:48 dbritt (at) columbusinternational (dot) com Comment #15 Reply to this comment
Hi Jan



Excellent, thank you very much



When can you do this?



Dale
2006-11-18 15:36:11 dbritt (at) columbusinternational (dot) com Comment #14 Reply to this comment
Hi Jan



Can I hire you to make this work on our servers with the unreleased 
version you have?



My biggest email client is very upset and I need this to work asap?



Many thanks

Dale


2006-11-18 11:24:40 Jan Schneider Comment #13 Reply to this comment
Short answer: no

Long answer: the mime parsing and generation code has been been 
refactored a lot in the current development code to fix issues like 
you experience. There is no simple bug fix or patch to fix this.
2006-11-17 20:45:30 dbritt (at) columbusinternational (dot) com Comment #12 Reply to this comment
Hi



We have tried unsuccessfully to make this work. Below is a comment 
from our sys admin



Can you get (perhaps from Jan) either a ?bugfix?, or something I can 
search for.  Something along the lines of content-type or something?   
Whatever it is that changed, I need to know so I can implement it.



Any help would be appreciated.



Thanks

Dale
2006-11-10 20:33:40 Jan Schneider Comment #11 Reply to this comment
It's not released yet, but you can grab a snapshot from snaps.horde.org.
2006-11-10 20:29:34 dbritt (at) columbusinternational (dot) com Comment #10 Reply to this comment
Hi



Where can I download version 4.2?



Thanks

Dale
2006-11-10 15:02:53 Jan Schneider Comment #9
State ⇒ Resolved
Reply to this comment
Yes, I am able to reproduce this, but only with Outlook which 
obviously ignores all standards, as usual. As soon as it sees a 
multipart/alternative mime part in a message, even if it is only an 
attachment like in this case, it displays this part without a choice 
for the user to see a different part.



The good news is though, that this no longer happens with IMP 4.2 
where the forwarding routines have been rewritten and forwarded 
messages are encapsulated in message/rfc822 mime parts which are 
displayed correctly even in Outlook.
2006-11-10 14:40:46 dbritt (at) columbusinternational (dot) com Comment #8 Reply to this comment
Hi Jan



Thank you for your reply



Quick Question, have you seen this before? And were you able to duplicate my

issue?



Many thanks

Dale
2006-11-10 14:06:02 Jan Schneider Comment #7 Reply to this comment
I'm afraid there is not much we can do anyway. Since the generated 
message seems to work fine in Horde and Outlook Express (and probably 
in other mailers too), it seems that Outlook is broken if it can't 
render it.

And since Outlook is not open source, there is no chance to debug why 
it isn't able to display it properly.
2006-11-09 16:41:36 dbritt (at) columbusinternational (dot) com Comment #6 Reply to this comment
Hi



If possible, could you provide me with a quote?



Dale
2006-11-09 16:28:28 Michael Slusarz Comment #5 Reply to this comment
Sorry to bother you with this but we have a couple large client's
asking if this has been resolved.
If it is critical, there is always http://horde.org/consulting/



Otherwise, this is a volunteer project.  So devs will get to it when 
they get to it.
2006-11-09 15:10:50 dbritt (at) columbusinternational (dot) com Comment #4 Reply to this comment
Hello



Sorry to bother you with this but we have a couple large client's 
asking if this has been resolved.



Were you able to reproduce this error? Can I offer any additional information?



Thanks

Dale
2006-11-03 18:41:16 dbritt (at) columbusinternational (dot) com Comment #3 Reply to this comment
We need the message source to be able to debug this.
Header from the email received in Horde



Return-Path: <dbritt@columbusinternational.com>

Delivered-To: daletest@insurebc.ca

Received: (qmail 3610 invoked by uid 399); 3 Nov 2006 18:36:46 -0000

X-Virus-Scan: Scanned by clamdmail 0.15 (no viruses);

   Fri, 03 Nov 2006 10:36:46 -0800

Received: from unknown (HELO onlyhosting.net) (192.220.109.150)

   by mail.www21.onlyhosting.net with SMTP; 3 Nov 2006 18:36:46 -0000

Received-SPF: pass (mail.www21.onlyhosting.net: local policy 
designates 192.220.109.150 as permitted sender)

        identity=mailfrom; client-ip=192.220.109.150;

        envelope-from=<dbritt@columbusinternational.com>;

Received: from Bossman (d205-250-57-174.bchsia.telus.net [205.250.57.174])

        (authenticated bits=0)

        by onlyhosting.net (8.13.6.20060614/8.13.1) with ESMTP id kA3IaiEw096304

        for <daletest@insurebc.ca>; Fri, 3 Nov 2006 10:36:45 -0800 (PST)

Message-ID: <233601c6ff77$5a0c6270$6400a8c0@Bossman>

Reply-To: "Dale Britt" <dbritt@columbusinternational.com>

From: "Dale Britt" <dbritt@columbusinternational.com>

To: <daletest@insurebc.ca>

Subject: Forward Test

Date: Fri, 3 Nov 2006 10:39:04 -0800

Organization: Columbus International

MIME-Version: 1.0

Content-Type: multipart/alternative;

        boundary="----=_NextPart_000_2333_01C6FF34.489ABAC0"

X-Priority: 3

X-MSMail-Priority: Normal

X-Mailer: Microsoft Outlook Express 6.00.2800.1807

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807



This is a multi-part message in MIME format.



------=_NextPart_000_2333_01C6FF34.489ABAC0

Content-Type: text/plain;

        charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable



Hi



This is a forwarding test.



This is the original message sent from Outlook Express to another email



Dale

------=_NextPart_000_2333_01C6FF34.489ABAC0

Content-Type: text/html;

        charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<HTML><HEAD>

<META http-equiv=3DContent-Type content=3D"text/html; =

charset=3Diso-8859-1">

<META content=3D"MSHTML 6.00.2800.1561" name=3DGENERATOR>

<STYLE></STYLE>

</HEAD>

<BODY bgColor=3D#ffffff>

<DIV><FONT face=3DArial size=3D2>Hi</FONT></DIV>

<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>

<DIV><FONT face=3DArial size=3D2>This is a forwarding test.</FONT></DIV>

<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>

<DIV><FONT face=3DArial size=3D2>This is the original message sent from =

Outlook=20

Express to another email</FONT></DIV>

<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>

<DIV><FONT face=3DArial size=3D2>Dale</FONT></DIV></BODY></HTML>



------=_NextPart_000_2333_01C6FF34.489ABAC0--









Header OF Forward Message



Received: from d205-250-57-174.bchsia.telus.net

        (d205-250-57-174.bchsia.telus.net [205.250.57.174]) by 64.40.107.103 (Horde

        MIME library) with HTTP; Fri, 03 Nov 2006 10:38:30 -0800

Message-ID: <20061103103830.b5b09cwjpecc0sk0@64.40.107.103>

Date: Fri, 03 Nov 2006 10:38:30 -0800

From: daletest@insurebc.ca

To: dalespam@onlyhosting.net

Subject: Fwd: Forward Test

MIME-Version: 1.0

Content-Type: multipart/mixed;

        boundary="=_2j9310tzdq68"

Content-Transfer-Encoding: 7bit



This message is in MIME format.



--=_2j9310tzdq68

Content-Type: text/plain;

        charset=ISO-8859-1;

        DelSp="Yes";

        format="flowed"

Content-Disposition: inline

Content-Transfer-Encoding: 7bit



This is the text in the forward message



Dale



----- Forwarded message from dbritt@columbusinternational.com -----

      Date: Fri, 3 Nov 2006 10:39:04 -0800

      From: Dale Britt <dbritt@columbusinternational.com>

Reply-To: Dale Britt <dbritt@columbusinternational.com>

   Subject: Forward Test

        To: daletest@insurebc.ca



Hi



This is a forwarding test.



This is the original message sent from Outlook Express to another email



Dale



----- End forwarded message -----





--=_2j9310tzdq68

Content-Type: multipart/alternative;

        boundary="----=_NextPart_000_2333_01C6FF34.489ABAC0";

        name=""

Content-Transfer-Encoding: 7bit



This message is in MIME format.



------=_NextPart_000_2333_01C6FF34.489ABAC0

Content-Type: text/plain;

        charset=iso-8859-1

Content-Disposition: inline

Content-Transfer-Encoding: quoted-printable



Hi



This is a forwarding test.



This is the original message sent from Outlook Express to another email



Dale

------=_NextPart_000_2333_01C6FF34.489ABAC0

Content-Type: text/plain;

        charset=ISO-8859-1

Content-Disposition: inline

Content-Transfer-Encoding: 7bit



[Attachment stripped: Original attachment type: "text/html", name: "unnamed"]

------=_NextPart_000_2333_01C6FF34.489ABAC0--



--=_2j9310tzdq68--
2006-11-03 07:31:14 Michael Slusarz Comment #2
State ⇒ Feedback
Reply to this comment
We need the message source to be able to debug this.
2006-11-01 15:14:26 dbritt (at) columbusinternational (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Forwarding Messages from Horde
Due ⇒ 2006-11-01
Queue ⇒ IMP
Reply to this comment
I sent a message from my Outlook Express and picked it up in Horde.



I then viewed the message in Horde and click forward



Leaving the previous text I created a message and then entered the

recipients email address and click send



Here's the issue..... When downloading to Outlook the original message shows

up but Not the new text that was added.



If I view it in Outlook Express or Horde I can see the new text




Saved Queries