randy roy ha scritto: > Stephan, > > Thanks for the info. I was able to get rid of the connection pool > problem. But there was a situation that made me get into this to begin > with that unfortunately is still there after all the performance tuning > stuff. > > I changed my provider from cable to DSL, and I'm getting failures on > send. In the SMTP log I get SocketException: Connection Reset messages. > > This is intermittent. Sometimes it sends fine. But then it will get on > a kick and fail for an hour or so, then start working again.
Sorry, no advice here. TCP/IP should works the same and should be transport agnostic. There should be no way to see difference between a cable and a DSL from the TCP/IP protocols. Maybe your new provider runs packet inspection hardware (this is a privacy violation and a known source of all kinds of problems, IMO). Maybe you should run some google search using your new provider name and problems: you should find someone complaining for this even if they are not using JAMES Server. > The worst part about it is that even though a failure is returned, the > email actually does get sent. So the email client continues to try to > send it resulting in a bunch of copies sent. SMTP protocol guarantee delivery of at least one copy of each sent message. Sending multiple time the same mail is a known corner case problem of SMTP protocol and while it can be minimized it cannot be avoided at all. In your case I guess there are bad network problems. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
