Get Satisfaction uses Javascript and cookies.

You'll need to enable Javascript and cookies to log-in and participate.

Share Follow

Know any helpful people?
Email this to a friend
- Your Name:
- Your Email:
- Email to: Enter up to 5 email addresses separated by commas
- Add an optional message
- Optional Message:
  Character limit of 1000 characters
- Or cancel
Twitter this
Share on Facebook
Get a short URL

Share it on these other sites

2 solutions marked best

4 replys made

2 persons participating

1 employee helping

The mood in here

happy 3

silly 0

indifferent 0

sad 0

Products & Services

Boxbe

Add a product

Tag this topic

Add a tag

SPF / DKIM Authentication Failure

My emails (from my mailserver) are being returned as having invalid spf and/or dkim signatures, but the other major email providers (google, yahoo, microsoft) are all able to verify my spf and dkim signing. How do I find out where I am not compliant?

Thanks!
ttyl
Dima

Inappropriate?

Reply to this problem

1 person has this problem

I have this problem, too! Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.

EMPLOYEE

Remove Inappropriate?
Delete or Edit

Boxbe Chris, Official Rep, replied on November 10, 2009 23:42

Dima,

Thank you for reporting this issue. Regarding verifying compliance, to verify which domains have SPF and DKIM records we use the following online tool: http://network-tools.com/

A) For SPF
domainname.com - using whatever the domain actually is.

Example:

gmail.com = has SPF
batman.com = has no SPF

B) For DKIM
_domainkey.domainname.com - replacing domain.com with whatever the domain is.

Example:

_domainkey.gmail.com = has DomainKey
_domainkey.hotmail.com = no DomainKey found

Thank you

I’m thankful

The company says this solves the problem

1 Comment Add a comment This solves the problem Mark as a company solution
Remove
ddbrodsky commented on November 17, 2009 19:27

Hi Chris,

Thanks for your response. Currently the txt entry for our dkim key is selector._domainkey. So it looks like we are being tripped by the selector; but both google and port25.com seem happy to use the selector. Also the software I used to generate the dkim created it with the selector. Is the selector part of a newer or older standard. All the literature I have seen seem to use the selector.

Thanks!
ttyl
Dima
EMPLOYEE

Remove Inappropriate?
Delete or Edit

Boxbe Chris, Official Rep, replied on November 25, 2009 11:22

Hi Dima,

We will pass this along to our Development Team to review and get back to you when we know more.

Thank you

I’m thankful

The company says this solves the problem

Add a comment This solves the problem Mark as a company solution
EMPLOYEE

Remove Inappropriate?
Delete or Edit

Boxbe Chris, Official Rep, replied on November 29, 2009 07:19

Please let us know the domain you are sending from, and is it possible to provide an example of a problem-causing message that was sent (date/time/recipient/subject would be ideal), so we can debug. You can send the information to support@boxbe.com and let us know it's been sent.

Thank you

I’m thankful

this solves the problem

Add a comment This solves the problem Mark as a company solution

Reply to ddbrodsky's problem

(Some HTML allowed)

Company participation

The mood in here

Products & Services

Tag this topic

Related topics in Boxbe

SPF / DKIM Authentication Failure