You may get a refusal if your reverse DNS doesn't hatch the helo name of the server:
Code:
dig -x 202.154.23.164
; <<>> DiG 9.4.1-P1 <<>> -x 202.154.23.164
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64430
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 2
;; QUESTION SECTION:
;164.23.154.202.in-addr.arpa. IN PTR
;; ANSWER SECTION:
164.23.154.202.in-addr.arpa. 86327 IN PTR host-202-154-23-164.rad.net.id.
;; AUTHORITY SECTION:
23.154.202.in-addr.arpa. 86327 IN NS ns3.gip.net.
23.154.202.in-addr.arpa. 86327 IN NS ns1.gip.net.
23.154.202.in-addr.arpa. 86327 IN NS ns1.rad.net.id.
23.154.202.in-addr.arpa. 86327 IN NS ns2.gip.net.
23.154.202.in-addr.arpa. 86327 IN NS ns2.rad.net.id.
;; ADDITIONAL SECTION:
ns1.rad.net.id. 3526 IN A 202.154.1.2
ns2.rad.net.id. 3528 IN A 202.154.3.2
Did you also read the link in the error message from Yahoo! -
Mail
The usual questions follow: do you have a valid /etc/hosts file and correct DNS A & MX records pointing to your server?