<<< Date Index >>>     <<< Thread Index >>>

mutt/2760: mime_forward does not work for text/rfc822-headers attachments



>Number:         2760
>Category:       mutt
>Synopsis:       mime_forward does not work for text/rfc822-headers attachments
>Confidential:   no
>Severity:       normal
>Priority:       medium
>Responsible:    mutt-dev
>State:          open
>Keywords:       
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 13 16:25:03 +0100 2007
>Originator:     Christoph Berg <cb@xxxxxxxx>
>Release:        
>Description:

Hi,

the following was submitted as Debian Bug #340506, I can confirm that
behavior here with 1.5.13.


----- Forwarded message from Ambrose Li <ambrose.li@xxxxxxxxx> -----

Date: Wed, 23 Nov 2005 17:20:24 -0500
From: Ambrose Li <ambrose.li@xxxxxxxxx>
Reply-To: 340506@xxxxxxxxxxxxxxx
To: Debian Bug Tracking System <submit@xxxxxxxxxxxxxxx>
Subject: mutt: mime_forward does not work for attachments of type
        text/rfc822-headers

Package: mutt
Version: 1.5.10-1
Severity: normal


If I try to forward an attachment of type text/rfc822-headers, mutt will 
forward it in-line and with lots of headers deleted. This happens even if I 
explicitly "set mime_forward".

It is thus currently impossible to forward "full headers" for spam reporting if 
the only headers available are inside a text/rfc822-headers attachment.

(Workaround is to save the attachment to a file, then insert the file from the 
text editor. Therefore the bug is "normal" and not "important".)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.28-ow1
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5)

Versions of packages mutt depends on:
ii  libc6                        2.3.5-8     GNU C Library: Shared libraries an
ii  libdb4.3                     4.3.29-1    Berkeley v4.3 Database Libraries [
ii  libgnutls11                  1.0.16-13.1 GNU TLS library - runtime library
ii  libidn11                     0.5.18-1    GNU libidn library, implementation
ii  libncursesw5                 5.5-1       Shared libraries for terminal hand
ii  libsasl2                     2.1.19-1.7  Authentication abstraction library
ii  postfix [mail-transport-agen 2.2.4-1.0.1 A high-performance mail transport 

Versions of packages mutt recommends:
ii  locales                       2.3.5-8    GNU C Library: National Language (
ii  mime-support                  3.35-1     MIME files 'mime.types' & 'mailcap

-- no debconf information



----- End forwarded message -----
----- Forwarded message from Ambrose Li <ambrose.li@xxxxxxxxx> -----

Date: Mon, 27 Mar 2006 15:35:42 -0500
From: Ambrose Li <ambrose.li@xxxxxxxxx>
Reply-To: 340506@xxxxxxxxxxxxxxx
To: 340506@xxxxxxxxxxxxxxx, Adeodato Sim?? <dato@xxxxxxxxxxxxxx>
Subject: Re: Bug#340506: mutt: mime_forward does not work for attachments
        of type text/rfc822-headers
Disposition-Notification-To: ambrose.li@xxxxxxxxx

Hi

sorry for the late reply; such bounces are hard to come by (most have the
complete mail in them, and I don't know how to make an artificial sample).

I just got the odd one (which is also an odd one) today.

Please find a sample mbox attached.

Regards,
Ambrose

On Mon, Jan 30, 2006 at 04:50:57AM +0100, Adeodato Sim?? wrote:
> Hi, any updates on this? Thanks.
> 
> * Adeodato Sim?? [Thu, 24 Nov 2005 01:55:40 +0100]:
> 
> > * Ambrose Li [Wed, 23 Nov 2005 17:20:24 -0500]:
> 
> > Hi,
> 
> > > If I try to forward an attachment of type text/rfc822-headers, mutt
> > > will forward it in-line and with lots of headers deleted. This happens
> > > even if I explicitly "set mime_forward".
> 
> > > It is thus currently impossible to forward "full headers" for spam
> > > reporting if the only headers available are inside a
> > > text/rfc822-headers attachment.
> 
> >   There are several more forwarding-related options; could I have a
> >   sample mbox to test?
> 
> >   If not, what are the value of your $mime_forward_decode and
> >   $mime_forward_rest variables? Also, if you set $mime_forward to no,
> >   does unsetting $forward_decode help?
> 
> > > (Workaround is to save the attachment to a file, then insert the file
> > > from the text editor. Therefore the bug is "normal" and not
> > > "important".)
> 
> >   As a last resort, I believe you could also unset $weed.
> 
> >   I wait your feedback on this bug report,
> 
> 
> -- 
> Adeodato Sim??                                     dato at net.com.org.es
> Debian Developer                                  adeodato at debian.org
>  
> Everything you read in newspapers is absolutely true, except for that
> rare story of which you happen to have first-hand knowledge.
>                 -- Erwin Knoll
> 


Christoph
-- 
cb@xxxxxxxx | http://www.df7cb.de/

>Fix:

Unknown
>Add-To-Audit-Trail: