Re: Bug in mutt?

[Michelle Konzack]

Hello Michael Tatge,

Am 2011-04-09 16:31:11, hacktest Du folgendes herunter:
> * On Thu, Apr 07, 2011 01:39PM +0200 Michelle Konzack 
> (linux4miche...@tamay-dogan.net) muttered:
> > if I am in a IMAP folder and want to tag messages with
> > 
> > ~m 1-16500
> > 
> > mutt download useless 16.500 messages to tag them.
> 
> My best guess is you to add some header via imap_headers. Check color
> statements, spam stuff, etc.

No, there is nothing.  My "main" account on   does
add nothing.  My intranet server  yes.

But this has nothing to do with taging messages by number/count

I consider this as bug.

The same happen to deleting of messages...  WHY does mutt  download  and
re-upload the messages it I wan to delete it?  I have tried  it  from  a
simple perl-script using "lib-net-imap-ssl-perl" and it just works.

"mutt" does something wired and does NOT support correctly the  RFC  for
the IMAP protocol

> HTH,
> Michael

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de
ICQ#328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Bug in mutt?

[Michael Tatge]

* On Thu, Apr 07, 2011 01:39PM +0200 Michelle Konzack 
(linux4miche...@tamay-dogan.net) muttered:
> if I am in a IMAP folder and want to tag messages with
> 
> ~m 1-16500
> 
> mutt download useless 16.500 messages to tag them.

My best guess is you to add some header via imap_headers. Check color
statements, spam stuff, etc.

HTH,

Michael
-- 
Breadth-first search is the bulldozer of science.
-- Randy Goebel

PGP-Key-ID: 0xDC1A44DD
Jabber: init[0]@amessage.de

Bug in mutt?

[Michelle Konzack]

Hello ME and *,

if I am in a IMAP folder and want to tag messages with

~m 1-16500

mutt download useless 16.500 messages to tag them.  Can someone tell  me
WHY it is neccesary to download 580 MByte only to tag messges by number?

And now, if I want to move them, it download the messages again

Same is if I want to delete it.

I am on GSM and my HSPA "Flat-Rate" is  limited  to  5 GByte,  so  mutts
behaviour is VERY annoying bug.

Also the downloading it can not stoped except with killing mutt.

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Bug in mutt set index_format?

[John P. Verel]

On 03/11/01, 08:00:01PM -0500, Ken Weingold wrote:
> > > > folder-hook . set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"
> > > 
> > > Try the following instead:
> > > 
> > > folder-hook . 'set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"'
> > > 
> > > 
> > 
> > Note that order matters in folder hooks.  Be sure to set the default
> > one, e.g. the dot version as above, AFTER any specific folder settings
> > for expected behavior.
> 
> True, but I actually tried what he said and saw exactly what he was
> saying.  All the index displayed was the %4C.  Putting the single
> quotes around it fixed it.
> 
> 
> -Ken

Yep, he had the format wrong, for sure.  I just had a look in the on
line manual and there's nothing in there to show the use of quotes,
although that's how I do it, probably based on Sven's sample .muttrc. :)
Perhaps the manual could use and example using qoutes, no?
-- 
John P. Verel
Norwalk, CT

Re: Bug in mutt set index_format?

[John P. Verel]

On 03/11/01, 05:37:45PM -0500, Ken Weingold wrote:
> On Mon, Mar 12, 2001, Benjamin Hoyt wrote:
> > I may or may not have found a nastyish bug in Mutt, but here's my problem.
> > (I'm running Redhat 6.0 with kernel 2.2.5-15 and Mutt v0.95.4, and I'm a
> > relative newbie to Linux, not to mention Mutt).
> > 
> > In my ~/.muttrc if I have
> > 
> > set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"
> > 
> > everything works fine, but if I instead prefix that with a folder-hook and
> > have something like:
> > 
> > folder-hook . set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"
> 
> Try the following instead:
> 
> folder-hook . 'set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"'
> 
> 

