Jason Webb wrote:
I've tried the following settings:Taken from Qmail - 60 second timeout is fineprops.put("mail.smpt.connectiontimeout", "6000");
Great.
props.put("mail.smtp.timeout", "1200000");Taken from Qmail - 20 minute timeout on I/O. This may be less than desirable. Someone may be sending you 1 byte every 19 minutes. This keeps the channel open and acts like a DOS attack.
Good enough.
props.put("mail.smtp.localhost", "stockholm.inovem.com");Not sure this is useful. Doesn't cause any problems, but I think it doesn't add much either.
Yeah, let's omit it for now.
You know this because the SendFailedException will enumerate the addresses that did not receive the message. Right now if I send an email to 14 hotmail accounts and one of them is bad, none of the recipients gets the message. That isn't very fun.props.put("mail.smtp.sendpartial", "true");This appears on the surface to be nice, but I don't think it is. I send a mail to 2 people, 1 address gives me a 5xx error (mail box full for example). Which one succeed? Do I try again later? Do I end up sending the same message many times (once per attempt) to the user who I can send to?
I'm not sure, but I think this may be a bad idea.
Yeah, possibly easy... I would agree to at least hold off until post 2.1.1.
It also leaks memory slowly and persitantly. My current opinon with JavaMail's SMTP transport is to keep it simple. So I'd recommend NOT using it.
Yeah, if it's leaking...
In summary add the following:
props.put("mail.smpt.connectiontimeout", "6000");
props.put("mail.smtp.timeout", "1200000");
Ok, will commit momentarily. We could think about making these
configurable at some point in the futue.--
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]
