I have some important follow-up to my last post about the GoDaddy issue.
Back on Friday, July 17, I posted to the blog here the lack of responsiveness that we got regarding what seemed to be pretty clearly a configuration issue on GoDaddy’s mail servers. I’m including my written email to their support below, as well as the eventual written response that I got from their Office of the President as well.
Late Friday afternoon I received a call from a very well-spoken and pleasant individual at GoDaddy named Daniel Butler. In that conversation he listened to my concerns, and explained how he felt that they were doing the best thing in the interests of GoDaddy by applying the Spamhaus PBL database the way that they did. GoDaddy also agreed to ‘whitelist’ our specific IP address. The bottom line is that GoDaddy knows that the PBL is a combination of policy blocks and straight up dynamic IP’s, and knows that using this list will give them false positives. They’re trying to convince Spamhaus to break these lists out so that they could use one or the other instead of being forced to use both, but in the meantime will continue to use the PBL list to block any incoming messages that reference IP’s there. Mr. Butler said that the number of people being affected by these false positives is vanishingly small, far less than 1% of their total webmail user population. Their solution to customers adversely affected by this is for them to contact Spamhaus or GoDaddy directly and get the IP’s whitelisted or removed from the PBL entirely.
I’m not 100% convinced that this would be satisfactory to everyone affected, but since they whitelisted us WRLR hasn’t had the issue anymore.
Of course, if our IP changes – which, as a hosted dynamic IP it almost certainly will – then I’ll have to ride the finger-pointing merry-go-round again, won’t I?
Our Office of the President has responded to your request, details of which are described below:
|Office of the President Response|
Dear Mr. Kastler,
Your email correspondence has been directed to the Office of the President
for further review.
As we understand, you are receiving bounceback errors when attempting to
send email to addresses in Go Daddy’s system based on the current SPAM and virus
filters. Per your discussion of the included information with Mr. Butler, we would like to forward these details for your record.
It appears, per your correspondence that the issue is due to the emails
that contain a link to ftp://wrlr[DOT]dyndns[DOT]org. Based on researching this link
and to confirm, we can see that it resolves to the IP address of 220.127.116.11,
which, is currently listed in Spamhaus.org‘s PBL. We do appreciate your concerns regarding
Go Daddy’s use of the PBL and your desire to obtain the appropriate details
about this matter.
Please understand that due to the fact that spammers are now using virus
infected personal computers to host sites as well as send spam, blocking sites
hosted on dynamic pools is very useful, and stops a large amount of spam with
very few false positives. While the Spamhaus PBL is currently a “policy”
blocklist, listing any system that should not send mail, it began life as a
“pool” blocklist, and in fact was started when the dynamic pool blocklist we
previously used was given to Spamhaus. We simply continued to use it the way we
had previously used it. Unfortunately, Spamhaus has now allowed non-pool
addresses to be voluntarily included in the PBL (the “policy” block list), and
no longer offers a list that is purely dynamic pool IPs. However, the vast
majority are still dynamic pool IPs, and the PBL remains the only dynamic pool
list at this time. Unfortunately, as these two very different concepts are
combined into the one PBL, results from both the “policy” block list as well as
the “pool” block list are returned for filtering at this time. Please note that
we have been in contact with Spmahaus regarding this matter in hopes of
splitting these two block lists up.
Spamhaus will remove IPs listed in the “policy” block list on request, and
we recommend removing any legitimate web hosts from the PBL. If a server should
not be sending mail, this is easily enforced at the router or firewall level.
Blacklists are, and always have been, a last-resort measure for dealing with
irresponsible ISPs who cannot or will not control their network through other
means. It should not be necessary for a responsible provider to voluntarily list
their own IPs in any external blacklist. Although there may not be a perfect
method to perform the spam protection which is necessary in today’s internet
environment, we do believe we have the best method available. If this current
condition creates an inconvenience for you, we sincerely apologize. Please know
we are constantly researching ways to improve the service we provide, and if
better methods become available in the future, we will adjust our techniques to
We would like to point out that we do employ various methods to help combat
spam and Go Daddy does take a very active role to do so. These methods and
means, however, are not to block legitimate messages or senders. Rather, these
means are in place to protect Go Daddy’s customers and their own contacts as new
viruses, malware, and other such infectious applications are so easily spread
without any knowledge these days.
We do hope this information has been helpful to you and again apologize for
any inconvenience this may cause. Based on your conversation with Mr. Butler, it appears this matter has been resolved amicably at this time. Additionally, should there be any other questions or
concerns with which our office may assist; please do not hesitate to contact us
|Thank you for your response.
As a journalist, I want to make sure I get my information correct. I plan
Here is my takeaway information that i will use to create my lead for this
If I have any of the information above incorrect, please let me know prior
I would also be pleased to interview a representative from godaddy about