Thanks Noel, I'll try an upgrade to 2.2.0, hopefully a painless one.
Hopefully this will also solve some other little problems I have where I simply cannot seem to reach certain mail destinations from my James server, but I can from others. (An example is mail to [EMAIL PROTECTED] (which works fine from other mail servers) but gives me a "Connection refused" error from my James). Thanks, John Hornsby > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: 13 July 2004 20:43 > To: James Users List; [EMAIL PROTECTED] > Subject: RE: Could not connect to SMTP host > > > Why would I get this? > > Because the number of sockets was maxed out, there was a > temporary network problem, or any number of other things. > Happens often. That is why large domains have multiple > servers, and why we retry transmission. > > > Is there anything I can do to get around this? BTW it > fails many times > > over many hours, until it finally gives up. > > > James 2.1.2 > > If you are using James 2.1.2, try using James 2.2.0, which > does a much better job of trying alternative MX records. > > --- Noel >
smime.p7s
Description: S/MIME cryptographic signature
