Re: An interesting note about memory leaks (was Memory leaks in RemoteDeliverymailet?)

[Serge Knystautas]

Jason Webb wrote:

The good news is that I can still set "mail.smtp.from" and have no
memory leaks.
Therefore I'd move that the setting of "mail.smtp.user" be dropped as a)
it causes problems and b) it's irrelevant.

Sounds good... yeah, we definitely need to keep setting mail.smtp.from, so I'm glad that doesn't leak.

Since we've upgraded to JavaMail 1.3, there are some other proerties we'd want to set...
1. mail.smpt.connectiontimeout (socket connection timeout value in milliseconds, default is infinite timeout)
2. mail.smtp.timeout (socket I/O timeout value in milliseconds, default is inifite)
3. mail.smtp.sendpartial (If set to true, and a message has some valid and some invalid addresses, send the message anyway, reporting the partial failure with a SendFailedException. If set to false (the default), the message is not sent to any of the recipients if there is an invalid recipient address.)

Also maybe...
4. mail.smtp.localhost (Local host name. Defaults to InetAddress.getLocalHost().getHostName(). Should not normally need to be set if your JDK and your name service are configured properly.) Maybe have this based on something in config.xml?

If possible, could try to set these as well and see if there are any memory leaks?... the 2 timeouts would be good to add to keep the delivery threads robust, as well as supporting partial message delivery (I can't believe people don't scream about this.)

--
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]