May be i understand now more Yes, above combination "ip from pool used by ISP" mean that you have ip which used by ISP for dynamicaly assign to dialup users. ISP usually have a very great range of ip's and dialup users get one of above ip's dynamically and randomly when connect to ISP modem pool.
Rustelekom LLC Dedicated server since 2002, RIPE NCC member, LIR, AS51168
Originally posted by worldhosting May be i understand now more Yes, above combination "ip from pool used by ISP" mean that you have ip which used by ISP for dynamicaly assign to dialup users. ISP usually have a very great range of ip's and dialup users get one of above ip's dynamically and randomly when connect to ISP modem pool.
So are you saying that even though I have a dedicated IP, say, 10.1.1.1, someone could potentially sign onto the internet via a dial-up ISP and have 10.1.1.1 assigned to him/her while on that session?
Hm now we are getting somewhere. I checked mine, but it did not state anything about a dynamic pool, etc. What about this IP address: 188.8.131.52. I just show that it is listed to CalPop with nothing about the dynamic pool, etc?
Now my mail IP is 184.108.40.206. So it looked like that were blocking an entire IP range or their system did not know what it was was doing.
220.127.116.11 was actually listed on blacklists, but mine was not. And about 2 weeks later, I was able to email Godaddy again. And then all of a sudden, we started getting the above message.
I first emailed them, they said
The IP is part of a dialup pool used by an Internet Service Provider. Due to the large number of virus-infected personal computers on cable/dsl/dialup connections, we no longer accept mail directly from these sources. The sender will need to configure their email software to send outgoing mail through their ISP's dedicated outgoing mail server. The server is usually named 'smtp.example.com' or 'mail.example.com'. The ISP's support line will be able to give you more details. We have whitelisted the mail server of most major ISPs, so the mail will get through if sent through these systems.
Now, having my clients do this, would be ridiculous. This could cause problems for other clients. Since the ISP is not the SOA for their domain name, reverse DNS would fail.
After about 20 support tickets, and a few phone calls (a few of them would not even speak with me because I was not a customer of theirs):
I have received a reply stating that this IP address has been unblocked, but if we find that this mailserver is involved with spam or viruses, it will be blocked again.
They still do not understand but at least the IP is unblocked on their server.
To even add more, I found out that some of their replies to my email address was being sent to my junk box because their SPF records were set up incorrectly! I think they fixed them but you would think they would have this fixed properly