Re: IP not authorized
Tony Yarusso schrieb: We're having no end of trouble setting up a new server here, so I'm hoping someone can explain what's going on. Basically, we have a new server that of course will generate messages from cron jobs, PHP mailers, and that sort of thing, and we want them to be able to make it out to people. To do so we wanted to use GMail as our SMTP server to relay through. We seem to have gotten all of the TLS stuff taken care of okay, but now are getting the error described on http://mail.google.com/support/bin/answer.py?answer=10336. It appears that this comes up on the _Receiving_ end of things, with any address that belongs to Google (either through standard GMail or Google Apps). We've tried sending out through GMail, no-ip's alternate port SMTP, and Comcast's SMTP. Other errors occur with different providers, which I suspect are from the same root reason. My theory is that it has something to do with the A/MX/PTR/SPF records for the domain. The domain is flamtap.com The IP address is currently 76.113.154.202, but is dynamic (through no-ip.com) That address also goes by c-76-113-154-202.hsd1.mn.comcast.net Any ideas of what we need to do to appear legitimate and not get caught by anti-spam measures? Maybe you have to check your spf record? # host 76.113.154.202 202.154.113.76.in-addr.arpa domain name pointer c-76-113-154-202.hsd1.mn.comcast.net. # host -t txt flamtap.com flamtap.com descriptive text v=spf1 include:no-ip.com -all # host -t txt no-ip.com no-ip.com text v=spf1 ip4:204.16.252.0/24 ip4:69.65.19.112/28 ip4:69.65.5.96/27 ip4:216.66.37.8/29 -all
Re: IP not authorized
On Oct 29, 2008, at 9:03 PM, Tony Yarusso wrote: We're having no end of trouble setting up a new server here, so I'm hoping someone can explain what's going on. Basically, we have a new server that of course will generate messages from cron jobs, PHP mailers, and that sort of thing, and we want them to be able to make it out to people. To do so we wanted to use GMail as our SMTP server to relay through. We seem to have gotten all of the TLS stuff taken care of okay, but now are getting the error described on http://mail.google.com/support/bin/answer.py?answer=10336. It appears that this comes up on the _Receiving_ end of things, with any address that belongs to Google (either through standard GMail or Google Apps). We've tried sending out through GMail, no-ip's alternate port SMTP, and Comcast's SMTP. Other errors occur with different providers, which I suspect are from the same root reason. My theory is that it has something to do with the A/MX/PTR/SPF records for the domain. The domain is flamtap.com The IP address is currently 76.113.154.202, but is dynamic (through no-ip.com) That address also goes by c-76-113-154-202.hsd1.mn.comcast.net Any ideas of what we need to do to appear legitimate and not get caught by anti-spam measures? You could always configure Postfix to login using a gmail account for relay access; http://www.opengroupware.org/en/users/docs/snippets/Mail/postfixauth.html has some details on this.
