Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Nigel Wade Newsgroups: comp.lang.java.programmer Subject: Re: JavaMail bug? Date: Wed, 03 Aug 2011 09:38:41 +0100 Lines: 11 Message-ID: <99sfoiFs99U1@mid.individual.net> References: <995djcFq0nU1@mid.individual.net> <99njvpFv11U1@mid.individual.net> <99qjntFk6uU1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 7Jb4jWz5Q8QYT+r+e31leAu04BgBf6cQBJ+ksQSJE56WMEzFD1 Cancel-Lock: sha1:W+VMP696w/NwP7IitH3CBY2uc5w= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.18) Gecko/20110616 SUSE/3.1.11 Thunderbird/3.1.11 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6772 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. -- Nigel Wade