On fre 27 aug 2010 23:47:54 CEST, Alex wrote
Hi,
I'm still having some difficulty with trusted_networks, and believe it
may be a result of a DNS issue?
trosted_networks on hostnames ?
just kidding right ?
Yes, but it is among the relays in the Received: headers, so I thought
this is how it determines the last external server, or the first
trusted server, as the case may be?
Well, lack of reverse DNS ends the trust/internal path. Hard to trust a host
without proper DNS records.
I thought I had a working DNS, though. localhost resolves, and so does
127.0.0.1. Here's an example with cnn.com. Is this correct?
Received: from smtp01.example.com ([127.0.0.1])
by localhost (smtp01.example.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 30215-385 for <10...@example.com>;
Wed, 25 Aug 2010 18:35:09 -0400 (EDT)
this is from your postfix hand it over to amavisd, so check
smtp_helo_name in master.cf
postfix does not resolve ips that are non routelble by default imho
Received: from i2.web2.mail.cnn.com (i2.web2.mail.cnn.com [157.166.236.129])
by smtp01.example.com (Postfix) with ESMTP id 04CC413D4020
for <10...@example.com>; Wed, 25 Aug 2010 18:35:09 -0400 (EDT)
perfekt
Here it looks like localhost didn't resolve properly, but I don't
understand how this could be, because it is not only in the hosts file
and in DNS, but it's also in the hosts file for postfix.
see amavisd.conf and search for localhost
--
xpoint http://www.unicom.com/pw/reply-to-harmful.html
