Mail Server News
05/11/2018 – Email from GMail Users
There have been a couple of issues receiving mail from gmail users recently where the gmail user said their email bounced sending to one of our users. The reason for this is that, while gmail does a fair job of blocking spam TO their system, when it comes to spam FROM their system, not so much. All free email services get abused by spammers and scammers at one time or another, gmail probably more than others. Spammers sign up for free accounts blasting out tons of spam without regard for how it affects other gmail users, and not caring if their accounts get cancelled as they only need to use them once. This usually results in the gmail servers involved being put on one or more blacklists for a time, which in turn causes problems for gmail users if the system tries to use those particular servers to send their mail.
Google actually is aware of this problem, yet still appears to do little to prevent it. In fact here is what they say about it in one of their knowledgebase articles. Bear in mind this article is written TO gmail users.
“Gmail sends mail from a number of different IP addresses that shift regularly. If one of your messages goes out from an IP address that was blacklisted after someone else used it to send spam, your mail can start getting bounced. Mail bounces only to recipients who’s mail servers use the RBL(s) that blacklisted the IP address, and only while the address remains blacklisted. Eventually, the RBL delists our server’s IP address, or Gmail assigns you another outgoing server, and your mail no longer bounces.”
Because so much junk does originate from gmail.com, whitelisting the domain is simply out of the question. We cannot in good conscience expose all our email users to that much abuse. So we handle problems on a case by case basis. Please keep this in mind if you suddenly can’t receive mail from a gmail user with whom you’ve corresponded for years. Remember also that the condition should be temporary, just until the gmail system sends their message from a server that is not blacklisted, or until the gmail server IP address is dropped from the blacklists.
09/25/2017 – Email to GoDaddy-Hosted Addresses Delayed
It has come to our attention that GoDaddy is having trouble with their email servers today. Messages sent to email addresses that are hosted by GoDaddy currently are being held in our outbound mail queue because our server cannot get them delivered. Our server will continue to retry sending periodically for up to 4 days from the time you initially clicked Send. If your message has been in the queue for an hour, you already should have received a notification from our server that there is a delay. If after 4 days it is still unable to deliver the message, it will notify you of the failure. If you have any questions about why this is happening, please contact your recipient and have them contact GoDaddy. Thank you!
01/26/2016 – UPDATE: Email to Comcast, AOL, and Q.com
As of this morning, our email is again getting to AOL.com users. If anyone can confirm the status of our email to Q.com users, please let us know. Thanks!
01/25/2016 – UPDATE: Email to Comcast, AOL, and Q.com
The missing Reverse DNS entries for our mail servers were replaced yesterday within a couple of hours after we discovered the problem. Delivery to Comcast addresses was restored relatively quickly. We’re not sure about Q.com addresses as we don’t have one of their emails with which to test. DNS at AOL apparently has not yet updated as they’re still blocking us as of about 11am this morning. However as soon as their DNS updates, we’ll again be able to send mail to AOL email customers. Again we apologize for any problems this may have caused and appreciate your continued support.
01/24/2016 – Email to Comcast, AOL, and Q.com
We were just made aware of a problem getting mail delivered to users of Comcast mail and possibly AOL and Q.com. Some mail is being returned and the bounce message mentions a lack of reverse DNS for our server. This feature had been in place since the server switch, so we’re not sure why it changed. However we’re in the process of taking care of it now, and hopefully it will be fixed by the end of the day. Because this is a DNS issue, and DNS takes time to propagate all around the internet, after the fix is in place, it could take 6 to 8 hours for the fix to propagate in North America, and 24 to 36 hours for the rest of the internet. We regret any inconvenience this may cause, and appreciate your patience and understanding during the propagation period.