On 21 Nov 2005 at 12:59, Rob Brenart wrote about
"Re: [exim] smarthost relay problems":
|...
| Thanks for the advice... it is a debian list, so I've asked on the exim4
| debian user's list and we'll see if I get any hits... in case it matters
| though, I tried your command and received the following... but no
| message delivered. However, I think I see the problem, :25... I'm pretty
| sure I need to be coming in over 465 with SSL...
|
| trying to find in the
| docs how to set this now
|
| delivering 1EeEN0-0007WR-67
| LOG: MAIN
| Unfrozen by forced delivery
| R: smarthost for rob@???
| T: remote_smtp_smarthost for rob@???
| Connecting to mail.xxxxxxxxx.com [99.99.2.202]:25 ... failed: Connection
| timed out (timeout=5m)
What machine is this exim running on? Is it connected to the
Internet by an ISP that blocks outbound port 25?
| LOG: MAIN
| mail.oculardata.com [99.99.2.202]: Connection timed out
mail.oculardata.com is running exim, and it is listening on port 25
(whence STARTTLS is available, which exim supports as a client). It
is also listening on port 465, requiring tls-on-connect (which exim
doesn't support as a client). It is *not* listening on the standard
MSA port (587). Short of running a portscan, I can't tell if it is
listening on any non-standard ports.
Do you have any influence on the configuration of your smarthost
(mail.oculardata.com)? If so, the most straightforward solution to
your apparent "port 25 blocked" problem is to configure it to listen
on port 587 (and require authentication), or some non-standard port
(using the same rules as port 25).
If not, perhaps you can get your ISP to lift the port 25 block for
you, at least to this one host.
Failing both of those, stunnel it is...
- Fred