Note that order matters in folder hooks.  Be sure to set the default
one, e.g. the dot version as above, AFTER any specific folder settings
for expected behavior.

Also, the current stable release of Mutt is 1.2.5.  You really should
upgrade.

Cheers.

John
> 
> -Ken
> 
> -- 
> [EMAIL PROTECTED]AIM: ScopusFest

-- 
John P. Verel
Norwalk, CT

Re: Bug in mutt set index_format?

[Ken Weingold]

On Mon, Mar 12, 2001, Benjamin Hoyt wrote:
> I may or may not have found a nastyish bug in Mutt, but here's my problem.
> (I'm running Redhat 6.0 with kernel 2.2.5-15 and Mutt v0.95.4, and I'm a
> relative newbie to Linux, not to mention Mutt).
> 
> In my ~/.muttrc if I have
> 
> set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"
> 
> everything works fine, but if I instead prefix that with a folder-hook and
> have something like:
> 
> folder-hook . set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"

Try the following instead:

folder-hook . 'set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"'



-Ken

-- 
[EMAIL PROTECTED]AIM: ScopusFest

Bug in mutt set index_format?

[Benjamin Hoyt]

I may or may not have found a nastyish bug in Mutt, but here's my problem.
(I'm running Redhat 6.0 with kernel 2.2.5-15 and Mutt v0.95.4, and I'm a
relative newbie to Linux, not to mention Mutt).

In my ~/.muttrc if I have

set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"

everything works fine, but if I instead prefix that with a folder-hook and
have something like:

folder-hook . set index_format="%4C %Z %{%b %d}  %-25.25L (%4l)  %s"

or

folder-hook outbox set index_format="%4C %Z %{%b %d}  %-25.25t (%4l)  %s"

