cant send emails to a specific domain

smeko

Member
Feb 17, 2020
12
1
3
Tirane, Albania
cPanel Access Level
Root Administrator
Hello,
I administrate a cpanel shared hosting server and one of accounts cant send emails only to dhl.com.
From domain which is hosted in this cpanel to other external domains mails work fine.
Emails to dhl.com are stuck in queue and i cant force delivery them because it gives me this error:

LOG: skip_delivery MAIN
Spool file is locked (another process is handling this message)
LOG: queue_run MAIN

I tried restarting exim, enabling dmarc record for this domain but the problem is not resolved.

Please help


Silvi
 

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator
Hi Silvi,

What does your mail/exim logs tell you?
Fx if you dig into mails to dhl.com (exigrep dhl.com /var/log/exim_mainlog)
It could be because of blacklisting/DNSBL - or maybe greylisting?
 

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator
What do you have in your /etc/resolv.conf file?
Also, please try sending output from dig dhl.com mx
 

smeko

Member
Feb 17, 2020
12
1
3
Tirane, Albania
cPanel Access Level
Root Administrator
What do you have in your /etc/resolv.conf file?
Also, please try sending output from dig dhl.com mx
/etc/resolv.conf file shows me the nameservers of this cpanel shared hosting server.
the output of dig dhl.com mx is:


; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> dhl.com mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63134
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 6, ADDITIONAL: 49

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;dhl.com. IN MX

;; ANSWER SECTION:
dhl.com. 300 IN MX 5 mx1.dhl.iphmx.com.
dhl.com. 300 IN MX 10 mx2.dhl.iphmx.com.

;; AUTHORITY SECTION:
dhl.com. 76612 IN NS ns6.dhl.com.
dhl.com. 76612 IN NS ns4.dhl.com.
dhl.com. 76612 IN NS ns6b.dhl.com.
dhl.com. 76612 IN NS ns2b.dhl.com.
dhl.com. 76612 IN NS ns4b.dhl.com.
dhl.com. 76612 IN NS ns2.dhl.com.

;; ADDITIONAL SECTION:
mx2.dhl.iphmx.com. 3563 IN A 68.232.142.236
mx2.dhl.iphmx.com. 3563 IN A 68.232.142.240
mx2.dhl.iphmx.com. 3563 IN A 68.232.143.21
mx2.dhl.iphmx.com. 3563 IN A 68.232.143.139
mx2.dhl.iphmx.com. 3563 IN A 68.232.143.176
mx2.dhl.iphmx.com. 3563 IN A 68.232.148.169
mx2.dhl.iphmx.com. 3563 IN A 68.232.148.170
mx2.dhl.iphmx.com. 3563 IN A 68.232.148.171
mx2.dhl.iphmx.com. 3563 IN A 68.232.129.11
mx2.dhl.iphmx.com. 3563 IN A 68.232.129.198
mx2.dhl.iphmx.com. 3563 IN A 68.232.129.199
mx2.dhl.iphmx.com. 3563 IN A 68.232.130.32
mx2.dhl.iphmx.com. 3563 IN A 68.232.135.98
mx2.dhl.iphmx.com. 3563 IN A 68.232.135.99
mx2.dhl.iphmx.com. 3563 IN A 68.232.135.101
mx2.dhl.iphmx.com. 3563 IN A 68.232.135.103
mx2.dhl.iphmx.com. 3563 IN A 68.232.141.53
mx2.dhl.iphmx.com. 3563 IN A 68.232.141.220
mx2.dhl.iphmx.com. 3563 IN A 68.232.142.49
mx2.dhl.iphmx.com. 3563 IN A 68.232.142.218
mx1.dhl.iphmx.com. 3309 IN A 68.232.143.139
mx1.dhl.iphmx.com. 3309 IN A 68.232.143.176
mx1.dhl.iphmx.com. 3309 IN A 68.232.148.169
mx1.dhl.iphmx.com. 3309 IN A 68.232.148.170
mx1.dhl.iphmx.com. 3309 IN A 68.232.148.171
mx1.dhl.iphmx.com. 3309 IN A 68.232.129.11
mx1.dhl.iphmx.com. 3309 IN A 68.232.129.198
mx1.dhl.iphmx.com. 3309 IN A 68.232.129.199
mx1.dhl.iphmx.com. 3309 IN A 68.232.130.32
mx1.dhl.iphmx.com. 3309 IN A 68.232.135.98
mx1.dhl.iphmx.com. 3309 IN A 68.232.135.99
mx1.dhl.iphmx.com. 3309 IN A 68.232.135.101
mx1.dhl.iphmx.com. 3309 IN A 68.232.135.103
mx1.dhl.iphmx.com. 3309 IN A 68.232.141.53
mx1.dhl.iphmx.com. 3309 IN A 68.232.141.220
mx1.dhl.iphmx.com. 3309 IN A 68.232.142.49
mx1.dhl.iphmx.com. 3309 IN A 68.232.142.218
mx1.dhl.iphmx.com. 3309 IN A 68.232.142.236
mx1.dhl.iphmx.com. 3309 IN A 68.232.142.240
mx1.dhl.iphmx.com. 3309 IN A 68.232.143.21
ns2.dhl.com. 71145 IN A 156.137.1.166
ns4b.dhl.com. 76612 IN A 165.72.190.166
ns4b.dhl.com. 300 IN AAAA 2a05:4a40:fffd:4105::1
ns6b.dhl.com. 76612 IN A 199.40.15.66
ns2b.dhl.com. 76612 IN A 156.137.195.66
ns6.dhl.com. 19931 IN A 199.40.254.166
ns4.dhl.com. 30726 IN A 165.72.192.16
ns4.dhl.com. 117126 IN AAAA 2a05:4a40:fff3:410a::1
 

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator
I think the post was too long. Can you post what's between "DNS lookup of dhl.com (MX) succeeded" and ">>>>> Exim" ? :)
 

