Re: [Mutt] #3328: mutt should handle unencoded whitespace in

To: antonio@xxxxxxxx, vincent@xxxxxxxxxx
Subject: Re: [Mutt] #3328: mutt should handle unencoded whitespace in
From: Mutt <fleas@xxxxxxxx>
Date: Mon, 07 Sep 2009 01:10:59 -0000
Auto-submitted: auto-generated
Cc: mutt-dev@xxxxxxxx, 497171@xxxxxxxxxxxxxxx
In-reply-to: <048.4af35b188c1fc0595aa1c81cff5ff3e6@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: <048.4af35b188c1fc0595aa1c81cff5ff3e6@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3328: mutt should handle unencoded whitespace in Q-coded strings
-------------------------------+--------------------------------------------
  Reporter:  antonio@xxxxxxxx  |       Owner:  mutt-dev
      Type:  enhancement       |      Status:  new     
  Priority:  trivial           |   Milestone:          
 Component:  mutt              |     Version:  1.5.20  
Resolution:                    |    Keywords:          
-------------------------------+--------------------------------------------
Changes (by vinc17):

 * cc: vincent@xxxxxxxxxx (added)


Comment:

 IMHO, this should be closed as invalid (what if the user really wants to
 write something like "=?us-ascii?Q?"?).

 It the user wants to handle such broken cases, he can use a tool like
 procmail.

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

References:
- [Mutt] #3328: mutt should handle unencoded whitespace in Q-coded strings
  - From: Mutt

Prev by Date: Re: [Mutt] #3325: attachment type misdetection for small .tar.gz
Next by Date: Re: [Mutt] #3330: wrong charset when editing message with headers
Previous by thread: [Mutt] #3328: mutt should handle unencoded whitespace in Q-coded strings
Next by thread: Re: [Mutt] #3328: mutt should handle unencoded whitespace in
Index(es):
- Date
- Thread