Re: [Mutt] #3108: Mutt 1.5.18 "could not copy message"

To: m.ashley@xxxxxxxxxxx, mutt-trac@xxxxxxxxxxxxxx, brendan@xxxxxxxxxx, cb@xxxxxxxx, sertac.liste@xxxxxxxxx, ttakah@xxxxxxxxxxxxxxxxx
Subject: Re: [Mutt] #3108: Mutt 1.5.18 "could not copy message"
From: Mutt <fleas@xxxxxxxx>
Date: Mon, 17 Nov 2008 04:30:12 -0000
Auto-submitted: auto-generated
Cc: mutt-dev@xxxxxxxx
In-reply-to: <036.549e959f00d806017021190b7a4f3bde@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <036.549e959f00d806017021190b7a4f3bde@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3108: Mutt 1.5.18 "could not copy message"
---------------------+------------------------------------------------------
  Reporter:  mcba    |       Owner:  mutt-dev
      Type:  defect  |      Status:  new     
  Priority:  major   |   Milestone:          
 Component:  mutt    |     Version:  1.5.18  
Resolution:          |    Keywords:  patch   
---------------------+------------------------------------------------------

Comment(by brendan):

 I wonder if changeset [f5fe657f0633] helps with this. Can you try a
 current nightly (see http://dev.mutt.org/nightlies/) and report how it
 handles these messages?

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3108#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

References:
- [Mutt] #3108: Mutt 1.5.18 "could not copy message"
  - From: Mutt

Prev by Date: Re: inconsistent expansion of mailbox shortcuts
Next by Date: Re: [PATCH] avoid full documentation
Previous by thread: Re: [Mutt] #3108: Mutt 1.5.18 "could not copy message"
Next by thread: Re: [Mutt] #3108: Mutt 1.5.18 "could not copy message"
Index(es):
- Date
- Thread