Ticket #1200 (assigned defect)

Opened 7 years ago

Last modified 6 months ago

mbox From_ line format over-strict expectations

Reported by: Nicolas Le Scouarnec <nlsn@…> Owned by: mutt-dev
Priority: minor Milestone:
Component: mutt Version: 1.5.17
Keywords: Cc: yusufg@…, jhawk@…

Description

Package: mutt
Version: 1.3.27i
Severity: normal

-- Please type your report below this line

Mutt does not read all messages in the to following mailboxes.
It only found 21 messages over hundreds in the first one and he doesn't found
any message in the other one.

ftp://ftp.cac.washington.edu/imap/c-client_archive_gz/

Bug reported on the newgroup: fr.comp.mail 


-- 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
cc -I/usr/local/include
Using builtin specs.
gcc version 2.95.3 20010315 (release) [FreeBSD]

- CFLAGS
-Wall -pedantic -O -pipe

-- Mutt Version Information

Mutt 1.3.27i (2002-01-22)
Copyright (C) 1996-2001 Michael R. Elkins et autres.
Mutt ne fournit ABSOLUMENT AUCUNE GARANTIE ; pour les détails tapez `mutt -vv'.
Mutt est un logiciel libre, et vous êtes libre de le redistribuer
sous certaines conditions ; tapez `mutt -vv' pour les détails.

System: FreeBSD 4.4-RELEASE-p9 (i386) [using slang 10404]
Options de compilation :
-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/local/bin/ispell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
EXECSHELL="/bin/sh"
-MIXMASTER
Pour contacter les développeurs, veuillez écrire à <mutt-dev@mutt.org>.
Pour signaler un bug, veuillez utiliser l'utilitaire flea(1).


--- Begin /usr/local/etc/Muttrc
ignore "from " received content- mime-version status x-status message-id
ignore sender references return-path lines
macro index \eb '/~b ' 'search in message bodies'
macro index \cb |urlview\n 'call urlview to extract URLs out of a message'
macro pager \cb |urlview\n 'call urlview to extract URLs out of a message'
macro generic <f1> "!less /usr/local/share/doc/mutt/manual.txt\n" "Show Mutt documentation"
macro index   <f1> "!less /usr/local/share/doc/mutt/manual.txt\n" "Show Mutt documentation"
macro pager   <f1> "!less /usr/local/share/doc/mutt/manual.txt\n" "Show Mutt documentation"
--- End /usr/local/etc/Muttrc


Received: (at submit) by bugs.guug.de; 5 Dec 2002 15:18:16 +0000
From alefav@bsdshell.dyndns.org Thu Dec 05 16:18:16 2002
Received: from [208.247.65.237] (helo=bsdshell.dyndns.org ident=root)
	by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian))
	id 18JxlW-0003Bx-00
	for <submit@bugs.guug.de>; Thu, 05 Dec 2002 16:18:15 +0100
Received: from bsdshell.dyndns.org (alefav@localhost [127.0.0.1])
	by bsdshell.dyndns.org (8.12.5/8.12.5) with ESMTP id gB5FIfKe090507
	for <submit@bugs.guug.de>; Thu, 5 Dec 2002 10:18:41 -0500 (EST)
	(envelope-from alefav@bsdshell.dyndns.org)
Received: (from alefav@localhost)
	by bsdshell.dyndns.org (8.12.5/8.12.5/Submit) id gB5FIS7D090506
	for submit@bugs.guug.de; Thu, 5 Dec 2002 15:18:28 GMT
Message-Id: <200212051518.gB5FIS7D090506@bsdshell.dyndns.org>
Date: 5 Dec 2002 15:13:59 -0000
From: nv017001@sneakemail.com
Subject: mutt-1.5.1i: strange behavior when email address contains 0xA0 's
To: submit@bugs.guug.de
Personality: fake

Package: mutt
Version: 1.5.1i
Severity: normal

-- Please type your report below this line
I recently had problems with mutt reading a news article (saved
to a file). It turned out that the poster uses an email address
\xA0@\xA0.\xA0 and mutt seems to ignore the mailbox delimiter line
	From \xA0@\xA0.\xA0 ...

Is this a bug?
I have appended a zipped and uuencoded copy of a mailbox that
can be used to reproduce the error.

-- Mutt Version Information

Mutt 1.5.1i (2002-05-02)
System: Linux 2.4.18 (i686) [using slang 10401]

