I can elaborate a little more on the last paragraph. It is deletion

of the top level part direct under a message/rfc822 part which
gives problems because the headers of the message/rfc822 part have
to be changed in this case. It is hard to tell exactly how many
bytes and lines will be removed and added in this case.

If we can refrain from deletion of such parts and thus only allow
deletion of parts direct under a multipart part, then it is
relative easy always to make correct Content-Length: and Lines:
headers in the copy. (The correctness of the Lines count is
dependent of the correctness of the initial value, though).

(From: Byrial Jensen)

1 files changed, 2 insertions, 2 deletions

diff --git a/compose.c b/compose.c
index 235f1cbf..d35c9be8 100644
--- a/compose.c
+++ b/compose.c
@@ -383,7 +383,7 @@ int mutt_compose_menu (HEADER *msg,   /* structure for new message */
   int oldSort = Sort, oldSortAux = SortAux;
   struct stat st;
 
-  idx = mutt_gen_attach_list (msg->content, idx, &idxlen, &idxmax, 0, 1);
+  idx = mutt_gen_attach_list (msg->content, -1, idx, &idxlen, &idxmax, 0, 1);
 
   menu = mutt_new_menu ();
   menu->menu = MENU_COMPOSE;
@@ -477,7 +477,7 @@ int mutt_compose_menu (HEADER *msg,   /* structure for new message */
 	  for (i = 0; i < idxlen; i++)
 	    safe_free ((void **) &idx[i]);
 	  idxlen = 0;
-	  idx = mutt_gen_attach_list (msg->content, idx, &idxlen, &idxmax, 0, 1);
+	  idx = mutt_gen_attach_list (msg->content, -1, idx, &idxlen, &idxmax, 0, 1);
 	  menu->data = idx;
 	  menu->max = idxlen;
 	}