mutt: 6 new changesets

[Brendan Cully]

6 new changesets in mutt:

http://dev.mutt.org/hg/mutt/rev/87ef3e3550e4
changeset:   5626:87ef3e3550e4
branch:  HEAD
tag: tip
user:Brendan Cully 
date:Fri Jan 02 23:13:43 2009 -0800
summary: SMTP: Use Hostname if Fqdn is bogus. Closes #3142.

http://dev.mutt.org/hg/mutt/rev/37ed3cc8d40c
changeset:   5625:37ed3cc8d40c
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 22:37:42 2009 -0800
summary: More tyops

http://dev.mutt.org/hg/mutt/rev/492c53436274
changeset:   5624:492c53436274
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 22:35:33 2009 -0800
summary: Tyops

http://dev.mutt.org/hg/mutt/rev/7d0583e0315d
changeset:   5623:7d0583e0315d
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 19:05:21 2009 -0800
summary: Add SSL intermediate certificate support for gnutls

http://dev.mutt.org/hg/mutt/rev/3af7e8af1983
changeset:   5622:3af7e8af1983
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 13:50:11 2009 -0800
summary: Simplify intermediate certificate handling.

http://dev.mutt.org/hg/mutt/rev/5db868a874b6
changeset:   5621:5db868a874b6
branch:  HEAD
user:TAKAHASHI Tamotsu 
date:Fri Jan 02 12:46:22 2009 -0800
summary: Add support for intermediate certificates to openssl code.

-- 
Repository URL: http://dev.mutt.org/hg/mutt

Copyright years

[Vincent Lefevre]

Hi,

Some files have been modified, but their copyright years.
Some copyright years in main.c should also be updated:

static const char *Notice = N_("\
Copyright (C) 1996-2008 Michael R. Elkins and others.\n\
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.\n\
Mutt is free software, and you are welcome to redistribute it\n\
under certain conditions; type `mutt -vv' for details.\n");

