Stan Hoeppner a écrit : > John WInther put forth on 3/6/2010 12:57 PM: >> Thanks for info, I am aware of the manual and I have previus tryed to >> change the myhostname to soapnut.dk, I still got the reverse dns error. >> I gave me an idear to reverse resolve the ip address registred in mx, >> and the reply from that test was the dns name of my internet access. >> 0xbcb75b12.cpe.ge-1-1-0-1112.customer.tele.dk, when i put that in as >> myhostname the reverse dns lookup reply with success. > > RFC does not dictate that your forward and reverse dns names match. It does > dictate that a domain name must be valid. Anything ending in .local is not > valid. > > I'd suggest against using > > 0xbcb75b12.cpe.ge-1-1-0-1112.customer.tele.dk > > as your Postfix HELO name. Use a hostname based on one of your mail domains > instead. Some sites will block SMTP servers that HELO with such a generic > hostname as that above.
true. better use soapnut.dk in myhostname. Although I doubt this will help a lot: - "some" sites will block if the PTR is generic... too many zombies out there... - OP's reverse DNS is borked: $ host 188.183.91.18 18.91.183.188.in-addr.arpa domain name pointer 0xbcb75b12.cpe.ge-1-1-0-1112.hcnqu2.customer.tele.dk. $ host 0xbcb75b12.cpe.ge-1-1-0-1112.hcnqu2.customer.tele.dk. Host 0xbcb75b12.cpe.ge-1-1-0-1112.hcnqu2.customer.tele.dk. not found: 3(NXDOMAIN) so OP not only has a "generic" name, but it doesn't resolve back to the IP. If he can get his ISP to fix his reverse (preferably using a custom reverse), then maybe things will get better.
