Домен: halje.ru
Создал А запись для 3 уровня: mail.halje.ru
Создал PTR запись для: halje.ru, mail.halje.ru
Создал MX запись: halje.ru > 10 mail.halje.ru
Из-за чего может быть эта ошибка? Не знаю что еще можно сделать.
В /etc/postfix/main.cf
#myhostname: mail.halje.ru
#mydomain: halje.ru
#myorigin: halje.ru
СКРИН С САЙТА MXTOOLBOX.COM
-
Вопрос заданболее года назад
-
634 просмотра
Создал PTR запись для: halje.ru, mail.halje.ru
Это как?
Предположим ip Вашего почтового сервера SERVER_IP, тогда для корректного принятия почты от вашего домена halje.ru должно быть создано 3 DNS записи:
1) A — запись для почтового сервера mail.halje.ru с адресом SERVER_IP
2) MX — запись для домена halje.ru указывающая на mail.halje.ru
3) PTR — запись для SERVER_IP указывающая на имя mail.halje.ru
Кроме того будет полезно создать spf, dkim и dmarc записи. Как это сделать легко гуглится
Пригласить эксперта
PTR записи создаются для ip адресов, а не для доменных имен.
У вас скорее всего нет PTR зоны и поэтому нужно обратиться к провайдеру, который вам выдал внешние ip адреса, так как управляет PTR зоной для них скорее всего именно он.
nslookup %ip адрес, привязанный к mail.halje.ru%, что показывает?
-
Показать ещё
Загружается…
13 февр. 2023, в 18:13
2000 руб./за проект
13 февр. 2023, в 17:43
3000 руб./за проект
13 февр. 2023, в 16:58
25000 руб./за проект
Минуточку внимания
I can’t send email messages from my server. However, I can receive email messages. I set up my server the exact same way I did many times which I’ve proven it works and it’s pretty straightforward and consist of: Create a DigitalOcean Droplet (Debian 7.0) + Set PTR record through renaming Droplet to a FQDN + Create Private NameServers in my Domain Registrar and point my domain(s) to my NameServers + Installing VestaCP (child-ns). From here, I simply add a web through VestaCP and the DNS records are added automatically.
I am not sure where I have gone wrong in my configuration but I am getting the error «Reverse DNS is not a valid Hostname» for my domain izanami.co
. I set my DigitalOcean Droplet PTR record to izanami.co
and all of the tests I have conducted using dig and host seem to return the correct information.
dig -x 188.166.32.113
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> -x 188.166.32.113
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47119
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;113.32.166.188.in-addr.arpa. IN PTR
;; ANSWER SECTION:
113.32.166.188.in-addr.arpa. 1283 IN PTR izanami.co.
;; Query time: 9 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Fri Aug 7 15:06:39 2015
;; MSG SIZE rcvd: 69
hostname -f
izanami.co
host izanami.co
izanami.co has address 188.166.32.113
izanami.co mail is handled by 10 mail.izanami.co.
host 188.166.32.113
root@izanami:~# host 188.166.32.113
113.32.166.188.in-addr.arpa domain name pointer izanami.co.
dig +short ptr 188.166.32.113.in-addr.arpa
113x32x166x188.ap113.ftth.ucom.ne.jp.
MXToolBox Transcript
Connecting to 188.166.32.113
220 izanami.co ESMTP Exim 4.80 Fri, 07 Aug 2015 14:20:52 +0200 [5750 ms]
EHLO PWS3.mxtoolbox.com
250-izanami.co Hello pws3.mxtoolbox.com [64.20.227.134]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP [719 ms]
MAIL FROM:<supertool@mxtoolbox.com>
250 OK [750 ms]
RCPT TO:<test@example.com>
550 relay not permitted [1141 ms]
PWS3v2 9719ms
I tried to send an email message and this is the log output in /var/log/exim4/mainlog
2015-08-07 14:58:07 1ZNh1m-00025M-ON == web-3ebnda@mail-tester.com <web-3EbnDa@mail-tester.com> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
Update:
A few more lines from my /var/log/exim4/mainlog
. As you can see, an email message which is supposed to be (auto)forwarded to my Gmail account doesn’t succeed.
2015-08-07 17:36:12 H=pws3.mxtoolbox.com [64.20.227.134] F=<supertool@mxtoolbox.com> rejected RCPT <test@example.com>: relay not permitted
2015-08-07 17:49:24 SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=128.red-79-157-253.dynamicip.rima-tde.net [79.157.253.128] input="^rn"
2015-08-07 17:51:47 1ZNjvu-0002TQ-Vb DKIM: d=google.com s=20120113 c=relaxed/relaxed a=rsa-sha256 [verification succeeded]
2015-08-07 17:51:47 1ZNjvu-0002TQ-Vb <= send-as-noreply@google.com H=mail-la0-f52.google.com [209.85.215.52] P=esmtps X=TLS1.2:RSA_ARCFOUR_SHA1:128 S=3356 id=CANY4h_3COHYMBQt1RA0QVgEc-LRv6ErtQPh68njd=dqPp_G=VA@mail.gmail.com
2015-08-07 17:51:47 1ZNjvu-0002TQ-Vb => example <example@izanami.co> R=localuser T=local_delivery
2015-08-07 17:51:47 1ZNjvu-0002TQ-Vb alt2.gmail-smtp-in.l.google.com [2607:f8b0:400c:c06::1a] Network is unreachable
-
#1
I ran a mxtoolbox report on our domain all the checks are coming green except one on top i just can’t figure out how to fix this any help on this would be great just to keep the security please note i have change our site name to abcxyz.com with 1.1.1.1 its ip address:
SMTP Valid Hostname Reverse DNS is not a valid Hostname More Info
SMTP Reverse DNS Mismatch OK — 1xx.xxx.xxx.xx resolves to abcxyz.com
SMTP Banner Check OK — Reverse DNS matches SMTP Banner
SMTP TLS OK — Supports TLS.
SMTP Connection Time 0.859 seconds — Good on Connection time
SMTP Open Relay OK — Not an open relay.
SMTP Transaction Time 3.344 seconds — Good on Transaction Time
WHM is is the dns server and rdns entry in our server provider is also set just dont know what i am missing:
our dns listings for this domain from our whm:
Code:
abcxyz.com. 3600 IN A 1.1.1.1 Edit Delete
localhost.abcxyz.com. 14400 IN A 127.0.0.1 Edit Delete
mail.abcxyz.com. 3600 IN A 1.1.1.1 Edit Delete
www.abcxyz.com. 3600 IN CNAME abcxyz.com Edit Delete
ftp.abcxyz.com. 3600 IN A 1.1.1.1 Edit Delete
cpanel.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
webdisk.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
webmail.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
pop.abcxyz.com. 3600 IN CNAME mail Edit Delete
abcxyz.com. 3600 IN TXT v=spf1 +a +mx +ip4:1.1.1.1 ~all Edit Delete
whm.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
cpcalendars.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
cpcontacts.abcxyz.com. 14400 IN A 1.1.1.1 Edit Delete
ns01.whmserver.com.abcxyz.com. 3600 IN A 2.2.2.2 Edit Delete
ns02.whmserver.com.abcxyz.com. 3600 IN A 3.3.3.3 Edit Delete
Last edited by a moderator: Sep 29, 2015
-
#2
Hello,
What is current hotname of your server? Please contact your server provider with your hotname and main server IP and ask them to setup the RDNS for your server.
-
#3
thanks for the reply, the current hostname for server is test1.domain.com an rdns is setup on the OVH portal for this host to 4.4.4.4
-
#4
Do i need to create a hostname A entry under the DNS zone for abcxyz.com for the current host, I still went ahead and create an entry of A record for test1.domain.com in abcxyz.com
now it looks like this but no luck : (
test1.domain.com.abcxyz.com. 3600 IN A 4.4.4.4 Edit Delete
-
#5
Hi,
You can create new DNS zone for your server host name.
A record of test1.domain.com should point and resolve to 4.4.4.4
And rdns of 4.4.4.4 should be to test1.domain.com
still issue? hit «post reply»
-
#6
Hi,
You can create new DNS zone for your server host name.
A record of test1.domain.com should point and resolve to 4.4.4.4
And rdns of 4.4.4.4 should be to test1.domain.com
still issue? hit «post reply»
Just checked my WHM there is already a zone for our server hostname which contains A records and other records this, plus i am able to do nslookup via servername or ip and resolve 100% correctly to server OVH RDNS records are also identical and refer to the IP and name of the server host.
I am literally pulling my hair at this stage……have read dozens forum not much out there for this specific issue..
I found this post but didn’t get anywhere with this : https://forums.cpanel.net/threads/r…e-smtp-greeting-must-have-an-a-record.473961/
-
#7
Can you DM me the domain name?
-
#8
Just checked my WHM there is already a zone for our server hostname which contains A records and other records this, plus i am able to do nslookup via servername or ip and resolve 100% correctly to server OVH RDNS records are also identical and refer to the IP and name of the server host.
Hello
It’s very possible that you have configured it correctly and the third-party utility you are using to test this with is checked cached records. You may want to test with a different website, or rely on command line tools such as «nslookup» or «dig».
Thank you.
-
#9
Can you DM me the domain name?
thanks for the reply got it sorted see my other comment
-
#10
Hello
It’s very possible that you have configured it correctly and the third-party utility you are using to test this with is checked cached records. You may want to test with a different website, or rely on command line tools such as «nslookup» or «dig».
Thank you.
Thanks Michael for pointing out I went out and tested with another provide check for MX and SMTP records and came out not a single issue so seems like only specific to mxtoolbox for some reason this issue.
thanks for the help on this, lesson learn always test with two different providers at the least.
-
#11
I am happy to see the results are normal at another provider’s utility. Thank you for updating us with the outcome.