On 9/24/2009 9:08 AM, Martijn de Munnik wrote:
On Thu, 2009-09-24 at 15:48 +0200, Martijn de Munnik wrote:
On Thu, 2009-09-24 at 09:41 -0400, Carlos Williams wrote:
On Thu, Sep 24, 2009 at 9:16 AM, Martijn de Munnik<mart...@youngguns.nl> wrote:
I think this is not too restrictive and the sending mailserver should
fix their rdns, YMMV. We use a policy server (policyd-weight) which
gives scores for things like no rdns, dailup ip, ip in dnsbl etc.
So the problem then is that the servers reverse DNS is not resolving
to their sending IP, correct?
When I do a RDNS on the server, I get the following:
204.117.196.2 resolves to
"mail.pmcatt-ppss.com"
Top Level Domain: "pmcatt-ppss.com"
204.117.196.2 has a reverse dns entry: 2.196.117.204.in-addr.arpa domain
name pointer mail.pmcatt-ppss.com.
So the problem is on your postfix box. Postfix replied a 450 temporary
failure, the sending mailserver should try again later. Check if you can
resolve the ip on your postfix box.
The client has slightly broken rDNS. From my box:
$ host 204.117.196.2
Host 2.196.117.204.in-addr.arpa not found: 2(SERVFAIL)
and a few minutes later...
$ host 204.117.196.2
2.196.117.204.in-addr.arpa domain name pointer
mail.pmcatt-ppss.com.
Note that postfix rejected the mail with a 450 "defer" code
since this was a temporary error; the client should retry
later. Hopefully the rDNS will work on a later attempt.
At any rate, if you need to consistently receive mail from
that client, you will need to either remove
reject_unknown_reverse_client_hostname (a useful and generally
safe restriction) or add that client to a check_client_access
whitelist.
-- Noel Jones
