Re: Interpreting Subject line

[Jason Lea]

I have been playing around with email encoding in the last few days - 
trying to send UTF-8 encoded email so that stuff is defined in RFC2047...

encoded-word = "=?" charset "?" encoding "?" encoded-text "?="

charset=iso-8859-1 (normal Latin-1 encoding)
encoding=B (can be either B or Q encoding)
encoded-text=UGF5IFBlbm5pZXMgb24gdGhlIERvbGxhciBmb3IgeW91ciBQcmVzY3JpcCh0aW9uIQ==
By chosing the 'B' encoding it is causing every character to be encoded 
using BASE64 encoding.  Normally if you send mostly ASCII characters you 
would choose type Q where the 8-bit characters are converted into =XX 
format (eg '=' becomes '=3D', SPACE becomes '=20').

see here for more info http://www.faqs.org/rfcs/rfc2047

Vinny wrote:

Sorry if this sounds stupid, but how do you interpret that crazy string of
characters? Is that sound king of screwed up MD5 sum or something?
 

=?iso-8859-1?B?>UGF5IFBlbm5pZXMgb24gdGhlIERvbGxhciBmb3IgeW91ciBQcmVzY3JpcCh
   

0a
 

W9uIQ==?=
   



-Vinny

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



--
Jason Lea


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]