[rt-users] Composed characters in email are not encoded

[Jesse Vincent]

On Sun, Apr 24, 2005 at 11:21:23PM +0200, Stephane Bortzmeyer wrote:
> RT does not encode (RFC 1522) the composed characters in the header of
> the email it sends:
> 
> Subject: [CODEV-NIC #80] Gestion des termes interdits et réservés 
> 
> Amavis complains (and rightly so):
> 
> X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char C3 hex) in message header 'Subject'
> 	Subject: ...] Gestion des termes interdits et r\303\251serv\303\251s \n
> 	^

Hm. I thought there was code specifically to deal with that. A patch
would be appreciated.


> 
> SpamAssassin thinks it's probably spam:
> 
> X-Spam-Report: 
> 	*  2.4 TO_HAS_SPACES To: address contains spaces
> 	*  2.7 SUBJ_ILLEGAL_CHARS Subject contains too many raw illegal characters
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Be sure to check out the RT Wiki at http://wiki.bestpractical.com
> 

--