I just can't figure it out. I have one server running Plesk that hosts my sites and email. I have two other servers that provide DNS for the domains running on the first (my reason for mentioning this is that I'm not using Plesk's domain services). I have tried everything, but too many emails from domains on the Plesk server are going into the recipients junk mail box - this happens when emailing gmail, yahoo, and hotmail accounts and even with other recipients that are using Apple's Mail on their own email domain.
I've tried creating SPF records in DNS. Not sure if they've done anything.
I've checked the blacklists, and the IP's are not blacklisted.
Does anyone have any suggestions?
I'd pay a consultant to look into this for me. If I can find someone affordable.
Thanks in advance!
Full Version: But my emails not spam.
Are your SPF records correct? http://www.kitterman.com/spf/validate.html
Do you have PTR/rDNS on your main IP? This can be a very big deal. Is the hostname of your server a FQDN (which should match the PTR).
When it does go into a spambox for something like the apple mail, have you looked at the headers? Often times that can help if it tells WHY it made it there.
Do you have PTR/rDNS on your main IP? This can be a very big deal. Is the hostname of your server a FQDN (which should match the PTR).
When it does go into a spambox for something like the apple mail, have you looked at the headers? Often times that can help if it tells WHY it made it there.
QUOTE (eth00 @ May 21 2009, 02:52 PM) 
Are your SPF records correct? http://www.kitterman.com/spf/validate.html
Do you have PTR/rDNS on your main IP? This can be a very big deal. Is the hostname of your server a FQDN (which should match the PTR).
When it does go into a spambox for something like the apple mail, have you looked at the headers? Often times that can help if it tells WHY it made it there.
Do you have PTR/rDNS on your main IP? This can be a very big deal. Is the hostname of your server a FQDN (which should match the PTR).
When it does go into a spambox for something like the apple mail, have you looked at the headers? Often times that can help if it tells WHY it made it there.
Thanks for your response.
Here's the validation from the link you gave me:
CODE
Input accepted, querying now...
SPF records are primarily published in DNS as TXT records. The TXT records found for your domain are:
v=spf1 a mx ptr ~all
SPF records should also be published in DNS as type SPF records. This is new and most implementations do not support it yet.
No type SPF records found.
Checking to see if there is a valid SPF record.
Found v=spf1 record for DOMAIN.NET
v=spf1 a mx ptr ~all
evaluating...
SPF record passed validation test with pySPF (Python SPF library)!
SPF records are primarily published in DNS as TXT records. The TXT records found for your domain are:
v=spf1 a mx ptr ~all
SPF records should also be published in DNS as type SPF records. This is new and most implementations do not support it yet.
No type SPF records found.
Checking to see if there is a valid SPF record.
Found v=spf1 record for DOMAIN.NET
v=spf1 a mx ptr ~all
evaluating...
SPF record passed validation test with pySPF (Python SPF library)!
I believe I have checked this before.
Using DNS Stuff, I did a rDNS check:
CODE
70.86.***.** PTR record: create.DOMAINNAME.NET. [TTL 86400s] [A=70.86.***.**]
It matches the Main IP.
Using DNS Stuff, DNS Report, I also got this for SPF Record:
CODE
You have an SPF record. This is very good, as it will help prevent spammers from abusing your domain. Your SPF record (I don't check to see if it is well designed!) is:
"v=spf1 a mx ptr a:create.DOMAINNAME.NET mx:mail.DOMAINNAME.NET mx:create.DOMAINNAME.NET ~all" [TTL=86400]
"v=spf1 a mx ptr a:create.DOMAINNAME.NET mx:mail.DOMAINNAME.NET mx:create.DOMAINNAME.NET ~all" [TTL=86400]
One thing that concerns me is I got this for "Mail Server Hostname In Greeting":
CODE
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.DOMAINNAME.NET claims to be host create.DOMAINNAME.NET [but that host is at 70.86.***.**8 (may be cached), not 70.86.***.*9]. <br />
mail.DOMAINNAME.NET claims to be host create.DOMAINNAME.NET [but that host is at 70.86.***.**8 (may be cached), not 70.86.***.*9]. <br />
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.