| Posted by Cameleon, 04-19-2009, 12:38 AM | | Hello, i been trying to get SPF to work
And still can't quite say what is wrong, someone could help plz?
:
Connected to 193.17.41.123 but sender was rejected.
Remote host said: 550 Bad SPF records for [mydomain.com:myserverip], see http://spf.pobox.com/
--- Below this line is a copy of the message.
Received: from static-ip-**-**-***-***.inaddr.server.com (HELO mail.mydomain.com) (second_server_ip)
I got entry in DNS for every domain like this:
domain.com TXT v=spf1 a mx ptr -all
anyone?
|
| Posted by mugo, 04-19-2009, 03:41 AM | | The machine sending the mail for the domain in question (domain.com) must be named in an A or MX record for domain.com.
Not sure what DNS server you are running, but you may need to enclose your record in quotes:
"v=spf1 a mx ptr -all"
The -all is a Hard Fail, try setting it to ~all (soft fail) and try sending, that will tell you if it's your syntax or not.
|
| Posted by net, 04-19-2009, 06:18 AM | | Moved > Technical & Security Issues.
|
| Posted by Cameleon, 04-19-2009, 04:05 PM | | okie, now i am getting this:
Hi. This is the qmail-send program at ********server.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
:
Connected to ***.***.138.18 but sender was rejected.
Remote host said: 553 5.7.1 Hello [**.***.183.234], for your MAIL FROM address policy analysis reported: Your domain is not liked source for email
What does it mean, and how to fix it?
|
| Posted by mugo, 04-19-2009, 04:09 PM | | Ouch, that sounds like you may be blocked by a blacklist.
It's specifically saying your domain is not liked.
Lookup your IP here and see if anyone is blocking:
http://www.mxtoolbox.com/blacklists.aspx
|
| Posted by Cameleon, 04-19-2009, 04:43 PM | | only last reports
BGISOCBL Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
DSBL Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
DSBLALL Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
DSBLMULTI Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
NJABLDYNA Listed TIMEOUT 0 0
SNARK Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
TRIUMF Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
US Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
WYTNIJ Listed TIMEOUT Return codes were: ERROR, Reponse code=2 0 0
rest is ok
Last edited by Cameleon; 04-19-2009 at 04:43 PM.
Reason: forgot
|
| Posted by mugo, 04-19-2009, 06:03 PM | | Blocks are actually shown at the top if there are any, so you are clear on theses major blacklists.
Try removing your SPF record all together and sending.
This line:
policy analysis reported: Your domain is not liked source for email
-means you may have made it onto their own list, maybe from sending too much or being tagged as SPAM too many times.
Is Gmail the only place giving you trouble?
|
| Posted by Cameleon, 04-19-2009, 06:45 PM | | Nope only some polish providers that i am aware of...
What do you think i ashould do now?,
Strange thing is that, my mail goes "sometimes" thru my main server ip but not the other IP wich i have MX and SPF record on.
I checked that services and most of theem are just gone, so timeout is ok i think.
Last edited by Cameleon; 04-19-2009 at 06:58 PM.
|
| Posted by Cameleon, 04-19-2009, 07:07 PM | | I olso got this iformations:
RESULT: mail.mydomain.com
Banner: 220 my.servername.com ESMTP
Connect Time: 0 seconds - Good
Transaction Time: 0.719 seconds - Good
Relay Check: OK - This server is not an open relay.
Rev DNS Check: OK - **.**.255.122 resolves to static-ip-**-**-255-122.inaddr.server.com
GeoCode Info: Geocoding server is unavailable
Session Transcript:
HELO please-read-policy.mxtoolbox.com
250 server.name. [141 ms]
MAIL FROM:
250 [297 ms]
RCPT TO:
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7. [141 ms]
QUIT
221 server.name. [141 ms]
|
| Posted by mugo, 04-19-2009, 08:05 PM | | Be aware that MX has nothing to do with your sending of mail, this is for your incoming mail only. When someone is sending your domain mail, they lookup your MX records, and try to deliver mail. Setting MX records doesn't tell your mail server which machine to send AS, it only tells remote machines where to send mail into your domain. Your SMTP server will have a way to bind or name the IP addresses is operates on, which is the IP you are connecting to other mail servers trying to deliver mail remotely.
SPF only relates to you sending mail...when users connect to your SMTP server and send mail to a remote account, it should be sent through a configured IP address. This IP address should be known, and for the same mail server / domain, it should not deviate. How it relates to your MX is, you publish a SPF record that says "any machine I name here may SEND mail on this one domains behalf".
The best way to find out what is going on is to look in your SMTP logs...this will usually log thing form the other mail servers that you don't get back in headers...usually there will even be URL's to direct you to why you were blocked and further info.
I think log file checking is your next best step.
|
|
 Add to Favourites
 Print this Article
|
