日本語のみで絞り込む
2025/3/4 -The sender's mail server has invalid PTR record (reverse DNS). Resolution. Contact the server provider of the IP address in order to correct PTR ...
2014/12/23 -You need a PTR record that resolves 128.199.39.109 to the hostname of your sending server. Might also want to look into SPF records for your domain too.
2013/11/8 -When a user here sends an email to a particular domain it bounces back with: 450 4.7.1 Client host rejected: cannot find your hostname.
2013/11/22 -Check the DNS settings on the outbound mailserver. Make sure you alse have a PTR record set up for the hostname that is send with the EHLO/HELO ...
2014/10/26 -To fix this, the sender should amend their PTR record to something like mail.jalequity.com, then add an A record for mail.jalequity.com with the ...
It seems that we do not have a reverse DNS record configured for the remote.ourhostname.com which can be causing our emails to be handled as spam or rejecting ...
2017/5/18 -I am using Plesk Onyx Version 17.5.3 Update #6 Web Host Edition on Ubuntu 14.04.5 LTS. I get this error when users try to send mail to any adress @siol.net.
2018/8/22 -I'm currently messing around with my mail-setup here. Everything is working properly except receiving mails (which should obv. work). I'm running the setup in ...
2019/2/8 -You should be able to force a PTR record through unbound by adding the following to data/conf/unbound/unbound.conf in the server block.
2021/2/16 -Checks against the hostname are needed to ensure that the hostname is properly resolving to the server. Here are the commands needed to perform this check.