[Nms-cgi-devel] Re: [Nms-cgi-support] TFMail - non ascii chars in realname_input

[Jonathan S. <jn...@ge...>]

On Mon, 2005-10-17 at 15:18, Konstantine wrote:

> I am using TFMail v1.36 
> NMSCharset.pm 
> NMStreq.pm 
> MIME_Lite.pm 
>  
> I was able to setup and run the program in no time thanks to clear instructions. Developers doing a superb job, thanks very much. 
>  
> The problem I am having is: 
> In the form I have two fields; sender and email. 
>  
> I am using default email template and I have following set in config file  
>  
> email_input: email 
> realname_input: sender 
> subject: message from {= param.sender =} 
>  
> and in the program 
> CHARSET => 'utf-8'; 
>  
> When the form fields contain non-ascii characters, in the body of the email all fields display non-ascii chars correctly as well as subject field in the header. But the realname_input in the header does not. The From field of email displays: garbled_text_if_nonascii [email_address] 
>  
> Any suggestions much appreciated, thank for your time in advance. 
>  

It might be helpful if you could send us the complete headers of the
offending message, I think probably what you are seeing is that TFmail
is a bit more strict with the characters that it allows in the comment
part of the email address than it is with those in the Subject, although
I'm surprised that UTF-8 characters in the header are displayed
correctly at all as they really should be encoded as per
http://www.faqs.org/rfcs/rfc2047.html.

Ideally TFmail should support proper MIME header encoding, or at least
Base64 encoding for UTF-8, unfortunately this will require some
developer feeling the urge to implement it - I have Cc'd the developers
list in case anyone feels so inclined.

/J\

-- 

This e-mail is sponsored by http://www.integration-house.com/