Many SBCglobal email users are not able to send emails from SBCglobal email from the exchange. They were able to do so a few days ago, but now, they are getting different errors. To know more about the issue, let’s check the steps given in the tutorial.
SBCglobal email account can be accessed from the exchange, however, some users are not able to access if from there due to ISP related issues or PTR. Let’s delve into the details of this problem in order to find out what exactly the issue is and how it can be fixed.
Many individuals are using Exchange server on Microsoft Windows Server 2008. It was all going great until the past few days when a new problem begins to surface on the domain when the server was trying to reach @sbcglobal.net account. The account got stuck in the email queue after which, it began to give errors to users. The problem was weird and out of people’s understanding, but it would have risen from the webmail platform. The error that people started to receive are here below:
The problem was related to the forged hostname for email IP. Users were not sure as to what the problem was, so they started looking for it along with the solutions. Internet is the best source for searching for new things, but at times, people are not able to find answers to certain problems, especially the complicated ones.
When SBCglobal email experts came to know about the problem, they tried to provide troubleshooting steps to users, but prior to that, they asked a few questions from the users such as;
- Are you able to do ISP setup a PTR record for a public IP address?
- Are you able to do ISP setup from the email from which email has been sent to the public FQDN of the server?
Some email experts have also encouraged email users to check if the FQDN on the ‘Send Connector’ matches with the PTR. Along with that, they also told to check the PTR, if it has a legitimate A record, which goes back to the same IP address. A common perception among users is that the problem has occurred due to the recent changes in the SBCglobal email, as there is not one email server, which rejects emails, but all the emails that are sent to SBCglobal.net are showing the same error, which is ‘possibly forged hostname’. Many users have a proper PTR record of all their outgoing IPs.
The solution to the problem:
IPChicken from your email server in order to receive its IP. You need to check whether you have this IP of the mail. domain record, which you are using. Moreover, you have to ping A form to your email server IP from WAN. Also, check if the fix mail.domain record is an issue or not. If it is not, then you need to check if it fixes ISP. It is now possible for you to know if the ISP is causing the problem or mail.domain record. If you are sure if it is the ISP, then consult SBCglobal email support, explain the problem that you are facing and ask them to add a reverse PTR. Also, check the firewall’s NAT policies if those are correct or not. If the NAT policy is not correct, then there are chances of outgoing IP being blocked by the firewall, especially when it isn’t present in the incoming email record.