On 15/03/11 15:10, Wietse Venema wrote:
> Rafael Azevedo:
> [ Charset ISO-8859-1 unsupported, converting... ]
>> Hi Wietse!
>>
>> Thanks again for helping me!
>>
>> Here is the postfix log:
>>
>> # SLOW DOMAIN
>> Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from
>> srv01.iagentemail.com.br[189.38.86.124]
>> Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client=
>> srv01.iagentemail.com.br[189.38.86.124]
>> Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id=<
>> 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br>
>> Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 "DKIM-Signature"
>> header added
>> Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from=<
>> reto...@iagentemail.com.br>, size=629, nrcpt=2 (queue active)
>> Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host
>> mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected:
>> cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command)
>> Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET
>> from srv01.iagentemail.com.br[189.38.86.124]
>> Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from
>> srv01.iagentemail.com.br[189.38.86.124]
> 
> The above message is rejected because 187.1.133.20 has no PTR record.

There are 2 nameservers listed in DNS that should have PTR records for
133.1.187.in-addr.arpa, both of these have 2 ip-addresses, resulting in
4 DNS servers to check. Two of these return correct data,  the other two
return no PTR record, and a strange looking SOA, for that matter.

$ dig ns 133.1.187.in-addr.arpa

; <<>> DiG 9.7.1-P2 <<>> ns 133.1.187.in-addr.arpa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34523
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 4

;; QUESTION SECTION:
;133.1.187.in-addr.arpa.                IN      NS

;; ANSWER SECTION:
133.1.187.in-addr.arpa. 5234    IN      NS      ns1.dns2.com.br.
133.1.187.in-addr.arpa. 5234    IN      NS      ns2.dns2.com.br.

;; ADDITIONAL SECTION:
ns1.dns2.com.br.        84434   IN      A       187.1.143.64
ns1.dns2.com.br.        84434   IN      A       189.38.86.79
ns2.dns2.com.br.        84434   IN      A       187.1.143.65
ns2.dns2.com.br.        84434   IN      A       189.38.86.80

$ dig +short -x 187.1.133.20 @189.38.86.79
mxcluster.iagentemail.com.br.
=> OK

$ dig +short -x 187.1.133.20 @187.1.143.64
=> No PTR, this is your problem

$ dig +short soa 133.1.187.in-addr.arpa @187.1.143.64
cyrus.webpro.com.br. raffus.gmail.com. 1299803423 10800 3600 604800 10800
=> Google mailbox as hostmaster address?

I think the person maintaining the DNS address space of *your
mailserver* made a typo or a config error somewhere.

Regards,
        Tom

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to