It says "%Z: unknown variable" when loading up the folder (mailbox). It gets
past the %4C but dies on pretty much anything else (%Z, %{%b, etc), because
even a simple "%4C %Z" doesn't work, while "%4C" does.

What is happening? Is it a bug?

The reason I wanna do this is so that in my inbox it tells me who the msg is
from, but in the outbox who it's to (which makes sense).

Thanks for your time.


-- 
Benjamin Hoyt
[EMAIL PROTECTED]

Re: Bug in mutt 1.0.1i: ^C can freeze login session

[Michael Tatge]

On Tue, Apr 25, 2000 at 02:30:25PM -0700, David Kalins wrote:
> Version:  1.0.1i
> Menu: Compose
> Command(s):   f  and  c
> 
> When I have used the f command (to add an Fcc: value) or
> the c command (to add a Cc: value) and when I use Cnt-C
> to cancel before adding the Fcc: or Cc: value, mutt aborts
> and returns to the Unix shell prompt, but the session is
> thereupon frozen and no longer responds to anything done
> on the keyboard.

I just tried to reproduce this with mutt 1.1.11i under Linux. ^C leads
to the 'Exit Mutt? ([y]/n)' prompt, it doesn't freeze. The only odd
think that occurs is that when pressing 'y' to exit the string 'yes'
gets printed on a shell prompt, without any disturbing effect.
 
> I found it really easy to completely freeze my login session by
> using ^C to cancel out of adding an Fcc: or a Cc: value using the
> f or c commands while composing a message.  I know now the FAQ suggests
> using ^G, but ^C was the obvious choice to me as a Unix person.  I
> could imagine alot of people might get screwed up this way.

Well, in fact under Unix there is no standard for keyboard shortcuts.
Think of how programs use ALT vs. CTRL. With mutt it's kind of logical
to quit after ^C because that's what I would expect to happen. Many
known programs use ^G to escape out of a function, so I'm quite happy
with it.

Michael
-- 
Equal bytes for women.

PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65  40FA 5967 ACA1 0B57 7C13

Bug in mutt 1.0.1i: ^C can freeze login session

[David Kalins]

Version:  1.0.1i
Menu: Compose
Command(s):   f  and  c

When I have used the f command (to add an Fcc: value) or
the c command (to add a Cc: value) and when I use Cnt-C
to cancel before adding the Fcc: or Cc: value, mutt aborts
and returns to the unix shell prompt, but the session is
thereupon frozen and no longer responds to anything done
on the keyboard.

Ouput of "uname -a":

   SunOS socrates 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-Enterprise

Output of "mutt -v":

   Mutt 1.0.1i (2000-01-18)
   Copyright (C) 1996-2000 Michael R. Elkins and others.
   ...
   System: SunOS 5.6
   Compile options:
   -DOMAIN
   -HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
   -USE_IMAP  -USE_POP  +HAVE_REGCOMP  -USE_GNU_REGEX  +HAVE_COLOR  
   +HAVE_PGP2  -BUFFY_SIZE 
   -EXACT_ADDRESS  +ENABLE_NLS
   SENDMAIL="/usr/lib/sendmail"
   MAILPATH="/var/mail"
   SHAREDIR="/usr/local/mutt-1.0.1/lib/mutt"
   SYSCONFDIR="/usr/local/mutt-1.0.1/etc"
   ISPELL="/usr/local/bin/ispell"
   _PGPPATH="/usr/local/bin/pgp"
   _PGPV2PATH="/usr/local/bin/pgp"
   


I am not really a mutt user.  Our system socrates.berkeley.edu is
a multi-user multi-purpose system for use by UC Berkeley students,
faculty and staff.  A user requested we install mutt, so I did so
the other day.  While playing around with it in near total ignorance,
I found it really easy to completely freeze my login session by
using ^C to cancel out of adding an Fcc: or a Cc: value using the
f or c commands while composing a message.  I know now the FAQ suggests
using ^G, but ^C was the obvious choice to me as a unix person.  I
could imagine alot of people might get screwed up this way.

I didn't find any mention of this issue in Sven's list, but I may
have overlooked something.  Thanks in advance for any help you
may have for me.   --dk

David Kalins
Systems Administrator
Central Computing Services
UC Berkeley

Re: Bug in mutt for Solaris?

[Vikram Adukia]

When the attachment arrived at your work address, it was probably just
appended to your mail spool. A lot of mail agents, including mutt, simply
look for a the header:

>From 

in order to determine the start of a new message. Assuming that the
attachment was a plain-text file, mutt just interpreted all the "From"s in
there as the start of a new message.

A safer way of sending a file such as this would be to gzip it up and send
it along.

On Mon, Nov 29, 1999 at 08:20:06AM +0200, Marc Silver wrote:
> Hey there,
> 
> I think I've stumbled across an interesting bug in mutt for Solaris.
> I could be wrong, but that's why I'm posting to this list first... :)
> 
> Last night, I sent an email to my work email address, and with it,
> I attached my /var/mail/$USER file.  This morning, upon coming into
> work, I found that the mail I sent had been stripped of it's attachment,
> and that the contents had been added to my existing /var/mail/$USER
> file  is this a feature, because as far as I'm concerned, it's
> a bug that could potentially cause some damage.
> 
> Here is some info on the mutt client I'm using at work;
> 
> Mutt 1.0pre3i (1999-09-25)
> Copyright (C) 1996-9 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.6 [using slang 10003]
> Compile options:
> -DOMAIN
> -HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
> -USE_IMAP  -USE_POP  +HAVE_REGCOMP  -USE_GNU_REGEX  +HAVE_COLOR  +HAVE_PGP2  
>-BUFFY_SIZE 
> -EXACT_ADDRESS  +ENABLE_NLS
> SENDMAIL="/usr/lib/sendmail"
> MAILPATH="/var/mail"
> SHAREDIR="/usr/local/share/mutt"
> SYSCONFDIR="/usr/local/etc"
> ISPELL="/usr/local/bin/ispell"
> _PGPPATH="/usr/local/bin/pgp"
> _PGPV2PATH="/usr/local/bin/pgp"
> To contact the developers, please mail to <[EMAIL PROTECTED]>.
> 
> Any help on this would be much appreciated.
> Cheers,
> Marc
> 
> 
> -- 
> 
> Marc Silver
> IS Hosting Infrastructure
> The Internet Solution
> Tel: (+27 11) 283 5500
> Fax: (+27 11) 283 5001 
> E-mail: [EMAIL PROTECTED] 
> Web: www.is.co.za

