Wild west has the most draconian of spam filters which have the effect of rendering your email service with them practically useless! Many companies that we deal with on a daily basis report the same issue, and these are reputable companies.
If a company uses a dynamic ip to send email (like most small businesses) they are highly likeyl to be bounced by godaddy and wild west.
I recently had a case that godaddy was bouncing btinternet addresses, and short of getting each of the companies that send mail to us to have a static ip address, we had to obviously move to another address.
It would be amazingif you could turn it off but you can't so you have to move. Even their whitelist system will not allow the emails to be delivered.
Main Topics
Browse All Topics
by: marc_nivensPosted on 2005-11-18 at 16:19:10ID: 15324050
Ok first lets break down the mail to ccil.org.
192.190.237.100 does not like recipient.
Remote host said: 550-Verification failed for <private@mcgrailgroup.com>
550-Called: 64.202.166.12
550-Sent: RCPT TO:<private@mcgrailgroup.c
550-Response: 553 192.190.237.* rejected due to spam, contact 480-505-8877 (Attack detected from pool 192.190.237.216)
550 Sender verify failed
Giving up on 192.190.237.100.
Notice the 550-Sent: RCPT TO:<private@mcmailgroup.co
This is an address in your domain, not ccil.org. If you were sending a message to ccil.org it should RCPT TO a ccil.org address. From the rest of the
message it appears that once you connect to their mail server and issue MAIL FROM:<private@mcgrailgroup
to smtp.secureserver.net (your hosting provider) and issues a RCPT TO for the mail address you are sending from. Likely this is a step their mail server
uses to verify the sender before allowing the message to be accepted (antispam measure). When it issues the RCPT TO it receives the 553 error and
disconnects. This then causes your message to fail.
Now when they send to you:
private@mcgrailgroup.com
SMTP error from remote mailer after RCPT TO:<private@mcgrailgroup.c
host smtp.secureserver.net [64.202.166.12]: 553 192.190.237.* rejected due
to spam, contact 480-505-8877 (Attack detected from pool 192.190.237.216)
This rejects the message with the same error as the other one. The message is the same because in both situations the ccil.org mail server is connecting
to smtp.secureserver.net and issuing a RCPT TO and getting a 553. Now the $64,000 question, why is it rejecting?
Well look closely at the description:
553 192.190.237.* rejected due to spam, contact 480-505-8877 (Attack detected from pool 192.190.237.216)
The smtp.secureserver.net server appears to be on a subnet that is being categorically rejected by the secureserver mail server.
Notice it says 192.190.237.* which indicates that entire subnet (assuming regular class C mask) is being rejected. Its possible that
secureserver.net has either rejected this IP block or its on a blacklist somewhere.
The only way to really know is to call the number in the NDR and find out. Not much you can do from the client end to fix this that wouldn't end up
being an inconvenience.