Agree, I filed a bug about this, they politely accepted my position and just as politely declined to take action. :-)
The position is that we should subclass MimeMessage to change this behaviour. d. > -----Original Message----- > From: Serge Knystautas [mailto:[EMAIL PROTECTED] > Sent: 07 March 2003 03:14 > To: James Developers List > Cc: JAVAMAIL-INTEREST > Subject: Re: ID-mail > > > Noel J. Bergman wrote: > >>In fact I must keep the same ID to make tri on the mails incoming on > > > > > > We understand the issue, and the problems that occur when Message-ID is > > changed because you have added a header to a MimeMessage. This is not > > something that James does; it is part of JavaMail. I am cc'ing the > > JavaMail-Interest list on this reply. Sun may have some > suggestion(s). > > We used to instantiate MimeMessages in James using a "ServerMimeMessage" > that extended MimeMessage, and overrode saveChanges to remove these mail > client style behavior. I'm not sure when or why it was removed, but > unless Sun has changed their position, JavaMail is geared towards mail > client usage, so this is how they want it to behave. > > -- > Serge Knystautas > President > Lokitech >> software . strategy . design >> http://www.lokitech.com/ > p. 1.301.656.5501 > e. [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