-- 
Vikram Adukia
[EMAIL PROTECTED]
(847) 632-3407

Bug in mutt for Solaris?

[Marc Silver]

Hey there,

I think I've stumbled across an interesting bug in mutt for Solaris.
I could be wrong, but that's why I'm posting to this list first... :)

Last night, I sent an email to my work email address, and with it,
I attached my /var/mail/$USER file.  This morning, upon coming into
work, I found that the mail I sent had been stripped of it's attachment,
and that the contents had been added to my existing /var/mail/$USER
file  is this a feature, because as far as I'm concerned, it's
a bug that could potentially cause some damage.

Here is some info on the mutt client I'm using at work;

Mutt 1.0pre3i (1999-09-25)
Copyright (C) 1996-9 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.6 [using slang 10003]
Compile options:
-DOMAIN
-HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
-USE_IMAP  -USE_POP  +HAVE_REGCOMP  -USE_GNU_REGEX  +HAVE_COLOR  +HAVE_PGP2  
-BUFFY_SIZE 
-EXACT_ADDRESS  +ENABLE_NLS
SENDMAIL="/usr/lib/sendmail"
MAILPATH="/var/mail"
SHAREDIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
ISPELL="/usr/local/bin/ispell"
_PGPPATH="/usr/local/bin/pgp"
_PGPV2PATH="/usr/local/bin/pgp"
To contact the developers, please mail to <[EMAIL PROTECTED]>.

Any help on this would be much appreciated.
Cheers,
Marc


-- 

Marc Silver
IS Hosting Infrastructure
The Internet Solution
Tel: (+27 11) 283 5500
Fax: (+27 11) 283 5001 
E-mail: [EMAIL PROTECTED] 
Web: www.is.co.za

Re: I found a bug in mutt

[Shao Zhang]

It has nothing to do with mutt.

I believe if you press CTRL-s, it will have the same effect.

Try press CTRL-q to unlock your terminal...

Moritz Schmitt [[EMAIL PROTECTED]] wrote:
> Hi,
> 
> I use mutt 0.95.6i with ncurses 4.2 on Linux 2.2.10. I think I found a bug in 
> _this_ version (other versions I've never tried). If mutt is started and you 
> press CTRL-X-S mutt is dead. And if you want to kill the process from an other
> console it is not possible. Until a reboot you can't use this terminal (yes, 
> perhaps it is possible to kill and restart anything else to use this terminal
> again, but I' am new on Linux so I can't use this terminal until a reboot).
> 
> If this bug is already known, ignore this mail and excuse me, but I couldn't
> find something like list of all known bugs.
> 
> Greeting 
> Moritz
> 
> -- 
> Please USE ONLY my 2048-bit RSA key with
> this key-id: 4EB28E79 -- Key fingerprint: 
> 24 06 88 DF 56 91 89 57  
> 72 00 2E 98 9C EB B0 EE
> 



-- 

Shao Zhang - Running Debian 2.1  ___ _   _
Department of Communications/ __| |_  __ _ ___  |_  / |_  __ _ _ _  __ _ 
University of New South Wales   \__ \ ' \/ _` / _ \  / /| ' \/ _` | ' \/ _` |
Sydney, Australia   |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, |
Email: [EMAIL PROTECTED]  |___/ 
_

Re: I found a bug in mutt

