james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lukáš Vlček <lukas.vl...@gmail.com>
Subject Re: Switching from 0.6 to 0.7.1 - address parsing, CRLF issues
Date Thu, 15 Dec 2011 12:19:26 GMT
OK, got it.
(Although in 0.6 it was returning decoded content)

Regards,
Lukas

On Thu, Dec 15, 2011 at 1:16 PM, Oleg Kalnichevski <olegk@apache.org> wrote:

> On Thu, 2011-12-15 at 11:41 +0100, Lukáš Vlček wrote:
> > Hi,
> >
> > I tried it and it works. Thanks!
> >
> > However, still I am not sure if this fixed everything.
> > See the following commit in my test repo on github (I added a new branch
> > called "workaround")
> >
> https://github.com/lukas-vlcek/mime4j-test/commit/385c66847bec4393ad67069fb367c174f87c5656
> >
> > As you can see the call to  message.getFrom().get(0).getName() returns
> > expected data, but message.getHeader().getField("from").getBody() does
> not.
> > At least that is how I understand its JavaDoc:
> >
> http://james.apache.org/mime4j/apidocs/org/apache/james/mime4j/stream/Field.html#getBody()
> >
> > "Gets the unparsed and possibly encoded (see RFC 2047) field body
> string."
> >
> > How should I understand the "encoded" in this context?
> >
>
> Encoded actually means, well, encoded, as specified in RFC 2047.
>
> Oleg
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message