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

Re: [Mutt] #902: Generated boundary was in attached file



#902: Generated boundary was in attached file

Changes (by brendan):

  * status:  new => closed
  * resolution:  => fixed

Old description:

> {{{
> Package: mutt
> Version: 1.3.23.2i
> Severity: normal
>
> -- Please type your report below this line
>
> I have recently sent a message which contained an attached message.
> The generated boundary was:
>
>    Content-Type: multipart/mixed; boundary="X1bOJ3K7DJ5YkBrT"
>
> However the attached message was a mbox-type mailbox which happened
> to contain a multipart message with exactly the same boundary
> parameter. This, of course, corrupted the message.
>
> I guess that it is superfluous to quote RFC 2046, but anyway I do:
>
>    As stated previously, each body part is preceded by a boundary
>    delimiter line that contains the boundary delimiter.  The boundary
>    delimiter MUST NOT appear inside any of the encapsulated parts, on a
>    line by itself or as the prefix of any line.  This implies that it is
>    crucial that the composing agent be able to choose and specify a
>    unique boundary parameter value that does not contain the boundary
>    parameter value of an enclosing multipart as a prefix.
>

>

> -- Build environment information
>
> (Note: This is the build environment installed on the system
> muttbug is run on.  Information may or may not match the environment
> used to build mutt.)
>
> - gcc version information
> gcc
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
>
> - CFLAGS
> -Wall -pedantic -g -O2
>
> -- Mutt Version Information
>
> Mutt 1.3.23.2i (2001-11-08)
> Copyright (C) 1996-2001 Michael R. Elkins m.fl.
> Der følger ABSOLUT INGEN GARANTI med Mutt; tast `mutt -vv` for detaljer.
> Mutt er et frit program, og du er velkommen til at redistribuere det
> under visse betingelser; tast `mutt -vv` for detaljer.
>
> System: Linux 2.4.7-10 (i686) [using ncurses 5.2]
> Tilvalg ved oversættelsen:
> -DOMAIN
> +DEBUG
> +HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  -DL_STANDALONE
> +USE_FCNTL  -USE_FLOCK
> -USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_SASL
> +HAVE_REGCOMP  -USE_GNU_REGEX
> +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
> +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
> +HAVE_PGP  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
> +ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
> +HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  -HAVE_GETADDRINFO
> ISPELL="/usr/bin/ispell"
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="Mailbox"
> PKGDATADIR="/usr/local/share/mutt"
> SYSCONFDIR="/usr/local/etc"
> EXECSHELL="/bin/sh"
> -MIXMASTER
> For at kontakte Mutts udviklere, skriv venligst til <mutt-dev@xxxxxxxx>.
> Brug venligst flea(1)-værktøjet, hvis du vil rapportere en bug.
>

>
> >How-To-Repeat:
>
> >Fix:
> }}}

New description:

 {{{
 Package: mutt
 Version: 1.3.23.2i
 Severity: normal

 -- Please type your report below this line

 I have recently sent a message which contained an attached message.
 The generated boundary was:

    Content-Type: multipart/mixed; boundary="X1bOJ3K7DJ5YkBrT"

 However the attached message was a mbox-type mailbox which happened
 to contain a multipart message with exactly the same boundary
 parameter. This, of course, corrupted the message.

 I guess that it is superfluous to quote RFC 2046, but anyway I do:

    As stated previously, each body part is preceded by a boundary
    delimiter line that contains the boundary delimiter.  The boundary
    delimiter MUST NOT appear inside any of the encapsulated parts, on a
    line by itself or as the prefix of any line.  This implies that it is
    crucial that the composing agent be able to choose and specify a
    unique boundary parameter value that does not contain the boundary
    parameter value of an enclosing multipart as a prefix.




 -- Build environment information

 (Note: This is the build environment installed on the system
 muttbug is run on.  Information may or may not match the environment
 used to build mutt.)

 - gcc version information
 gcc
 Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
 gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)

 - CFLAGS
 -Wall -pedantic -g -O2

 -- Mutt Version Information

 Mutt 1.3.23.2i (2001-11-08)
 Copyright (C) 1996-2001 Michael R. Elkins m.fl.
 Der følger ABSOLUT INGEN GARANTI med Mutt; tast `mutt -vv` for detaljer.
 Mutt er et frit program, og du er velkommen til at redistribuere det
 under visse betingelser; tast `mutt -vv` for detaljer.

 System: Linux 2.4.7-10 (i686) [using ncurses 5.2]
 Tilvalg ved oversættelsen:
 -DOMAIN
 +DEBUG
 +HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  -DL_STANDALONE
 +USE_FCNTL  -USE_FLOCK
 -USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_SASL
 +HAVE_REGCOMP  -USE_GNU_REGEX
 +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
 +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
 +HAVE_PGP  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
 +ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
 +HAVE_LANGINFO_YESEXPR
 +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  -HAVE_GETADDRINFO
 ISPELL="/usr/bin/ispell"
 SENDMAIL="/usr/sbin/sendmail"
 MAILPATH="Mailbox"
 PKGDATADIR="/usr/local/share/mutt"
 SYSCONFDIR="/usr/local/etc"
 EXECSHELL="/bin/sh"
 -MIXMASTER
 For at kontakte Mutts udviklere, skriv venligst til <mutt-dev@xxxxxxxx>.
 Brug venligst flea(1)-værktøjet, hvis du vil rapportere en bug.



 >How-To-Repeat:

 >Fix:
 }}}

Comment:

 Fixed in [59fcc37f8c75]

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/902#comment:3>