-- Sample mailbox
begin 644 mbox.gz
M'XL("+=L[ST``VUB;W@`C9-=;]LV%(;O]2M8;!<;&K&2+,N6UJW^3OPEV['J
M."F*@I8HBS%%RB1EV?DU^:FCW/4B`SH,$""`?,^+E\\Y9R1X#EX[`+Z"*"O!
M`,<`-('M!FXK<#S@6)9CA&&T-)=<*L+VY@`I'-3:&V`UK_I:`RPG:/A!LPE,
MR[,L(\25W`M>%C(`.8D%ESQ5L"AWE,2P(BSAE3P7,,.T^(98\DV61<&%NHEY
M7D`N(26L/-\@JGZ(_?;;.Y@3&=_\A_4.21)+8UWNGG&L`G"O4S]D),[`$@E%
M%.$,?``]SA68(X;V6``BP0Y+]>F3,=)4`HWE%;X:"[%'C+R@ND*?&2-.*:_*
MPHQX`.J$*44Y-G[&Q0H:7F`[FDM;<]F:-1F!48*%SD/8)@06]'UH.PGXDB?R
M*_CMW/9`P]D1]7LMYV97Q!DY:?,+EL8]3K'`+,8:[,=&TU=EZ::8Y?'^X/O'
M?)_LTI9']C+/D6^U1<=%9ZC!_04^8M3*5^XO>?^N"QW7<CO1U)FO1U%XN[0M
M?;^95'<^=-NN]^OAQ8&N[[9\K\/^B6O#0O`$$I5`K/EEN@D'R+#2A8M5=VH/
M>ZPVMBWG7\;&?#P?FALLY)6?#2VCSYG"3)G1I:B1X;/ZL*2(L#]`G"$AL?KS
M\]KLKOOCL3''4NK>F..!?B[URIBM^I-):])[WD[WV^@A;JPZLL#H@)&\7/,8
M,\)J.([W=F[O]#\`G@MMZ$#;KUL1"13K`/+4,)>5"!%W&+X\Q&&?2D27(QP/
M#[VNE;T<VR5/Q2)OA=WFIERM-GS12"</)Q3B:#QO3]GM=HD.3^X=:1!Q/$7K
MX3M"+^/#DS=<'?S!?$61P.?;SZ?[[2@ZK1]EE#RN^[P<VM[[\%"<_/-B,*!J
MTIOAP>SI6&5%D;OT<;Z1+Z?N>OINC"[G5O7<*]O'I^.Y1W7TOMZ%&IF2W\=P
M5TK\%H06#>;][O]3=NM34R_B]YHQ2[5T2;4"ZY4`LA08*`Y2+BHD$H!`S(L+
MX"GHSF8@NTZS_)G-0F585$0[5?HCE-:.)4,[>O748Z6'68(++P6(?X2MCPLL
EZ$6[UAU,"57UQMC0-HPO0*HR34&"*58X`5^-OP%Y.0[,Q@0`````
`
end

Received: (at submit) by bugs.guug.de; 16 Dec 2002 02:52:29 +0000
From yusufg@outblaze.com Mon Dec 16 03:52:29 2002
Received: from 202-77-223-51.outblaze.com ([202.77.223.51] helo=corpmail.outblaze.com)
	by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian))
	id 18NlMq-0004uo-00
	for <submit@bugs.guug.de>; Mon, 16 Dec 2002 03:52:29 +0100
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by corpmail.outblaze.com (Postfix) with ESMTP id F10E77D4B
	for <submit@bugs.guug.de>; Mon, 16 Dec 2002 02:58:44 +0000 (GMT)
Received: from yusufg.portal2.com (202-77-223-125.outblaze.com [202.77.223.125])
	by corpmail.outblaze.com (Postfix) with SMTP id AB918520D2
	for <submit@bugs.guug.de>; Mon, 16 Dec 2002 02:58:44 +0000 (GMT)
Received: (qmail 18858 invoked by uid 500); 16 Dec 2002 02:52:50 -0000
Date: 16 Dec 2002 02:52:50 -0000
Message-ID: <20021216025250.18857.qmail@yusufg.portal2.com>
From: "Yusuf Goolamabbas" <yusufg@outblaze.com>
Subject: mutt-1.4i: Unable to read any of the psyche-list archives mailboxes
To: submit@bugs.guug.de
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.6; VAE: 6.17.0.2; VDF: 6.17.0.6; host: corpmail.outblaze.com)

Package: mutt
Version: 1.4i
Severity: normal

-- Please type your report below this line
Hi, When I download and gunzip the archives of the psyche-list

https://listman.redhat.com/pipermail/psyche-list/

mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail'
command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody
else seeing similar behaviour and can explain why this is so

Regards, Yusuf
yusufg@outblaze.com


-- Mutt Version Information

Mutt 1.4i (2002-05-29)
Copyright (C) 1996-2001 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.4.20 (i686) [using slang 10401]
Compile options:
DOMAIN="outblaze.com"
-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/site/mutt/share/mutt"
SYSCONFDIR="/usr/local/site/mutt/etc"
EXECSHELL="/bin/sh"
-MIXMASTER
To contact the developers, please mail to <mutt-dev@mutt.org>.
To report a bug, please use the flea(1) utility.


Received: (at submit) by bugs.guug.de; 4 Jan 2004 11:00:39 +0000
From jhawk@MIT.EDU Sun Jan 04 12:00:36 2004
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian))
	id 1Ad5zn-0006b7-00
	for <submit@bugs.guug.de>; Sun, 04 Jan 2004 12:00:35 +0100
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i04B3FFp016252;
	Sun, 4 Jan 2004 06:03:15 -0500 (EST)
Received: from coleco-sidewinder.mit.edu (COLECO-SIDEWINDER.MIT.EDU [18.187.2.149])
	(authenticated bits=56)
        (User authenticated as jhawk@ATHENA.MIT.EDU)
	by manawatu-mail-centre.mit.edu (8.12.4/8.12.4) with ESMTP id i04B3D8e008964;
	Sun, 4 Jan 2004 06:03:14 -0500 (EST)
Received: (from jhawk@localhost) by coleco-sidewinder.mit.edu (8.12.9)
	id i04B3DlP008485; Sun, 4 Jan 2004 06:03:13 -0500 (EST)
Date: Sun, 4 Jan 2004 06:03:13 -0500 (EST)
From: jhawk@MIT.EDU
Message-Id: <200401041103.i04B3DlP008485@coleco-sidewinder.mit.edu>
Subject: mutt-1.4.1i: Mutt doesn't like some ^From mailbox seperators (esp. with "at")
To: submit@bugs.guug.de
X-Spam-Status: No, hits=-3.6 required=4.0
	tests=BAYES_10,NO_REAL_NAME
	version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)

Package: mutt
Version: 1.4.1i
Severity: normal

-- Please type your report below this line

(This is also seen with 1.5.4).

Mutt fails to properly read mbox-format files with From lines like:

  From dtucker at zip.com.au  Thu Jan  1 11:19:33 2004

This sort of mbox-file can be found, e.g., at
http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January.txt

With debugging, mutt spews:

is_from(): parsing: dtucker at zip.com.au  Thu Jan  1 11:19:33 2004
is_from(): got return path: dtucker
is_from():  expected weekday, got: at zip.com.au  Thu Jan  1 11:19:33 2004

mutt then shows a mailbox with none or one or two messages,
instead of the correct number.

I'm not sure what the best way to make the parser more flexible is.
In http://www.imc.org/ietf-smtp/old-archive/msg02087.html,
jgm notes:

| Mark Crispin's c-client has code to parse at least 20 different
| variants of this format--10 different possible date formats, each with
| or without a " remote from XXX" after it.

So maybe that code should be hunted down and copied/emulated? 
is_from()'s parser looks relatively fragile.

I'm loathe to try to craft a patch that's specific to this one type,
and I don't know what a good authoritative reference is. If you'd
find it useful for me to do so, please let me know and I shall.

--jhawk

-- 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/gcc/lib/gcc-lib/sparc-sun-solaris2.9/3.2.1/specs
Configured with: ../src/configure --prefix=/usr/gcc --disable-shared
Thread model: posix
gcc version 3.2.1

- CFLAGS
-Wall -pedantic -g -O2

-- Mutt Version Information

Mutt 1.4.1i (2003-03-19)
Copyright (C) 1996-2002 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: SunOS 5.9 (sun4u) [using slang 10310]
Compile options:
-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/athena/bin/ispell"
SENDMAIL="/usr/lib/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/mit/sipb/share/mutt"
SYSCONFDIR="/mit/sipb/etc"
EXECSHELL="/bin/sh"
-MIXMASTER
To contact the developers, please mail to <mutt-dev@mutt.org>.
To report a bug, please use the flea(1) utility.



>How-To-Repeat:
>Fix:

Change History

Changed 6 years ago by Bob Bell <bobbell@…>

On Thu, Dec 05, 2002 at 11:48:59AM -0800, Michael Elkins <me@sigpipe.org> wrote:
> There has been some talk recently about making Mutt's mbox parsing less
> strict than it is right now.  This would involve:
> 
> - Consider any line starting with "From " to be a message separator
>   regardless of whether the rest of the line is parsable (return path
>   and date)
> 
> - ignore the Content-Length field
> 
> This would solve some of the portability issues that come up
> occasionally...

   I may have been part of that conversation.  I rather like that way
that mutt handles mbox folders.  It doesn't force me to have '>From
' lines and such in my email.  For me, the solution was to have procmail
generate a Content-Length header for incoming mail.

   At the least, I would want to have whether Content-Length is adhered
to or not be a configurable option.

-- 
Bob Bell <bobbell@zk3.dec.com>
-------------------------------------------------------------------------
"The computer should be doing the hard work.  That's what it's paid
 to do, after all."
  -- Larry Wall, creator of the Perl programming language

Changed 6 years ago by Edmund GRIMLEY EVANS <edmundo@…>

nv017001@sneakemail.com <nv017001@sneakemail.com>:

> I recently had problems with mutt reading a news article (saved
> to a file). It turned out that the poster uses an email address
> \xA0@\xA0.\xA0 and mutt seems to ignore the mailbox delimiter line
> 	From \xA0@\xA0.\xA0 ...
> 
> Is this a bug?

It's probably just an incompatibility between Mutt and whichever
program created the mail folder.

You might be able to make the mail folder readable by processing it
with formail, or you could just hack it with perl, replacing each line
that matches /^From / with a valid mbox separator.

Edmund

Changed 6 years ago by Edmund GRIMLEY EVANS <edmundo@…>

Michael Elkins <me@sigpipe.org>:

> There has been some talk recently about making Mutt's mbox parsing less
> strict than it is right now.  This would involve:
> 
> - Consider any line starting with "From " to be a message separator
>   regardless of whether the rest of the line is parsable (return path
>   and date)

This seems sensible. It seems to me that strict parsing of From_ lines
does more harm than good. For compatibility you still have to add '>'
to any line that starts with "From " when writing to a folder (unless
you are relying on Content-Length). If another program is failing to
escape From_ lines, then all your strict parsing does is hide a
potentially serious problem, with possible security implications,
making it more dangerous: if a message gets split at the start of a
paragraph of English text, then the user is going to know that there
is a bug, but if a message gets split at the start of a forwarded
message, or where someone is deliberately trying to deceive, then the
user might not realise what is happening and the bug might go
unreported.

> - ignore the Content-Length field

There should probably be some kind of option involved here. I can
think of at least three possible behaviours:

* Ignore the Content-Length altogether.

* Use the Content-Length, and if any value is found to be incorrect
report an error.

* Use the Content-Length, but if any value is found to be incorrect
quietly ignore it, and maybe ignore all values in that folder from
then onwards.

The third behaviour is perhaps too dangerous: if you are expecting to
use Content-Length, but you can't, then you are probably adding
messages that contain unescaped From_ lines, so you are corrupting
your own folders and you would really like to be told about this
situation.

I try to use MMDF with all new folders.

Edmund

Changed 6 years ago by Edmund GRIMLEY EVANS <edmundo@…>

Yusuf Goolamabbas <yusufg@outblaze.com>:

> Hi, When I download and gunzip the archives of the psyche-list
> 
> https://listman.redhat.com/pipermail/psyche-list/
> 
> mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail'
> command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody
> else seeing similar behaviour and can explain why this is so

The message separator lines seem to have been antispammed:

$ grep '^From ' 2002-September.txt | head -n 3
>From psyche-list at redhat.com  Mon Sep 30 18:01:01 2002
>From psyche-list at redhat.com  Mon Sep 30 18:06:00 2002
>From psyche-list at redhat.com  Mon Sep 30 18:31:05 2002

You can make the folders readable by Mutt by processing them like
this:

perl -pe 's/^(From psyche-list) at /$1\@/;' 2002-September.txt > 2002-September.txt2

The original files work with other mail clients becaue they are less
strict about parsing From_ lines, probably rightly so.

Edmund

Changed 6 years ago by Lars Hecking <lhecking@…>

Yusuf Goolamabbas writes:
> Package: mutt
> Version: 1.4i
> Severity: normal
> 
> -- Please type your report below this line
> Hi, When I download and gunzip the archives of the psyche-list
> 
> https://listman.redhat.com/pipermail/psyche-list/
> 
> mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail'
> command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody
> else seeing similar behaviour and can explain why this is so

I can confirm this for 1.4 and mutt-cvs. This is a weird one, as there
isn't anything obviously wrong with these mailing list archives.

Changed 6 years ago by Lars Hecking <lhecking@…>

Yusuf Goolamabbas writes:
> Package: mutt
> Version: 1.4i
> Severity: normal
> 
> -- Please type your report below this line
> Hi, When I download and gunzip the archives of the psyche-list
> 
> https://listman.redhat.com/pipermail/psyche-list/
> 
> mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail'
> command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody
> else seeing similar behaviour and can explain why this is so

I can confirm this for 1.4 and mutt-cvs. This is a weird one, as there
isn't anything obviously wrong with these mailing list archives.

Changed 6 years ago by Eduardo Pérez Ureta <eperez@…>

On 2002-12-16 10:06:42 +0000, Lars Hecking wrote:
> Yusuf Goolamabbas writes:
> > Package: mutt
> > Version: 1.4i
> > Severity: normal
> > 
> > -- Please type your report below this line
> > Hi, When I download and gunzip the archives of the psyche-list
> > 
> > https://listman.redhat.com/pipermail/psyche-list/
> > 
> > mutt 1.4i on Redhat 7.0/7.3/8.0 does not show any messages, the 'mail'
> > command on redhat 7.0/7.3/8.0 is able to read the mailboxes. Anybody
> > else seeing similar behaviour and can explain why this is so
>  
>  I can confirm this for 1.4 and mutt-cvs. This is a weird one, as there
>  isn't anything obviously wrong with these mailing list archives.

That's not an mbox. The From header is not correct.
The email address is not correct has " at " instead "@"

There's not bug in mutt but at redhat mailing lists https://listman.redhat.com/pipermail/

Changed 5 years ago by Alain Bench <veronatif@…>

# fixed long ago by Thomas
close 910
# not a bug
close 923
# weddings
merge 751 1463
merge 1407 1427
# could lead to data loss by misdirected replies
severity 1488 grave
# submitter agrees lowering
severity 1106 wishlist
tags 1231 patch
tags 1362 patch
tags 1406 patch
retitle 1623 dummy bug for testing retitle -- ignore
-- I wonder why
my inline #comments disapeared.

Changed 5 years ago by Alain Bench <veronatif@…>

# no infos, no followups
close 1032
close 1394
merge 1200 1407
severity 1022 wishlist
severity 1608 wishlist
merge 1022 1579 1608
tags 1022 patch
merge 1199 1517
tags 1481 patch
tags 1550 patch

Changed 5 years ago by Alain Bench <veronatif@…>

Hello, and thank you for the report.

On Sunday, January 4, 2004 at 6:03:13 AM -0500, jhawk@MIT.EDU wrote:

> Mutt fails to properly read mbox-format files with From lines like:
>| From dtucker at zip.com.au  Thu Jan  1 11:19:33 2004

   Yes. Same bug as #1427 merged with 1200/1407, I will merge this one
too. See there discussion about workarounds and future fixes. The BTS is
at <URL:http://bugs.guug.de/db/pa/lmutt.html>.


> I'm loathe to try to craft a patch that's specific to this one type,
> and I don't know what a good authoritative reference is. If you'd find
> it useful for me to do so, please let me know and I shall.

   Thanks. But perhaps don't bother: I have a half working patch to
is_from() in testing phase. It's very simple, no much more code than is
there now, but fixes at best the 4 bugs. Still has 2 problems to polish
before release.


Bye!	Alain.
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Changed 5 years ago by Alain Bench <veronatif@…>

severity 1613 wishlist
merge 800 1613
merge 1427 1747
severity 1765 wishlist
merge 1603 1765
tags 1334 patch
tags 1642 patch
tags 1778 patch
-- are 1662/1663 fixed and closable?

Changed 3 years ago by rado

  • status changed from new to assigned
pretty old, asking for update

Changed 3 years ago by rado

- Does this apply to current versions?
- Please provide a more detailed report with more background info what you've setup, are doing and trying to achieve.

Changed 3 years ago by Alain Bench <veronatif@…>

On Saturday, August 20, 2005 at 4:06:44 PM +0200, Rado Smiljanic wrote:

> Synopsis: Some mailbox doesn't work at all.
> Does this apply to current versions?

    Yes until 1.5.10.


> Please provide a more detailed report with more background info what
> you've setup, are doing and trying to achieve.

    Not needed, more than full info in the bugs. This is 4 merged bugs:

bug#1200: mutt-1.3.27i: Some mailbox doesn't work at all.
bug#1407: mutt-1.5.1i: strange behavior when email address contains 0xA0 's
bug#1427: mutt-1.4i: Unable to read any of the psyche-list archives mailboxes
bug#1747: mutt-1.4.1i: Mutt doesn't like some ^From mailbox seperators (esp. with "at")

    It's all about From_ line format over-strict expectations in Mutt.


Bye!	Alain.
-- 
Mutt muttrc tip for mailing lists: set followup_to=yes and declare the list as
 - subscribe ^list@ddress$ if you are subscribed and don't want courtesy copy.
 - lists ^list@ddress$     if you are not subscribed or want a courtesy copy.

Changed 3 years ago by ab

  • status changed from assigned to assigned
On Saturday, August 20, 2005 at 4:06:44 PM +0200, Rado Smiljanic wrote:

    Add all reporters to notifieds, deduppe unform, tag
analysed, and retitle from "Some mailbox doesn't work at
all."

Changed 3 years ago by ab

add flea/2247 submitter to notifieds

Changed 19 months ago by jhawk

  • cc changed from nv017001@sneakemail.com, yusufg@outblaze.com, jhawk@mit.edu, seth.arnold@suse.de to nv017001@sneakemail.com, yusufg@outblaze.com, jhawk@mit.edu, seth.arnold@suse.de

Is this bug supposed to be fixed?

1.5.15 continues to fail on mailman/pipermail archives, like this one:

http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January.txt

I offered to craft a patch in Jan. 2004 and the impression I had was that the mutt developers were pursuing a solution. But I renew my offer -- shall I craft a patch?

--jhawk@…

John Hawkinson

Changed 6 months ago by John Hawkinson

Seems about time to renew my yearly query on this (no chance
of getting it in 1.6, I guess?), since it doesn't look like
my inquiry from May 2007 got looked at?

Is someone working on this? I'm still happy to...

Thanks.

--jhawk@mit.edu
  John Hawkinson


Mutt <fleas@mutt.org> wrote on Tue, 29 May 2007
at 02:26:55 -0000 in <076.2729bc913ea884d36c864d0d2304171b@mutt.org>:


> Sender: fleas@mutt.org
> X-Trac-Version: 0.10.3
> Cc: mutt-dev@mutt.org, nv017001@sneakemail.com, yusufg@outblaze.com,
> 	seth.arnold@suse.de
> To: nlsn@free.fr, veronatif@free.fr, edmundo@rano.org, bobbell@zk3.dec.com,
> 	lhecking@nmrc.ie, eperez@it.uc3m.es, jhawk@mit.edu
> X-Trac-Project: Mutt
> Date: Tue, 29 May 2007 02:26:55 -0000
> Reply-To: fleas@mutt.org
> Subject: Re: [Mutt] #1200: mbox From_ line format over-strict expectations
> X-Trac-Ticket-URL: http://dev.mutt.org/trac/ticket/1200#comment:17
> Message-ID: <076.2729bc913ea884d36c864d0d2304171b@mutt.org>
> X-Trac-Ticket-ID: 1200
> In-Reply-To: <067.c5fb525363f1c37cf06b40d94a292f8c@mutt.org>
> X-bts2muttdev: gateway
> X-Debbugs-No-Ack: please
> X-Delivery-Agent: TMDA/1.1.11 (Ladyburn)
> From: Mutt <fleas@mutt.org>
> Mail-Followup-To: fleas@mutt.org
> X-Spam-Score: 0.13
> 
> #1200: mbox From_ line format over-strict expectations
> 
> Comment (by jhawk):
> 
>  Is this bug supposed to be fixed?
> 
>  1.5.15 continues to fail on mailman/pipermail archives, like this one:
> 
>  http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January.txt
> 
>  I offered to craft a patch in Jan. 2004 and the impression I had was that
>  the mutt developers were pursuing a solution. But I renew my offer --
>  shall I craft a patch?
> 
>  --jhawk@mit.edu
>    John Hawkinson
> 
> -- 
> Ticket URL: <http://dev.mutt.org/trac/ticket/1200#comment:17>

Changed 6 months ago by jhawk

  • cc nv017001@…, seth.arnold@… removed
  • version changed from 1.5.10 to 1.5.17

Remove bouncing emails (seth.arnold@…, nv017001@…). Note it still fails in 1.5.17.

Note: See TracTickets for help on using tickets.