>Mar 1 09:24:14 gumby kwoody[4549]: postfix/smtpd[7343]: reject: RCPT from >freelists-180.iquest.net[206.53.239.180]: 450 ><[EMAIL PROTECTED]>: Sender address rejected: Domain not >found; from=<[EMAIL PROTECTED]> >to=<[EMAIL PROTECTED]>
450 means it was a DNS timeout >Dig freelists.org = > >freelists.org. 23h53m44s IN A 206.53.239.180 so it was a temporary DNS failure. >Ok so they dont match the reject above is not reject_unknown_client in from_senders_bogus, it's simple DNS failure. > so this looks to be valid mail I added: to which file? >iquest.net OK >freelists.org OK ><IP of iquest.net> OK > >rebuilt access. > >Still mail gets refused. Failing with a 450 so it will be retried. yes, try to find out why postfix can get the same resulst that dig on the postfix machine gets >So I just try a dig on the mailserver (the above dig was done on our >primary NS) and I get a timeout on our primary MX: > >dig freelists.org > >; <<>> DiG 8.3 <<>> freelists.org >;; res options: init recurs defnam dnsrch >;; res_nsend to server default -- 0.0.0.0: Operation timed out et voila, Monsieur Keith, votre probleme >?? > >so as a test I added our NS to resolv.conf and still the mailserver cannot >find freelists.org. > >So go to our 2ndary MX: dig @where? freelists.org any >;; FROM: tuck.citytel.net to SERVER: default -- 0.0.0.0 "default -- 0.0.0.0" ??? that would work better if it were an ip address!! :)) >A whois shows the domain is valid, though with different AUTH servers. screw whois, it has nothing to do with DNS. >Anything that I might look at here to get this mail to be accepted? you've found the DNS problem as seen by postfix, so the solution is NOT to whitelist anything, but fix your DNS problem. >I cant find a reason why our primary MX cant find freelists.org, yet our >primary NS and the secondary MX can? well, keep looking :)) >What could be missing here? patience and persistence!! :)) Len
