A number of SBCGlobal email users are eager to use their email accounts from Exchange, but they are not able to do so because of the issues with ISP or PTR. If you too are looking to operate your SBCGlobal email account from Exchange, then read on.
Many SBCGlobal email users were using SBCGlobal email on MS Windows Server 2008. It was all going fine until past few days when they started encountering a problem on the domain. The domain was trying to get to @sbcglobal.net account, but it got stuck in the email queue. After that, it began to give errors to the SBCGlobal email users. This is one of those issues that SBCGlobal email users could never imagine getting in their systems. Now, they are all looking to find a solution to this problem.
The problem could have occurred due to a forged hostname for their email IP. Errors occurring from a web-based service these days are quite common and one should not feel scared of seeing those errors. The right thing for them to do is find an appropriate solution for that error and bring back the email service to normalcy. This particular issue, i.e., SBCGlobal email not working from Exchange find its roots in RDNS issue. Some users have identified the reason for the problem, i.e., RDNS not working properly with the ISP.
To resolve this issue, it is important that users provide answers to the following question:
- Are users able to use ISP in order to set up a PTR record for that public IP address and from that email server where the sending has taken place to the public FQDN of the server?
Some SBCGlobal email help and support providers have also told users to check whether the FQDN on the send connector matches with the PTR or not. Moreover, they have also told to check whether the PTR has a valid A record that returns to the same IP address.
Some SBCGlobal email users blame this issue on the changes that occurred in an SBCGlobal net email in the past few months because a single email server is not rejecting emails, but all emails that are sent to SBCGlobal.net are showing the same error, i.e., ‘possibly forget hostname’. Users have the right PTR records for all outgoing IPs.
A solution that works on this problem:
You need to IPChicken from your email server to get its IP. You need to confirm whether that’s the IP of your mail.domain record or not.
Ping –a from the WAN to the IP of your mail server. If this fixes your mail.domain record and ISP issue. If you are able to identify the issue to be within the ISP, then you will have to get in touch with the ISP and ask them to add a reverse PTR.
There is one more thing that you have to make sure of and i.e., NAT policies in the firewall are correct. If NAT policy is not right, then your outgoing IP is being blocked by the firewall. The problem is not in the incoming mail record.
Now, you will see that all emails that were queued are now delivered to the respective email addresses.