The account or domain may not exist, they may be blacklisted, or missing .. ? is it?

[lehels]

exim.conf:
#
# Trap Failures to Remote Domain
#

fail_remote_domains:
driver = redirect
domains = ! +local_domains
allow_fail
data = ":fail: The mail server could not deliver mail to $local_part@$domain.
The account or domain may not exist, they may be blacklisted, or missing the pr
oper dns entries."


the SMTP transaction test:

>>> using ACL "check_recipient"
>>> processing "accept"
>>> check hosts = :
>>> host in ":"? no (end of list)
>>> accept: condition test failed
>>> processing "warn"
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} {yes}{no}}
>>> = no
>>> warn: condition test failed
>>> processing "accept"
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} {yes}{no}}
>>> = no
>>> accept: condition test failed
>>> processing "warn"
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} {yes}{no}}
>>> = no
>>> warn: condition test failed
>>> processing "accept"
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} {yes}{no}}
>>> = no
>>> accept: condition test failed
>>> processing "require"
>>> check verify = recipient
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> routing psitest@psitest.ro
>>> psitest.ro in "lsearch;/etc/localdomains"? no (end of list)
>>> psitest.ro in "+local_domains"? no (end of list)
>>> psitest.ro in "! +local_domains"? yes (end of list)
>>> psitest.ro in "! +local_domains"? yes (end of list)
>>> calling lookuphost router
>>> lookuphost router declined for psitest@psitest.ro
>>> psitest.ro in "! +local_domains"? yes (end of list)
>>> calling literal router
>>> literal router declined for psitest@psitest.ro
>>> psitest.ro in "! +local_domains"? yes (end of list)
>>> calling fail_remote_domains router
>>> fail_remote_domains router forced address failure
>>> ----------- end verify ------------
>>> require: condition test failed

550-The mail server could not deliver mail to psitest@psitest.ro. The account
550-or domain may not exist, they may be blacklisted, or missing the proper dns
550 entries.

LOG: H=() [IP] F=<test@beeline.ro> rejected RCPT psitest@psitest.ro: The mail server could not deliver mail to psitest@psitest.ro. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries.

----

beeline.ro is hosted in our server,
psitest.ro is not hosted by us, so it shouldn't be [it isn't] in the /etc/localdomains

the domain is not blacklisted, and has proper dns entries,

why the message still fails to leave? ok, accept condition failed, why failing?

thank you,
Lehel

[cpanelnick]

Looks like its failing because of dns resolution. Check your /etc/resolv.conf

try

dig psitest.ro MX

[Domenico]

Looks like its failing because of dns resolution. Check your /etc/resolv.conf

try

dig psitest.ro MX

Ok I have the same problem. How can you tell the resolv.conf is wrong?
When I look at the other resolv.conf files they are all the same and those servers work fine and to me the resolv.conf looks fine.

Please be more specific Nick!

[FeeL]

For solutions about this problem, see also

Account or domain may not exist, they may be blacklisted, or missing the proper dns e

Thanks

[ElrondBCN]

I'm having the same problem, and it only started recently. What is strange about it is that most messages to a particular address are delivered successfully, but occasionally the message delivery fails. And there appears to be no rhyme or reason for it.

[Danks]

Sorry to bump an old thread but I had a similar issue and this was one of the first results in google.

I had this same issue and it turned out the remote domain had MX records pointing to an IP address, an incorrect set up of course.

My solution was to add

allow_mx_to_ip = yes


to /etc/exim.conf which fixed the problem.

Yes I know the owner of the remote domain needs to fix the problem since their set up was incorrect but of course our user just wanted it to work