According to SpamCop, we spend about 10% of our time blacklisted.
It’s getting hard to explain to customers. And, I don’t think it’s our (mine, the customers, or even JodoHosts) fault. Personally, I’m getting tired of SpamCop as a system or even as a concept. Too many civilian casulties.
They list any and all auto responders as spam these days, if one auto reply comes in they list it. Many times it is what we would call very legitimate auto replies as well, but some of thier users/staff send the report in anyway.
The ips are automatically swapped within 5 minutes if they get blacklisted by a script we wrote.
So any returned email would have been within those 5 minutes. Just resend it
[QUOTE=Yash]
The ips are automatically swapped within 5 minutes if they get blacklisted by a script we wrote.
So any returned email would have been within those 5 minutes. Just resend it
[/QUOTE]
Didnt work for me.
bounced back twice in good while (ie - much longer than 5 minutes)
212.150.49.2 does not like recipient.
Remote host said: 550 5.7.1 Blocked - see SpamCop.net - Blocking List ( bl.spamcop.net ) @ Giving up on 212.150.49.2.
In that case the issue was most liekly the receiving mail server has cached the spamcop entry. You shouldn’t have an issue at another server and usually caches clear within an hour
both the IPs you report belong to the same server mail1 and we did act on its spam reports so hopefully this case of listing wont happen again
[QUOTE=Yash]
In that case the issue was most liekly the receiving mail server has cached the spamcop entry. You shouldn’t have an issue at another server and usually caches clear within an hour
both the IPs you report belong to the same server mail1 and we did act on its spam reports so hopefully this case of listing wont happen again
[/QUOTE]
I thought the whole idea of having the IP change automatically is to overcome the cache - that the next time a mail goes out, it goes out on a different IP, so even if the initial IP was cached, the next email it still coming from a fresh IP.
?(
it was not using this IP for the last 24 hours now, it has just moved back to that IP.
Well then i guess the plan isnt working, because folks (me!) are still getting blocked by cached IPs in ISPs. the loop should then be longer than 24 hours. But anyway - i thought Yash said the cache should bust in 1 hour, a lot less than 24.
I was not talking about cache, just saying that the blocked ip had not been used for over 24 hours, until about the time I posted before it started being used agian. The cache should not last 24 hours at all, and there is no listing now.