Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: JavaMail bug? Date: Tue, 16 Aug 2011 21:06:14 +0000 (UTC) Organization: UK Free Software Network Lines: 24 Message-ID: References: <995djcFq0nU1@mid.individual.net> <99njvpFv11U1@mid.individual.net> <99qjntFk6uU1@mid.individual.net> <99sfoiFs99U1@mid.individual.net> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1313528774 17041 84.45.235.129 (16 Aug 2011 21:06:14 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Tue, 16 Aug 2011 21:06:14 +0000 (UTC) User-Agent: Pan/0.133 (House of Butterflies) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:7143 On Wed, 03 Aug 2011 09:38:41 +0100, Nigel Wade wrote: > I've just been reviewing the JavaMail API as it's a while since I used > it. You need to be aware that Transport.send() is a /static/ method. I > presume this means it takes no note of any connection established by an > object of class Transport, since the class method has no knowledge of > any contents of any Transport object. That probably explains why it uses > the values in the Session, not those established by the Transport object > you've created. > Final comment: On Sunday this whole mess niggled me again, so I ripped out the property setting the default MTAname and replaced the call of tr.send(msg) with tr.sendMessage(msg, recipients) so the Transport acquired from the Session is used. This all works as expected: there's only the one EHLO conversation and the recipient is validated (which I don't remember seeing earlier). -- martin@ | Martin Gregorie gregorie. | Essex, UK org |