On Mar 25, Jeremy Blosser [[EMAIL PROTECTED]] wrote:
> On Mar 25, Sven Guckes [[EMAIL PROTECTED]] wrote:
> > well, considering the amount of data this generates
> > mutt-dev isn't the place to take in such huge mails, either.
>
> mutt-dev is the place where the developers want the bugs to come so
On Mar 25, Sven Guckes [[EMAIL PROTECTED]] wrote:
> * Jeremy Blosser <[EMAIL PROTECTED]> [2002-03-20 03:23]:
> > Second, it is wrong as far as it goes. flea(1) doesn't send anything
> > to debian.org.
>
> SUBMIT="[EMAIL PROTECTED]"
> DEBIAN_SUBMIT="[EMAIL PROTECTED]"
>
> hmm... isn't DEBIAN
the place to take in such huge mails, either.
> In any case, people really should just use flea if they
> want to get a tracked resolution/not fall through the cracks.
ok - I'll just tell everybody to report bugs with "flea" then.
thanks for your feedback, Jeremy
On Mar 16, Sven Guckes [[EMAIL PROTECTED]] wrote:
> I have updated my text about reporting bugs and made it available as a
> separate page:
> http://www.math.fu-berlin.de/~guckes/mutt/bugrep.html
>
> Additions? Corrections? Feedback welcome!
The last sentence of the top section is:
"The repor
I have updated my text about reporting bugs
and made it available as a separate page:
http://www.math.fu-berlin.de/~guckes/mutt/bugrep.html
Additions? Corrections? Feedback welcome!
Sven
--
Sven [EMAIL PROTECTED] [mutt-versions] Latest versions:
MUTT http://www.mutt.org/ news:comp.mail.mu
* Ralph Geier <[EMAIL PROTECTED]> [011207 17:08]:
> I found the following bug in Mutt 1.2.5 / 1.3.24
> - first, save your 'mbox'-file (i.e. the folder
> where read mail is saved), it will be corrupted
> after trying the following!
> - assume you have 1 new message in your
> spool mailbox (i.
Jeez hombre..
Why didn't you send your photo album as well ?
Was the whole of your .muttrc required to compliment
the problem reported.
I for one won't be reading it.
--
Regards
Cliff
Ralph Geier muttered:
> I found the following bug in Mutt 1.2.5 / 1.3.24
>
> - first, save your 'mbox'-file (i.e. the folder where read mail is
> saved), it will be corrupted after trying the following!
>
> - assume you have 1 new message in your spool mailbox (i.e. incoming
> mail)
>
> - c
Hi,
On Fri, 07 Dec 2001 Ralph <[EMAIL PROTECTED]> spewed into the ether:
[-- snipped out 3460 lines !! --]
2 things -
* Please don't send such big attachments on the list. If you want
everyone to read a file, just put it up somewhere and post the link.
I have a dialup connection to the net, an
I found the following bug in Mutt 1.2.5 / 1.3.24
- first, save your 'mbox'-file (i.e. the folder where read mail is
saved), it will be corrupted after trying the following!
- assume you have 1 new message in your spool mailbox (i.e. incoming
mail)
- call mutt, have a look at the message, go
My system: SunOS 5.7 (sun4u)
The bug occurs when starting it up in dtterm or xterm_color, but not
xterm. After reading the mail mailbox, it seg-faults when trying to
display it (1 message header comes out before the crash). The
sysadmin just recently installed this. Could there have been a s
On Monday, 20 December 1999 at 13:22, Larry P . Schrof wrote:
> Mutt apparently does not honor the [ALERT] IMAP server response code.
> According to the IMAP RFC's, it must.
>
> Here's a log of the IMAP dialogue between my mutt client and the IMAP
> server. As you will see, the server is indeed i
Mutt apparently does not honor the [ALERT] IMAP server response code.
According to the IMAP RFC's, it must.
Here's a log of the IMAP dialogue between my mutt client and the IMAP
server. As you will see, the server is indeed issuing an ALERT on the
second-to-last line of the output.
--- BEGIN IMA
Hello,
I just compiled and installed mutt 1.0 (upgrading from mutt 1.0pre4)
and discovered a small bug in the use of colors. The 'default' color is
not recognized anymore. As a result, a lot of color settings I use are
now considered invallid :(
Below you find the output of 'mutt -v' for mutt 1.
++
version: mutt-1.0pre3
menu: main-menu
command: Reply
++
Hi Folks,
When trying to Reply to a message whose header doesnt have
( I have no idea how that happpened) Mutt-1.0pre3
Raju K V [[EMAIL PROTECTED]] wrote:
> On Fri, Sep 03, 1999 at 01:06:29PM -0500, Larry P . Schrof [[EMAIL PROTECTED]]
>wrote:
> > Hi. I'd like to submut a bug report. I looked around on the web for
> > information on the way to report the bug which is most helpful to th
Sven Guckes' page at:
http://www.math.fu-berlin.de/~guckes/mutt/
contains a section called "BugReport Guide".
HTH,
Raju
On Fri, Sep 03, 1999 at 01:06:29PM -0500, Larry P . Schrof [[EMAIL PROTECTED]] wrote:
> Hi. I'd like to submut a bug report. I looked around on the w
Larry P . Schrof [[EMAIL PROTECTED]] wrote:
> Hi. I'd like to submut a bug report. I looked around on the web for
> information on the way to report the bug which is most helpful to the
> dev team. I'm not convinved that the information I found is
> up-to-date. Could someon
Hi. I'd like to submut a bug report. I looked around on the web for
information on the way to report the bug which is most helpful to the
dev team. I'm not convinved that the information I found is
up-to-date. Could someone please post a URL or actually descibe
everything that should b
On 03/05/99 Michael Robinson uttered the following other thing:
> I'm using mutt-0.95.4, on a Solaris 2.6 machine, to talk to a
> Mircosoft sExchange server via IMAP. It all seems to work quite
> well.
>
> *But*, mutt won't allow me to change to a folder with a space in
> its name. Is this a de
I'm using mutt-0.95.4, on a Solaris 2.6 machine, to talk to a
Mircosoft sExchange server via IMAP. It all seems to work quite
well.
*But*, mutt won't allow me to change to a folder with a space in
its name. Is this a deliberate design decision?
-- michael.
Warning
Could not process message with given Content-Type:
multipart/signed; boundary=dDRMvlgZJXvWKvBx; micalg=pgp-sha1;protocol="application/pgp-signature"
Thus spake David Thorburn-Gundlach ([EMAIL PROTECTED]):
> I don't know much about the bugs list, but I did notice one thing in
> your email:
> % X-Mailer: Mutt 0.95.3i
[...]
> % Mutt 0.93.2 (1998-07-29)
> ...
>
> Which mutt are you actually using?
I'm using 0.95.3i here at work (or else Oec wou
Thus spake Thomas Roessler ([EMAIL PROTECTED]):
> > I considure this a bug. If it's an old one I'm sorry. I've
> > read the mutt FAQ by Fefe and the mutt fixes page by guckes. Didn't
> > find it there.
>
> It's fixed in 0.95.2.
Ok, thanks.
--
Andreas Jaekel, UNIX System Administration, Alcate
Warning
Could not process message with given Content-Type:
multipart/signed; boundary=LpQ9ahxlCli8rRTG; micalg=pgp-sha1;protocol="application/pgp-signature"
On 1999-02-18 14:47:05 +0100, Andreas Jaekel wrote:
> I considure this a bug. If it's an old one I'm sorry. I've
> read the mutt FAQ by Fefe and the mutt fixes page by guckes. Didn't
> find it there.
It's fixed in 0.95.2.
tlr
--
http://home.pages.de/~roessler/
Hi folks.
I'm new to mutt, so don't jump on me, please.
The advantage is that I have no complicated .muttrc you might
have to scan for errors.
I've startet mutt on a RedHat 5.2 system (the usual mutt RPM
is installed there) and read my mail. When finished, I hit 'q'
to quit mutt and was aksed we
27 matches
Mail list logo