smeko

Member
Feb 17, 2020
12
1
3
Tirane, Albania
cPanel Access Level
Root Administrator
I think the post was too long. Can you post what's between "DNS lookup of dhl.com (MX) succeeded" and ">>>>> Exim" ? :)
DNS lookup of dhl.com (MX) succeeded
DNS lookup of mx1.dhl.iphmx.com (A) gave TRY_AGAIN
mx1.dhl.iphmx.com in dns_again_means_nonexist? no (option unset)
returning DNS_AGAIN
set_address_from_dns: Lookup failed; type 0/1
DNS lookup of mx1.dhl.iphmx.com (AAAA) gave NO_DATA
returning DNS_NODATA
set_address_from_dns: Lookup failed; type 1/1
DNS lookup of mx2.dhl.iphmx.com (A) gave TRY_AGAIN
mx2.dhl.iphmx.com in dns_again_means_nonexist? no (option unset)
returning DNS_AGAIN
set_address_from_dns: Lookup failed; type 0/1
DNS lookup of mx2.dhl.iphmx.com (AAAA) gave NO_DATA
returning DNS_NODATA
set_address_from_dns: Lookup failed; type 1/1
fully qualified name = dhl.com
host_find_bydns yield = HOST_FIND_AGAIN (1); returned hosts:
mx1.dhl.iphmx.com <null> MX=5 *
mx2.dhl.iphmx.com <null> MX=10 *
lookuphost router: defer for
message: host lookup did not complete
cannot be resolved at this time: host lookup did not complete
search_tidyup called
>>>>>>>>>>>>>>>> Exim pid=767020 (main) terminating with rc=1 >>>>>>>>>>>>>>>>
 
Last edited:

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator
Ok - so you have an issue resolving the hostnames in the MX records.
I suggest you switch DNS servers in your /etc/resolv.conf

One test you can do:
dig mx1.dhl.iphmx.com a
and with Google DNS:
dig @8.8.8.8 mx1.dhl.iphmx.com a

PS: You may want to remove the real e-mail address from your posts... ;)
 

Michael Svendsen

Well-Known Member
Dec 19, 2016
75
20
83
Denmark
cPanel Access Level
Root Administrator
Great! So you changed DNS servers in your resolv.conf?

The change shouldn't have any effect on your server - unless:

a) The old DNS server was an internal DNS server, where you also had special internal records added (split DNS/views)
b) You used the old DNS as a DNS resolver towards DNSBL services
c) Special network/firewall setup (offline/internal server, blocking outgoing DNS, etc. )
 

cPanelLauren

Technical Support Community Manager
Staff member
Nov 14, 2017
12,366
1,126
313
Houston
Great! So you changed DNS servers in your resolv.conf?

The change shouldn't have any effect on your server - unless:

a) The old DNS server was an internal DNS server, where you also had special internal records added (split DNS/views)
b) You used the old DNS as a DNS resolver towards DNSBL services
c) Special network/firewall setup (offline/internal server, blocking outgoing DNS, etc. )
Most of these being rare circumstances, you could also retain one of the nameserver entries as a tertiary resolver as well (3rd entry)