static const char *Copyright = N_("\
Copyright (C) 1996-2007 Michael R. Elkins \n\
Copyright (C) 1996-2002 Brandon Long \n\
Copyright (C) 1997-2007 Thomas Roessler \n\
Copyright (C) 1998-2005 Werner Koch \n\
Copyright (C) 1999-2008 Brendan Cully \n\
Copyright (C) 1999-2002 Tommi Komulainen \n\
Copyright (C) 2000-2002 Edmund Grimley Evans \n\
Copyright (C) 2006-2008 Rocco Rutte \n\

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

[Mutt] #3145: atoi() is not safe (undefined behavior if value is not representable)

[Mutt]

#3145: atoi() is not safe (undefined behavior if value is not representable)
+---
 Reporter:  vinc17  |   Owner:  mutt-dev
 Type:  defect  |  Status:  new 
 Priority:  major   |   Milestone:  
Component:  mutt| Version:  1.5.18  
 Keywords:  |  
+---
 Mutt uses the standard atoi() function in some number of places. But this
 function can have undefined behavior in case of error, e.g. if the value
 cannot be represented:

   7.20.1  String conversion functions

   [1]  The  functions  atof,  atoi,  atol,  and atoll need not
   affect the value of  the  integer  expression  errno  on  an
   error.   If  the  value of the result cannot be represented,
   the behavior is undefined.

 atoi may be safe in some cases, but this is not documented. Sometimes it
 isn't at all (e.g. in smtp.c), with a possible security problem. strtol
 should be used instead, with proper error checking, to avoid things like
 memory corruption, crashes and so on.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: Copyright years

[Thomas Dickey]

On Sat, 3 Jan 2009, Vincent Lefevre wrote:


Hi,

Some files have been modified, but their copyright years.
Some copyright years in main.c should also be updated:

static const char *Notice = N_("\
Copyright (C) 1996-2008 Michael R. Elkins and others.\n\
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.\n\
Mutt is free software, and you are welcome to redistribute it\n\
under certain conditions; type `mutt -vv' for details.\n");

static const char *Copyright = N_("\
Copyright (C) 1996-2007 Michael R. Elkins \n\
Copyright (C) 1996-2002 Brandon Long \n\
Copyright (C) 1997-2007 Thomas Roessler \n\
Copyright (C) 1998-2005 Werner Koch \n\
Copyright (C) 1999-2008 Brendan Cully \n\
Copyright (C) 1999-2002 Tommi Komulainen \n\
Copyright (C) 2000-2002 Edmund Grimley Evans \n\
Copyright (C) 2006-2008 Rocco Rutte \n\


from casual reading of the list, this appears up to date (unless you're
referring to someone who's been overlooked).  It would help if you
pointed out which is the case.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Re: Copyright years

[Vincent Lefevre]

On 2009-01-03 08:50:52 -0500, Thomas Dickey wrote:
> from casual reading of the list, this appears up to date (unless you're
> referring to someone who's been overlooked).  It would help if you
> pointed out which is the case.

There have been some changes in 2009 (see "hg log" output).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Re: [Mutt] #3145: atoi() is not safe (undefined behavior if value

[Rocco Rutte]

Hi,

* Mutt wrote:

#3145: atoi() is not safe (undefined behavior if value is not representable)


I have a patch adding strtol wrappers. I'll polish it up and attach to
the ticket.

Rocco

Re: [Mutt] #3145: atoi() is not safe (undefined behavior if value

[Mutt]

#3145: atoi() is not safe (undefined behavior if value is not representable)
-+--
  Reporter:  vinc17  |   Owner:  mutt-dev
  Type:  defect  |  Status:  new 
  Priority:  major   |   Milestone:  
 Component:  mutt| Version:  1.5.18  
Resolution:  |Keywords:  
-+--

Comment(by Rocco Rutte):

 {{{
 Hi,

 * Mutt wrote:

 I have a patch adding strtol wrappers. I'll polish it up and attach to
 the ticket.

 Rocco
 }}}

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: mutt: 6 new changesets

[Rocco Rutte]

Hi,

* Brendan Cully wrote:


http://dev.mutt.org/hg/mutt/rev/37ed3cc8d40c
changeset:   5625:37ed3cc8d40c
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 22:37:42 2009 -0800
summary: More tyops

http://dev.mutt.org/hg/mutt/rev/492c53436274
changeset:   5624:492c53436274
branch:  HEAD
user:Brendan Cully 
date:Fri Jan 02 22:35:33 2009 -0800
summary: Tyops


Thanks for fixing these. I was about to fix them myself along with other
minor fixes.

Rocco

Re: [Mutt] #3140: ignore old flag set by other mail clients

[Mutt]

#3140: ignore old flag set by other mail clients
--+-
  Reporter:  adrian13 |   Owner:  mutt-dev
  Type:  enhancement  |  Status:  new 
  Priority:  minor|   Milestone:  2.0 
 Component:  mutt | Version:  
Resolution:   |Keywords:  patch   
--+-
Changes (by brendan):

  * milestone:  => 2.0


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3139: certificate problems in 1.5.18 nightly

[Mutt]

#3139: certificate problems in 1.5.18 nightly
-+--
  Reporter:  balderdash  |   Owner:  mutt-dev
  Type:  defect  |  Status:  new 
  Priority:  major   |   Milestone:  1.6 
 Component:  mutt| Version:  
Resolution:  |Keywords:  
-+--
Changes (by brendan):

  * milestone:  => 1.6


Comment:

 I can't reproduce this. Can you try using an empty .muttcerts when running
 the snapshot, then comparing the new .muttcerts to your original file
 after you've accepted certs?

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3140: ignore old flag set by other mail clients

[Mutt]

#3140: ignore old flag set by other mail clients
--+-
  Reporter:  adrian13 |   Owner:  brendan
  Type:  enhancement  |  Status:  new
  Priority:  minor|   Milestone:  2.0
 Component:  IMAP | Version: 
Resolution:   |Keywords:  patch  
--+-
Changes (by brendan):

  * owner:  mutt-dev => brendan
  * component:  mutt => IMAP


Comment:

 I'm going to defer this until after 1.6. The approach you've taken is a
 bit hackish, I'm afraid. It might be better to ignore `Status: O` iff the
 server supports custom persistent IMAP flags (this is how mutt marks
 messages old). But I'm afraid that this might not be enough for some
 environments, so I think such a patch needs a testing window.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [PATCH] Create a "cd" command to change the current directory

[Brendan Cully]

On Sunday, 28 December 2008 at 14:34, Adeodato Simó wrote:
> Hello! (Long time no see, heh.)
> 
> I'd very grateful if the attached patch could be considered for
> inclusion. It adds a very simple "cd" command that changes the current
> working directory of the Mutt process.
> 
> I've missed this eg. when receiving a patch over email, wanting to apply
> it with git-apply(1), and failing because Mutt was not started in the
> right directory. It's easier to :cd from Mutt, than to quit, cd from the
> shell *and* find the message again.

--git-dir? --directory? (I don't use git, but I do this all the time
from mutt to hg with "|hg -R /path/to/repo import -")

> If you don't find this command suitable for inclusion, please let me
> know why. :-)

I think it's a good idea, but it'll have to queue up behind bug
fixes. It would be nice to try to clean up other path handling warts
(LastDir vs attachments, local vs IMAP) when we do this.

Re: mutt: 11 new changesets

[Brendan Cully]

On Thursday, 18 December 2008 at 15:12, Rocco Rutte wrote:
> Hi,
>
> * Brendan Cully wrote:
>
>> http://dev.mutt.org/hg/mutt/rev/7b46e23ae476
>> changeset:   5607:7b46e23ae476
>> branch:  HEAD
>> user:Erik Hovland 
>> date:Tue Dec 16 12:53:19 2008 -0800
>> summary: Remove redundant int clamping
>
> I think this change is actually wrong. The sign of a%b in C is
> machine-dependent for negative values. Thus,
>
>h = (h * SOMEPRIME) % n;
>h = (h >= 0) ? h : h + n;
>
> ensures that h is always positive. So at least the former line needs to
> go in again or it must be sure that the final return value is in the
> range 0..n-1.

Sorry, I forgot to reply to this earlier. I think since h is now
unsigned, h * SOMEPRIME is unsigned and so (h * SOMEPRIME) % n will
also be signed. (n should never be negative -- I am not sure why it
isn't typed as unsigned).

We might also want to use a better hash function -- there are many
available. In fact, I'll look into that now.

Re: [PATCH] Create a "cd" command to change the current directory

[David Champion]

> I think it's a good idea, but it'll have to queue up behind bug
> fixes. It would be nice to try to clean up other path handling warts
> (LastDir vs attachments, local vs IMAP) when we do this.

Alongside a cd I'd like to see a pushd/popd.  Cd could even be the pushd
operation.  Personally I don't care how deep the stack is or whether
it's finite at all.  The most common use case only needs a depth of 1.

I have a generic variable-stacking patch I could dredge up if the
stack-handling code is useful for this.  (Not that it'd be hard to write
from scratch, but who's not short on time?)

-- 
 -D.d...@uchicago.eduNSITUniversity of Chicago

Planning to release 1.5.19 Monday

[Brendan Cully]

Hi all,

I'd like to release 1.5.19 on Monday, so that I can concentrate on the
spate of nearly-identical IMAP segfault bugs still blocking 1.6, and
let more people bang on the new IMAP path canonicalization stuff. I'd
be grateful if people could bang on tip over the next 48 hours to help
prevent brown paper bag bugs. Translators are welcome to refresh now
as well.

Thanks!

(New year's resolution: more time for mutt)


pgpw9YSGIN6om.pgp
Description: PGP signature

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

[Mutt]

#3143: Segmentation fault in index menu with IMAP account
--+-
  Reporter:  debarshiray  |   Owner:  brendan 
  Type:  defect   |  Status:  assigned
  Priority:  major|   Milestone:  1.6 
 Component:  IMAP | Version:  1.5.18  
Resolution:   |Keywords:  
--+-
Changes (by brendan):

  * status:  new => assigned


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3074: Mutt hangs indefinitely

[Mutt]

#3074: Mutt hangs indefinitely
-+--
  Reporter:  jaymzh  |   Owner:  brendan   
  Type:  defect  |  Status:  new   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2938
-+--
Changes (by brendan):

  * keywords:  => duplicate 2938


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2935: Occasional segfault when IMAP inbox updates

[Mutt]

#2935: Occasional segfault when IMAP inbox updates
-+--
  Reporter:  skunk   |   Owner:  brendan   
  Type:  defect  |  Status:  assigned  
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * keywords:  => duplicate 2902


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2985: segfault in mx_update_context

[Mutt]

#2985: segfault in mx_update_context
-+--
  Reporter:  jukka   |   Owner:  brendan   
  Type:  defect  |  Status:  assigned  
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * keywords:  => duplicate 2902


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3028: mutt segfaults while moving messages from gmail

[Mutt]

#3028: mutt segfaults while moving messages from gmail
---+
  Reporter:  michele.zaffalon  |   Owner:  brendan   
  Type:  defect|  Status:  assigned  
  Priority:  major |   Milestone:  1.6   
 Component:  IMAP  | Version:  1.5.18
Resolution:|Keywords:  duplicate 2902
---+
Changes (by brendan):

  * keywords:  => duplicate 2902


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3041: imap fetch segfault

[Mutt]

#3041: imap fetch segfault
-+--
  Reporter:  chrisl  |   Owner:  brendan   
  Type:  defect  |  Status:  assigned  
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * keywords:  => duplicate 2902


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

[Mutt]

#3143: Segmentation fault in index menu with IMAP account
--+-
  Reporter:  debarshiray  |   Owner:  brendan   
  Type:  defect   |  Status:  assigned  
  Priority:  major|   Milestone:  1.6   
 Component:  IMAP | Version:  1.5.18
Resolution:   |Keywords:  duplicate 2902
--+-
Changes (by brendan):

  * keywords:  => duplicate 2902


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2935: Occasional segfault when IMAP inbox updates

[Mutt]

#2935: Occasional segfault when IMAP inbox updates
-+--
  Reporter:  skunk   |   Owner:  brendan   
  Type:  defect  |  Status:  started   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * status:  assigned => started


Comment:

 hdrs[msgcount - 1] should always be valid, and hdrs[msgcount] should never
 be -- hdrs is indexed from 0, and msgcount is the total number of headers.
 For example, if you have one message in your mailbox, hdrs[0] should be
 set, hdrs[1] should not be, and msgcount should be 1. This particular clue
 is, I'm afraid, a red herring.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: mutt: 11 new changesets

[Vincent Lefevre]

On 2009-01-03 13:57:03 -0800, Brendan Cully wrote:
> Sorry, I forgot to reply to this earlier. I think since h is now
> unsigned, h * SOMEPRIME is unsigned and so (h * SOMEPRIME) % n will
> also be signed. (n should never be negative -- I am not sure why it
  ^^ unsigned
> isn't typed as unsigned).

Perhaps consistency between types? Everywhere else in the code,
the type int seems to be used for hashes (not unsigned int).
Indeed one still has:

In hash.h:

typedef struct
{
  int nelem;
  struct hash_elem **table;
}
HASH;

In hash.c:

HASH *hash_create (int nelem)

and

  int h;
[...]
  h = hash_string ((unsigned char *) key, table->nelem);

In thread.c:

  int hash;
[...]
hash = hash_string ((unsigned char *) subjects->data,
ctx->subj_hash->nelem);

Also, with the current (lack of) comments in the code, it is a bit
difficult to see whether there can be a problem. For instance, say
that the hash_string() function returns a value between 0 and n-1.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

[Mutt]

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try 
reopening
the mailbox."
--+-
  Reporter:  neteler  |   Owner:  brendan 
  Type:  defect   |  Status:  assigned
  Priority:  major|   Milestone:  1.6 
 Component:  IMAP | Version:  1.5.16  
Resolution:   |Keywords:  
--+-

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3041: imap fetch segfault

[Mutt]

#3041: imap fetch segfault
-+--
  Reporter:  chrisl  |   Owner:  brendan   
  Type:  defect  |  Status:  assigned  
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:
Resolution:  |Keywords:  duplicate 2902
-+--

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2935: Occasional segfault when IMAP inbox updates

[Mutt]

#2935: Occasional segfault when IMAP inbox updates
-+--
  Reporter:  skunk   |   Owner:  brendan   
  Type:  defect  |  Status:  started   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

[Mutt]

#3143: Segmentation fault in index menu with IMAP account
--+-
  Reporter:  debarshiray  |   Owner:  brendan   
  Type:  defect   |  Status:  assigned  
  Priority:  major|   Milestone:  1.6   
 Component:  IMAP | Version:  1.5.18
Resolution:   |Keywords:  duplicate 2902
--+-

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3028: mutt segfaults while moving messages from gmail

[Mutt]

#3028: mutt segfaults while moving messages from gmail
---+
  Reporter:  michele.zaffalon  |   Owner:  brendan   
  Type:  defect|  Status:  assigned  
  Priority:  major |   Milestone:  1.6   
 Component:  IMAP  | Version:  1.5.18
Resolution:|Keywords:  duplicate 2902
---+

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2985: segfault in mx_update_context

[Mutt]

#2985: segfault in mx_update_context
-+--
  Reporter:  jukka   |   Owner:  brendan   
  Type:  defect  |  Status:  assigned  
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--

Comment(by Brendan Cully ):

 (In [2c7cf8d68d6d]) Ignore unexpected FETCH responses during
 imap_read_headers.
 Thanks to Chris Li for the excellent bug report in #3041.
 See #2902, #2935, #2985, #3028, #3041, #3143.
 With luck, this may close them. In truth, imap_read_headers
 is still a horrible kludge of duct tape and chicken wire.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

[Mutt]

#3143: Segmentation fault in index menu with IMAP account
--+-
  Reporter:  debarshiray  |   Owner:  brendan   
  Type:  defect   |  Status:  infoneeded
  Priority:  major|   Milestone:  1.6   
 Component:  IMAP | Version:  1.5.18
Resolution:   |Keywords:  duplicate 2902
--+-
Changes (by brendan):

  * status:  assigned => infoneeded


Comment:

 Can you retest against tip?

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3041: imap fetch segfault

[Mutt]

#3041: imap fetch segfault
-+--
  Reporter:  chrisl  |   Owner:  brendan   
  Type:  defect  |  Status:  started   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * status:  assigned => started


Comment:

 Can you retest against tip? Thanks.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

[Mutt]

#3143: Segmentation fault in index menu with IMAP account
--+-
  Reporter:  debarshiray  |   Owner:  brendan   
  Type:  defect   |  Status:  started   
  Priority:  major|   Milestone:  1.6   
 Component:  IMAP | Version:  1.5.18
Resolution:   |Keywords:  duplicate 2902
--+-
Changes (by brendan):

  * status:  assigned => started


-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2985: segfault in mx_update_context

[Mutt]

#2985: segfault in mx_update_context
-+--
  Reporter:  jukka   |   Owner:  brendan   
  Type:  defect  |  Status:  started   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--
Changes (by brendan):

  * status:  assigned => started


Comment:

 Can you retest against tip? Thanks.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2935: Occasional segfault when IMAP inbox updates

[Mutt]

#2935: Occasional segfault when IMAP inbox updates
-+--
  Reporter:  skunk   |   Owner:  brendan   
  Type:  defect  |  Status:  started   
  Priority:  major   |   Milestone:  1.6   
 Component:  IMAP| Version:  1.5.18
Resolution:  |Keywords:  duplicate 2902
-+--

Comment(by brendan):

 Can you retest against tip? Thanks.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

[Mutt]

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try 
reopening
the mailbox."
--+-
  Reporter:  neteler  |   Owner:  brendan
  Type:  defect   |  Status:  started
  Priority:  major|   Milestone:  1.6
 Component:  IMAP | Version:  1.5.16 
Resolution:   |Keywords: 
--+-
Changes (by brendan):

  * status:  assigned => started


Comment:

 Can you retest against tip? Thanks.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2951: mutt-1.5.16: smtp error 550 causes blocking

[Mutt]

#2951: mutt-1.5.16: smtp error 550 causes blocking
---+
  Reporter:  errordevelo...@gmail.com  |   Owner:  brendan   
  Type:  defect|  Status:  infoneeded
  Priority:  major |   Milestone:  1.6   
 Component:  SMTP  | Version:
Resolution:|Keywords:
---+
Changes (by brendan):

  * status:  assigned => infoneeded


Old description:

> {{{
>

> Package: mutt
> Version: 1.5.16
> Severity: normal
>
> -- Please type your report below this line
> I had this heppening a few times:
> after getting SMTP session error 550 i could not do anything,
> just had to correct the From field, but Mutt wouldnt react on any
> keystrokes,
> apart from ^C .
> i haven't got any extra debug msgs, sorry.
>

>
> -- System Information
> System Version: Linux 00110101 2.6.20-gentoo-r8-111 #7 SMP PREEMPT Wed
> Aug 29 23:56:20 UTC 2007 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
> 3800+ AuthenticAMD GNU/Linux
>
> -- 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
> x86_64-pc-linux-gnu-gcc
> Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/specs
> Configured with: /var/cache/etmp/portage/sys-
> devel/gcc-3.4.6-r2/work/gcc-3.4.6/configure --prefix=/usr
> --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.6
> --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/include
> --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.6
> --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.6/man
> --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.6/info --with-gxx-
> include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/include/g++-v3
> --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec
> --enable-nls --without-included-gettext --with-system-zlib --disable-
> checking --disable-werror --enable-secureplt --disable-libunwind-
> exceptions --enable-multilib --enable-java-awt=gtk --enable-
> languages=c,c++,java,objc,f77 --enable-shared --enable-threads=posix
> --enable-__cxa_atexit --enable-clocale=gnu
> Thread model: posix
> gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)
>
> - CFLAGS
> -Wall -pedantic -march=athlon64 -O2 -pipe
>
> -- Mutt Version Information
>
> Mutt 1.5.16 (2007-06-09)
> Copyright (C) 1996-2007 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.20-gentoo-r8-111 (x86_64)
> ncurses: ncurses 5.6.20061217 (compiled with 5.6)
> libidn: 0.6.5 (compiled with 0.6.5)
> Compile options:
> -DOMAIN
> -DEBUG
> -HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
> -USE_FCNTL  +USE_FLOCK   -USE_INODESORT
> -USE_POP  -USE_IMAP  +USE_SMTP  -USE_GSS  -USE_SSL_OPENSSL
> +USE_SSL_GNUTLS  +USE_SASL  +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/spool/mail"
> PKGDATADIR="/usr/share/mutt"
> SYSCONFDIR="/etc/mutt"
> EXECSHELL="/bin/sh"
> MIXMASTER="mixmaster"
> To contact the developers, please mail to .
> To report a bug, please visit http://bugs.mutt.org/.
>
> patch-1.5.16.sidebar.20070704.txt
>
> --- Begin /home/110101/.muttrc
> set folder=~/Mail/Mutt  # this is symlink virtualisation thingy ;]
> set sort=threads
> set collapse_unread=yes
> set sort_browser=alpha
> set sort_browser=reverse-alpha
> set folder_format="%t-%N ===%f  %s  %>:  %F %u:%g== "
> set quit=ask-no
> color hdrdefault blue white
> color quoted blue white
> color signature green white
> color attachment red white
> color message magenta white
> color error brightred white
> color indicator brightyellow brightblack
> color status white magenta
> color tree black white
> color normal black white
> color markers cyan white
> color search white black
> color tilde brightmagenta white
> color index blue white ~F
> color index brightgreen white "~N"
> color index green white "~O"
> color index brightmagenta white "~g|~G|~k"
> color header cyan white ^To:
> color header cyan white ^From:
> color header cyan white ^Sender:
> color header yellow white ^Subject:
> my_hdr X-ErrosOcured: N0N3
> my_hdr Face: :]\#
> set edit_headers=yes
> mailboxes uni imp inbox

Re: [Mutt] #2033: buffer overflow in attachment decoding function

[Mutt]

#2033: buffer overflow in attachment decoding function
---+
  Reporter:  pvalc...@openbsd.org  |   Owner:  mutt-dev 
  
  Type:  defect|  Status:  closed   
  
  Priority:  major |   Milestone:  1.6  
  
 Component:  mutt  | Version:  1.4.2 (stable) and 1.5.9 
(snapshot)
Resolution:  worksforme|Keywords:   
  
---+
Changes (by brendan):

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


Comment:

 I can't reproduce, I don't see the flaw (though that code is pretty
 obfuscated), and the submitter agrees that this bug can be closed.
 Removing from the 1.6 pile.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent

Re: [Mutt] #2966: Crash when opening encrypted message

[Mutt]

#2966: Crash when opening encrypted message
-+--
  Reporter:  intvnut |   Owner:  mutt-dev
  Type:  defect  |  Status:  closed  
  Priority:  major   |   Milestone:  1.6 
 Component:  mutt| Version:  1.5.16  
Resolution:  worksforme  |Keywords:  
-+--
Changes (by brendan):

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


Comment:

 Unreproducible.

-- 
Ticket URL: 
Mutt 
The Mutt mail user agent