[Dirk Pirschel]

On Sun, 31 Oct 1999, Moritz Schmitt wrote:

> I use mutt 0.95.6i with ncurses 4.2 on Linux 2.2.10. I think I found a bug in 
> _this_ version (other versions I've never tried). If mutt is started and you 
> press CTRL-X-S mutt is dead. And if you want to kill the process from an other
> console it is not possible. Until a reboot you can't use this terminal (yes, 
> perhaps it is possible to kill and restart anything else to use this terminal
> again, but I' am new on Linux so I can't use this terminal until a reboot).

This is not a bug!
Ctrl-s suspends the terminal, press Ctrl-q to resume.


CU
Dirk

-- 
Dirk Pirschel
E-Mail: [EMAIL PROTECTED] (PGP key on request)

"Microsoft has been doing a really bad job on their OS." -- Linus Torvalds

Addendum: I found a bug in mutt

[Moritz Schmitt]

Hi,

it's me again...

In my last mail I told that you have to reboot your system if you want to use
the dead terminal again. I didn't checked it it is not possible to reboot.
I've waited for ca. 5 minutes but Linux didn't reboot.

Greetings
Moritz
-- 
Please USE ONLY my 2048-bit RSA key with
this key-id: 4EB28E79 -- Key fingerprint: 
24 06 88 DF 56 91 89 57  
72 00 2E 98 9C EB B0 EE


 PGP signature

Re: I found a bug in mutt

[Ronny Haryanto]

On 31-Oct-1999, Moritz Schmitt wrote:
> I use mutt 0.95.6i with ncurses 4.2 on Linux 2.2.10. I think I found a bug in 
> _this_ version (other versions I've never tried). If mutt is started and you 
> press CTRL-X-S mutt is dead.

Hmm.. I found this by accident, not exactly in mutt but in a bash
prompt in xterm. If you press Ctrl-S it enters some kind of a
"no-echo" state (that's what I call it anyway), you can quit with
Ctrl-Q. You might want to give that a try.

Like I said I found this by accident, don't ask me what or why :)

-- 
Ronny Haryanto <[EMAIL PROTECTED]>

I found a bug in mutt

[Moritz Schmitt]

Hi,

I use mutt 0.95.6i with ncurses 4.2 on Linux 2.2.10. I think I found a bug in 
_this_ version (other versions I've never tried). If mutt is started and you 
press CTRL-X-S mutt is dead. And if you want to kill the process from an other
console it is not possible. Until a reboot you can't use this terminal (yes, 
perhaps it is possible to kill and restart anything else to use this terminal
again, but I' am new on Linux so I can't use this terminal until a reboot).

If this bug is already known, ignore this mail and excuse me, but I couldn't
find something like list of all known bugs.

Greeting 
Moritz

-- 
Please USE ONLY my 2048-bit RSA key with
this key-id: 4EB28E79 -- Key fingerprint: 
24 06 88 DF 56 91 89 57  
72 00 2E 98 9C EB B0 EE


 PGP signature

Bug in mutt, or, more likely, ncurses?

[Mike Dowling]

I have just down loaded and compiled mutt-0.95.7i, but it issues
segmentation faults when executed.  The relevant strace output is:

read(3, "\7\0\r\0\33[%i%p1%d;%p2%dr\0\33[3g\0\33[H\33[J"..., 720) = 720
close(3)= 0
ioctl(1, TCGETS, {B9600 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B9600 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=30, ws_col=132, ws_xpixel=0, ws_ypixel=0})
= 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


There is no problem if compiled with the --with-slang configure
parameter.  I have recently upgraded my libc, and with it ncurses. so
that my new ncurses.so.5.0 is untested.

Comments would be appreciated.

Cheers,
  Mike Dowling

-- 
Dr. Michael L. Dowling
Abteilung für Mathematische Optimierung
TU Braunschweig, Pockellsstraße 14
38106 Braunschweig, Germany