<<< Date Index >>>     <<< Thread Index >>>

Re: mutt/2173: When replying to a message, Mutt should filter control characters from headers



The following reply was made to PR mutt/2173; it has been noted by GNATS.

From: TAKAHASHI Tamotsu <ttakah@xxxxxxxxxxxxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc: 
Subject: Re: mutt/2173: When replying to a message, Mutt should filter control 
characters from headers
Date: Sat, 4 Mar 2006 13:01:20 +0900

 Thanks for trying my patch.
 
 * Fri Mar  3 2006 Vincent Lefevre <vincent@xxxxxxxxxx>
 >  The ^M should also be replaced by '?', IMHO, at least in the Compose
 >  menu. I've not tried, but there may be the same problem with the ^[
 >  (Escape) character, where some escape sequences may corrupt the
 >  terminal, send a job to the printer and so on.
 
 Okay, you can replace "#if 0" with "#if 1" in the patch.
 That will filter out any unprintable characters.
 
 BTW, I'm afraid the same problem could be in rfc2231.c.
 If an attachment has an NL in its name, mutt will break
 the line like this:
 
 [-- Attachment #2: before_nl_
 _after_nl.txt --]
 [-- Type: text/plain, Encoding: 7bit, Size: 2.8K --]
 
 -- 
 tamo