204.14.107.174 is listed on spamcop.
spamcop SpamCop.net - Blocking List ( bl.spamcop.net ) bl.spamcop.net LISTED
please take care.
Mails should go fine now.
still mail not reach recipient.
still blacklisted:
SpamCop.net - checkblock
There is no way to expedite the listing.
If the mail hasnt reached intended receipient, it can be something else. Please update your ticket with requested details
ok, thanks.
200.12.238.174 does not like recipient.
Remote host said: 550 Blocked - see SpamCop.net - Blocking List ( bl.spamcop.net )
Giving up on 200.12.238.174.
!!!
this will be corrected shortly.
The issue is SpamCop’s policy against misdirected bounces. Some spammer is hitting a customer’s forwarder with spam which is getting bounced to different email addresses (faked headers).
They expect us to find these mail boxes without any information.
We are working on it. Hopefuly SpamCop should get back to us shortly.
We also plan to increase our pool of free SMTP IPs so in the future we could quickly change it so mail wouldn’t be affected (this is transparent to the customers)
This IP is also listed 204.14.104.85. I believe it is mail4.
SpamCop says this about it being listed: In the past 61.7 days, it has been listed 7 times for a total of 4.6 days.
204.14.107.174 (Mail3) and 204.14.107.1 (Mail1) were unlisted by SpamCop and we do not expect them to be listed again. SpamCop forwarded us info on the source of the misdirected bounces and they were taken care of.
204.14.104.85 (Mail4) just got listed. The outgoing IP has been changed to 204.10.105.68 10min back so you will receive no spamcop bounces. We have contacted SpamCop about .85 and hopefully we should have it pemanently unlisted in under 20 hours
In the last month, some of our mail server IPs have been blacklisted due to SpamCOPs unfair misdirected bounces policy. We are now working with SpamCOP to find the sources of these bounces and ensure it doesn’t happen again.
Also, being listed for 4.6 days as per spamcop’s website doesn’t mean you couldn’t send email for 4.6 days. we change outgoing IPs very quickly upon a blacklist.. hence the actual blacklist wouldn’t have lasted more than an hour in each instance
204.14.107.174 listed again: SpamCop.net - Blocking List ( bl.spamcop.net )
It also mentions “SpamCop spam traps” - are they working with you to trace the source of what’s triggering these?
The problem is that everytime they tell us some auto responder caused an issue. We disable it and another autoresponder pops up. SpamCOP has told us very clearly we must stop offering auto responder service if we stop getting blacklisted.. This is pretty ridiculous.
We just changed Mail3’s outgoing IP. So 204.14.107.174 is no longer being used. Try resending that email
It’s not ridiculous if they’re being used to send spam…
is it not possible to impose a mass-mailing limit on auto-responders in the same way as other mail accounts?
The changing IP method is not going to cure the problem in the long run. It benefits spammers as well as legitimate users, and conceivably might lead to spamcop listing the entire range when one of them causes a problem.
from SpamCop.net - SpamCop FAQ: Why are auto responders bad? , “There is also an experimental patch for qmail which allows you to send bounces, but isolate them on a different IP address (so that spamcop can block them without blocking other mail):”. Could this method be used for all autoresponders?
SpamCop wants ALL ISPs to stop offering autoresponders… Because it can be abused for bounces and there is no way to control it.
Plus bro, you are not understanding is that alot of these autoresponders are not actually being targetted by spammers. They themselves get hit by a spam message from some source, get autoresponded and end up in a spam trap. So even if we had some mechanism to limit mass autoresponding.. it would not help
There is no way to limit autoresponders. That is the way qmail works.
Also, these aren’t bounces.. all the patches mentioned we have already applied. We have patches to prevent over quota and no user bounces.. That patch you mentioned cannot be applied in our HSphere mail setup (needs a qmail recompile)
The changing IP solution is something we are doing only temporarily while we also work with spamcop and try figuring out a permanent solution.
So that there’s no way to limit autoresponses would seem to be the main problem…
Well, having already decided not to be a part of the problem and contribute to the plethera of unnecessary emails flying around the Internet, we have already 80-90% opted not to use autoresponders (we don’t use the HSphere facility at all, only selected web ‘contact us’ type forms) and would happily support disabling this feature.
Having said that though I add that we realise this is not feasable or entirely possible. Aside from not beliving control and regaultion is a desirable form of action, many applications already have autoresponder facilities that are outside of the control of JodoHost and do infact serve a valuable purpose e.g. newsletter sign-up confirmation of email requests.
We believe a better solution possible lies in best practice behaviour and education (sharing information). Here are some suggestions:
a) Don’t use the HSphere autoresponder (or anything else that unintellegently replies to all email received)
b) Only send an autoresponse from a submitted web form that performs server side validation checks to prevent the form being exploited for SPAM
c) If an autoresponse to an email address such as [email protected] is warrented (because of, for example, a ticket tracking system that provides a tracking reference number) require customers to first register their email addresses and only autorespond to valid email addresses.
These are only suggestions and would still need to be practically actioned. Any comments, revisions or further ideas are welcome and encouraged.
Regards,
“Tired of the SPAM-ache”
[QUOTE=com-du-it.com]
Well, having already decided not to be a part of the problem and contribute to the plethera of unnecessary emails flying around the Internet, we have already 80-90% opted not to use autoresponders (we don’t use the HSphere facility at all, only selected web ‘contact us’ type forms) and would happily support disabling this feature.
Having said that though I add that we realise this is not feasable or entirely possible. Aside from not beliving control and regaultion is a desirable form of action, many applications already have autoresponder facilities that are outside of the control of JodoHost and do infact serve a valuable purpose e.g. newsletter sign-up confirmation of email requests.
We believe a better solution possible lies in best practice behaviour and education (sharing information). Here are some suggestions:
a) Don’t use the HSphere autoresponder (or anything else that unintellegently replies to all email received)
b) Only send an autoresponse from a submitted web form that performs server side validation checks to prevent the form being exploited for SPAM
c) If an autoresponse to an email address such as [email protected] is warrented (because of, for example, a ticket tracking system that provides a tracking reference number) require customers to first register their email addresses and only autorespond to valid email addresses.
These are only suggestions and would still need to be practically actioned. Any comments, revisions or further ideas are welcome and encouraged.
Regards,
“Tired of the SPAM-ache”
[/QUOTE]
Please provid more details for suggestion C:
If an autoresponse to an email address such as [email protected] is warrented …
I have autoresponse anable for the [email protected] mail box. how do i set it so customers will be equire to first register their email addresses (register where ?)???
am still getting blocked responses today - for hours already, all on 204.14.107.202 it seems.
cant we get this IP changed as well?
It was changed a few hours ago. Mail1 is 204.14.107.1; no longer .202
try resending, must be cached
Also.. we just disabled a major source of misdirected bounces on mail1 (autoresponder again)
If mail accounts are set up with SPF, would that help solve the problem of faked headers with autoresponders?
Also, does an autoresponder happen before the incoming mail goes through spam checking? If so, that’s a major problem right there… hopefully incoming mail gets checked first before triggering the autoresponder…
I would be quite happy if the autoresponder was disabled. As a reseller I do not have the autoresponder enabled in any of my hosting plans. There’s enough junk mail circulating as it is without autoresponders replying to bounces containing spoofed return addresses.
[QUOTE=Mio]
Please provid more details for suggestion C:
If an autoresponse to an email address such as [email protected] is warrented …
I have autoresponse anable for the [email protected] mail box. how do i set it so customers will be equire to first register their email addresses (register where ?)???
[/QUOTE]
You need to run an intelligent autoresponder script. The script will check a selected POP3 mailbox and respond only to those messages that have a sender’s address matching one in its database. Try Google with “autoresponder script”.