On Tue, Jan 19, 2010 at 07:47:11AM +0000, Camaleón wrote:
> On Tue, 19 Jan 2010 00:50:56 +0000, Adam Hardy wrote:
> > Jan 18
> > 23:32:32 my-other-domain postfix/smtp[32633]: 11C082A8779:
> > to=<adam@my-other-domain.vs.athnic.net>, relay=none, delay=0.07,
> > delays=0.04/0.01/0.02/0, dsn=4.4.1, status=deferred (connect to
> > my-other-domain.vs.athnic.net[11.22.33.44]:25: Connection refused) (END)
> This can be the cause. You (or your provider) are forcing Postfix to
> listen only in loopback interface (127.0.0.1) so you get a "connection
> refused" error when tries to connect to [11.22.33.44] (also, the "square
> brackets" means no name server resolution is done).
>
> It seems your host is configured for local delivery only :-?
This is not how I read the logs.
He does not want the machine running postfix to accept mail
from the outside world, so he does want it to listen only on
127.0.0.1 -- this is by design.
The "connection refused" logs are the postfix daemon
attempting to connect outbound - this does not look to be a
postfix-specific issue.
Adam, can you connect outbound to your ISPs mail server on
port 25, by hand? Use netcat if you have it, or telnet if
you do not, to test:
$ nc my-other-domain.vs.athnic.net 25
220 <more stuff>
You should get a response line like the above. If it does
not appear after a few seconds, or you get a connection
refused message, then your local ISP is blocking port 25
outbound, which is nowadays fairly common.
The ISP for your domain, who run the SMTP server, may accept
mail on alternative ports. The "submission" port 587 is
commonly used for this purpose, and is less likely to be
blocked by your home-Internet-ISP:
$ nc my-other-domain.vs.athnic.net 587
220 <more stuff>
If that works, reconfigure postfix to use port 587 instead
of 25 for it's relay host / smart host.
If it doesn't, you may have to use your ISPs relay host for
outbound mail.
--
Jon Dowland
Attachment:
signature.asc
Description: Digital signature