Re: mutt shows wrong size of message on mime messages
On Wednesday, 22 June 2011 at 08:35, jurri...@rivierenland.xs4all.nl wrote: From: David Champion d...@uchicago.edu Date: Tue, Jun 21, 2011 at 03:25:46PM -0500 * On 21 Jun 2011, Jurriaan wrote: on screen, I see things like 50 21-06-11 Xx Xxxx ( 1.2K) Xx x 51 21-06-11 Xxx (13433K) Xxxx The sizes of messages with mime components (mostly html messages) are much to big. Given that this is a router, without strace or gdb (well, Are you certain? That doesn't look too surprising for an HTML message with inline images. If I save the message to disk, it's only 13 kilobytes. There are no inline images, it a text-part and the same as html, but no images. I'll append the headers below. I'm not too sure I'd be happy receiving 133 megabytes messages... Have you tried copying it to another machine and running mutt on it there? Yes, on a regular AMD64 machine running Debian Unstable and mutt 1.5.21-5 from Debian, it shows as 13K in the index. There is no Content-Length field in the headers at all. Still, I think mutt is doing something to determine the length of the message - perhaps something else that just looking at the file. Might be related to this patch: https://dev.mutt.org/trac/changeset/5d96f24efa85 If you can rebuild mutt on your router, try reverting that.
mutt shows wrong size of message on mime messages
I have mutt running on a router ( a RouterStation Pro, to be exact).
Mutt 1.5.20 (2009-06-14)
Copyright (C) 1996-2009 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.6.32.27 (mips)
ncurses: ncurses 5.7.20081102 (compiled with 5.7)
Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL -USE_SETGID -USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK
+USE_POP +USE_IMAP -USE_SMTP
+USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO
+HAVE_REGCOMP +USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME
-EXACT_ADDRESS -SUN_ATTACHMENT
-ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
-HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE
-ISPELL
SENDMAIL=/usr/sbin/sendmail
MAILPATH=/var/mail
PKGDATADIR=/usr/share/mutt
SYSCONFDIR=/etc
EXECSHELL=/bin/sh
-MIXMASTER
in my /etc/Muttrc:
set index_format=%4C %Z %{%d-%m-%y} %-15.15L (%6c) %s
on screen, I see things like
50 21-06-11 Xx Xxxx ( 1.2K) Xx x
51 21-06-11 Xxx (13433K) Xxxx
The sizes of messages with mime components (mostly html messages) are
much to big. Given that this is a router, without strace or gdb (well,
they're theoretically available, but I don't have space on my flash to
install them), how can I debug this? Normal commands like ls work
flawlessly and show the proper file sizes. Before I go to the trouble
and cross-compile the latest mutt into a package I can install on this
architecture, I'd like to know if this is some sort of known problem.
I tried searching known bugs in mutt, but found nothing.
Thanks,
Jurriaan
Re: mutt shows wrong size of message on mime messages
* On 21 Jun 2011, Jurriaan wrote: on screen, I see things like 50 21-06-11 Xx Xxxx ( 1.2K) Xx x 51 21-06-11 Xxx (13433K) Xxxx The sizes of messages with mime components (mostly html messages) are much to big. Given that this is a router, without strace or gdb (well, Are you certain? That doesn't look too surprising for an HTML message with inline images. Have you tried copying it to another machine and running mutt on it there? -- David Champion • d...@uchicago.edu • IT Services • University of Chicago
Re: mutt shows wrong size of message on mime messages
On Tue, Jun 21, 2011 at 10:12:16PM +0200, Jurriaan wrote: The sizes of messages with mime components (mostly html messages) are much to big. Given that this is a router, without strace or gdb (well, Depending on the mailbox type, you may look at the Content-Length header field, and see if it looks wrong.
Re: mutt shows wrong size of message on mime messages
From: David Champion d...@uchicago.edu Date: Tue, Jun 21, 2011 at 03:25:46PM -0500 * On 21 Jun 2011, Jurriaan wrote: on screen, I see things like 50 21-06-11 Xx Xxxx ( 1.2K) Xx x 51 21-06-11 Xxx (13433K) Xxxx The sizes of messages with mime components (mostly html messages) are much to big. Given that this is a router, without strace or gdb (well, Are you certain? That doesn't look too surprising for an HTML message with inline images. If I save the message to disk, it's only 13 kilobytes. There are no inline images, it a text-part and the same as html, but no images. I'll append the headers below. I'm not too sure I'd be happy receiving 133 megabytes messages... Have you tried copying it to another machine and running mutt on it there? Yes, on a regular AMD64 machine running Debian Unstable and mutt 1.5.21-5 from Debian, it shows as 13K in the index. There is no Content-Length field in the headers at all. Still, I think mutt is doing something to determine the length of the message - perhaps something else that just looking at the file. Return-Path: oyst...@oysterband.co.uk Received: from pop.xs4all.nl by onderneming10.xs4all.nl with POP3 (fetchmail-6.3.14) for root@localhost (single-drop); Tue, 21 Jun 2011 18:24:06 +0200 (CEST) Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by mxdrop129.xs4all.nl (8.13.8/8.13.8) with ESMTP id p5LGL2s9002286 for thund...@xs4all.nl; Tue, 21 Jun 2011 18:21:04 +0200 (CEST) (envelope-from oyst...@oysterband.co.uk) Received: from host86-177-8-237.range86-177.btcentralplus.com (EHLO _192.168.1.65_) ([86.177.8.237]) by c2beaomr10.btconnect.com with ESMTP id DGV36915; Tue, 21 Jun 2011 17:20:18 +0100 (BST) Mime-Version: 1.0 Message-Id: p06240835ca26508262b1@[192.168.1.65] Date: Tue, 21 Jun 2011 17:17:14 +0100 To: oyst...@oysterband.co.uk From: oyst...@oysterband.co.uk Subject: Oysternews - June 2011 Content-Type: multipart/alternative; boundary=_-903449278==_ma X-Mirapoint-IP-Reputation: reputation=Poor-1, source=Queried, refid=tid=0001.0A0B0303.4E00C4BE.00E2, actions=tag X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2011.6.21.150915:17:8.510, ip=86.177.8.237, rules=__MIME_VERSION, __HAS_MSGID, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, NO_REAL_NAME, __CT, __CTYPE_MULTIPART_ALT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __TO_SAME_AS_FROM, __ANY_URI, __INT_PROD_ONLINE, __CP_URI_IN_BODY, __LINES_OF_YELLING, __HAS_HTML, HTML_NO_HTTP, BODY_SIZE_1_PLUS, BODYTEXTH_SIZE_1_LESS, __MIME_HTML, __TAG_EXISTS_HTML, RDNS_GENERIC_POOLED, HTML_50_70, FROM_SAME_AS_TO, RDNS_SUSP_GENERIC, RDNS_SUSP X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4E00C4D5.0169,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine X-Junkmail-IWF: false X-XS4ALL-DNSBL-Checked: mxdrop129.xs4all.nl checked 213.123.26.188 against DNS blacklists X-CNFS-Analysis: v=1.1 cv=xL5jk9sXKm39SpsYdNcr82C1o66kMlwr2Nm7bZal+6w= c=1 sm=0 a=kEbnFjf2cEUA:10 a=K6Ntl5L26ydyoV0739a08A==:17 a=mtkaXmQ8:8 a=aSRvjw2B:8 a=sHIh3Y_A:8 a=zLJGO5AY:8 a=U98ht5og:8 a=I20D6wHo:8 a=wrizyG0k:8 a=HhpTCGD2:8 a=GRzHY_bf:8 a=eR6-1q3x:8 a=HfyrKNce:8 a=4op6XsmP:8 a=z3B3hatJ:8 a=dR5Ukl99:8 a=fIpVGChO:8 a=hJqsIHQe:8 a=MdCgT5qH:8 a=2fvbXiwO:8 a=ktoeQTjK:8 a=6rq3X7HK:8 a=vmswM2Zr:8 a=x4d__Wq2:8 a=Km2ryu5w:8 a=RuyKgJuB:8 a=3j4BkbkP:8 a=_PMq8zET:8 a=4llNYCDgeoKaJu1OEyMA:9 a=O-cjF62q-FjmmYcXgPMA:7 a=wPNLvfGTeEIA:10 a=6kRK9SETbxkA:10 a=qbqIrQuHEgUA:10 a=zC9KXN8MXCXW_rJM:21 a=kukFqfnfpnJJ9kuZ:21 a=QUid0w6XvQMYMb6En90A:9 a=EYiheKTwF60SzJ5IYhAA:7 a=udQIuOo2nYMA:10 a=ztrDGr55cS9-V-nN:21 a=_xfDTva1TwfLhyb9:21 a=e6Lv1tFzlP879CmMbBnc9w==:117 X-Virus-Scanned: by XS4ALL Virus Scanner X-XS4ALL-Spam-Score: 0.5 () HTML_MESSAGE, XS_REPLACESTAR, XS_STARSPAM X-XS4ALL-Spam: NO X-Label: thund...@xs4all.nl --_-903449278==_ma Content-Type: text/plain; charset=iso-8859-1 ; format=flowed Content-Transfer-Encoding: quoted-printable Thanks, Jurriaan
Re: mutt shows wrong size of message on mime messages
From: Michael Elkins m...@sigpipe.org Date: Tue, Jun 21, 2011 at 01:27:26PM -0700 On Tue, Jun 21, 2011 at 10:12:16PM +0200, Jurriaan wrote: The sizes of messages with mime components (mostly html messages) are much to big. Given that this is a router, without strace or gdb (well, Depending on the mailbox type, you may look at the Content-Length header field, and see if it looks wrong. It's a maildir mailbox, and there's no Content-Length header. Thanks, Jurriaan
