Many people use Exchange server on MS Windows Server 2008. But since few days, these users are facing problem whenever they were trying to get to @sbcglobal.net account. The SBC email account was stuck in the email queue and after some moment, it started showing an error to the users.

Some people have already found the main cause of this issue, which is most possibly a RDNS issue with the ISP. Questions like were you able to ISP setup a PTR record for that IP address (public), from that email server from which the sending has taken place to the public FQDN of the server? helped the experts check the accounts personally and troubleshoot.

Some experts have also told to check whether the Fully Qualified Domain Name on the Send connector is matched with the PTR. What most of the users think the reason for this very issue is the recent change that occurred in @www SBCGlobal net because there isn’t a single email server that is rejecting emails, but all the mails that are being sent to @sbcglobal.net are showing the same error, i.e., ‘possibly forged hostname’

The Most Possible Solution:

IPChicken from your email server to receive its IP. Do you have this IP of the mail.domain record that you are using? You will have to ping A form from WAN to mail server IP. Check if this fix mail.domain record issue or not. If it doesn’t fix that issue, then check, if it fix ISP. You will be able to know if it is ISP, which is creating the problem or the mail.domain record, and if it is ISP, then you will have to call the E-mail help & support team and explain them that they need to add a reverse PTR. People can also go check out SBCGlobal net email settings just in case they are skeptical about the settings.

User also have to ensure that the Firewall’s NAT policies are correct. If the NAT policy is not right, then there are chances that the outgoing IP is the Firewall. It is not there in the incoming email record. So do not forget to check on that too.