Thanks for your advice Noel. Today I upgraded from 2.1.2 to 2.2.0 and the results were as you predicted.
It seems the 2.2.0 version tries all the MX records it can find rather just
the first as in 2.1.2 (?) so I'm seeing much better results now.
Anyway.. The result is that I am now able to send to imray.co.uk (it tried 6
different addresses for depot.dial.pipex.com. before finally succeeding at
fallback.dial.pipex.com.).
Strange that I still seem to have problems with the AOL address I started
out with - but I can see that it tries a large number (16) of different mail
servers before giving up ("No mail server(s) available at this time") so at
least it seems to be working as well as possible from my end. Bit tough
on AOL users waiting for mail though because this failure to deliver was
repeated 4 times and counting...
Thanks,
John Hornsby
> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: 14 July 2004 16:14
> To: James Users List; [EMAIL PROTECTED]
> Subject: RE: Could not connect to SMTP host
>
> > 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).
>
> Mail for imray.co.uk is handled by depot.dial.pipex.com,
> followed by fallback.dial.pipex.com. Make sure that James is
> using those hosts, not imray.co.uk directly. Then test
> access to them from the same machine on which James is
> running by doing a telnet <host> smtp.
>
> --- Noel
>
smime.p7s
Description: S/MIME cryptographic signature
