Content-Transfer-Encoding: quoted-printable, James 2.0a3

[Ian Huynh <ia...@hubspan.com>]

I am receiving email (with MIME attachment) from a user in Europe which uses
Content-Transfer-Encoding: quoted-printable.

Shouldn't James handle this encoding automatically prior to passing it on to 
our mailet? or should we handle this inside our mailet?  

Thanks

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Content-Transfer-Encoding: quoted-printable, James 2.0a3

[Danny Angus <da...@apache.org>]

Ian,

AFAIK it should be handled correctly by MimeMessage, if you're having specific problems what are they?
FWIW I've noticed problems with Europeans (self included) using US_ASCII charset, the answer is to use utf-8.
I use quoted printable meself, and this mail comes to you from Europe via James... 

FYI there were problems in the past related to James having a non-English "locale" and trying to process data from a different locale, this was related to dates which are always in English (James was translating them), but I could easily see how a similar locale difference would affect charset, though not transfer encoding which is by definition meant to solve many of the problems of messages being altered en-route.

d.

> -----Original Message-----
> From: Ian Huynh [mailto:ianh@hubspan.com]
> Sent: 23 October 2002 19:09
> To: james-user@jakarta.apache.org
> Subject: Content-Transfer-Encoding: quoted-printable, James 2.0a3 
> Importance: High
> 
> 
> I am receiving email (with MIME attachment) from a user in Europe 
> which uses
> Content-Transfer-Encoding: quoted-printable.
> 
> Shouldn't James handle this encoding automatically prior to 
> passing it on to 
> our mailet? or should we handle this inside our mailet?  
> 
> Thanks
> 
> --
> To unsubscribe, e-mail:   
> <ma...@jakarta.apache.org>
> For additional commands, e-mail: 
> <ma...@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>