You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Marcello Marangio <m....@tno.it> on 2008/01/16 12:05:02 UTC

mailimpl and recipients bug 336 on james 2.2.0

Hi all.

I found this bug on james 2.2.0

https://issues.apache.org/jira/browse/JAMES-336

 I read that it has been fixed in the release 3.0.

As we cannot (at the moment) upgrade our system, we made a patch so that the
constructor of mailImpl reads all the recipients (TO, CC, and BCC).

Can anyone see any problem in this patch?

Thanks

Marcello

 


Re: mailimpl and recipients bug 336 on james 2.2.0

Posted by Stefano Bagnara <ap...@bago.org>.
Marcello Marangio ha scritto:
> Hi all.
> 
> I found this bug on james 2.2.0
> 
> https://issues.apache.org/jira/browse/JAMES-336
> 
>  I read that it has been fixed in the release 3.0.

It has been fixed removing that constructor whose behavior was not clear.

> As we cannot (at the moment) upgrade our system, we made a patch so that the
> constructor of mailImpl reads all the recipients (TO, CC, and BCC).
> 
> Can anyone see any problem in this patch?

There is no right way to "read" the recipients from the MimeMessage. The 
right behavior depends on the specific use case. So there is no right 
patch for the issue above.

That's why we fixed it removing the constructor that made it possible.

If some code require the creation of a Mail object from a MimeMessage 
then it is its own responsibility to decide how to populate the 
recipient part of the generated Mail object.

Stefano



---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org