Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm getting the following in my mail logs on my app server:

550-5.7.1 [67.23.15.78] The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers. Please use the SMTP relay at your 550-5.7.1 service provider instead. Learn more at 550 5.7.1 http://support.google.com/mail/bin/answer.py?answer=10336

I've checked and the IP is not listed on any PBL/SBL/etc that I know of. The domain name in the FROM: email address is a CNAME to our app server's primary domain (djangostage.farstarserver.com). We have a PTR record for the server's IP, so reverse DNS resolves to the same domain (djangostage.farstarserver.com). We also have the following SPF record set up for the domain to allow our vhost domains on that server to send email under their own domains:

"v=spf1 a a:django.farstarserver.com -all"

Any ideas why Google is blocking our server?

share|improve this question

1 Answer 1

Did you try clicking on the link in your question? It explains the situation rather nicely.

In addition to being blocked by Gmail, your IP is listed in the SpamHaus PBL. The same range is probably listed in similar DNSBLs run by other organisations. If you want to reliably send mail from this IP address, you will have to contact all of them.

SpamHaus suggest you read the RackSpace AUP before requesting removal. I would recommend finding a different IP to send mail from.

Talk to Slicehost/Rackspace. Use their SMTP relay or upgrade your package to one that is allowed to send mail.

Note that it is practically impossible to send email from an EC2 IP address too. That's why Amazon run SES.

share|improve this answer
    
I don't think the link explains it very well -- it doesn't say the real reason I was blocked, other than "the IP is not authorized". Well, how does one become authorized? Also, it's Rackspace cloud -- and yes, I've put in a support ticket. They said to contact Google (which, as most people know, is a dead end). –  Ben Davis Feb 28 '13 at 23:43
    
Spamhaus is the only blacklist: mxtoolbox.com/SuperTool.aspx?action=blacklist%3a67.23.15.78# –  Gaia Mar 1 '13 at 0:18
    
I checked the IP, it is not listed on any spamhaus blacklists. –  Ben Davis Mar 1 '13 at 17:41
    
@BenDavis Yes it is. It's in the PBL. Regardless of that, Google don't use SpamHaus so requesting removal from the Spamhaus PBL won't help your deliverability at Gmail. –  Ladadadada Mar 1 '13 at 17:46
    
Odd, I could have sworn when I checked that it was not listed. I have no idea why I didn't see it earlier (perhaps I typed the wrong IP). I'll try it anyway and see. Are you sure they don't use Spamhaus in any way? I know that spamhaus keeps a list of blocks of IPs that are considered "non-commercial", and as I've recently learned, the ip's rackspace hands out for its cloud servers are included in those blocks. –  Ben Davis Mar 1 '13 at 17:51

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.