However, my original point still remains. The MimeMessageWrapper
appears to be inconsistent with respect to which functions it updates
the internal header cache for and which it doesn't. I don't see that
there is any particular reason why there should be a difference between
the set functions which do update the header cache and those that
don't...
There is nothing in any email spec that correlates the To, Cc (other recipient headers) with the RCPT-TO lines. They are totally divorced, and to imply they are related is inaccurate.
If you want to know WHERE to deliver the message, you look at the RCPT-TO. In special cases where there is no RCPT-TO information, such as fetchmail, you can go back the MimeMessage to attempt to recreate the recipient list. But this is a known guessing attempt, it shouldn't be intermixed with existing delivery information.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
