Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to increase email deliverability, from what I read, most important things I need to have set are SPF records, DKIM and sender ID, I set SPF and DKIM, but...

  • "sender ID" is same as "SMTP ID" from email header?
  • how do I setup a sender ID ?

// using Cent OS on my servers

share|improve this question

migrated from Sep 17 '11 at 22:24

This question came from our site for professional and enthusiast programmers.

up vote 2 down vote accepted

Sender ID is the next generation SPF that hasn't happened yet. Basically nobody supports it and I feel confident in saying you'd be wasting your time. SPF is widely supported. DKIM is supported by most of the big guys, and any smaller ones that are serious about spam.

If you really want to setup Sender ID, it's just a series of SPF-like DNS records. The contents of the record are identical to SPF except the beginning, because the (possible multiple) SenderID record applies to different aspects of the e-mail depending on the contents of the record.

By example, if the record starts with:

spf2.0/mfrom, such as spf2.0/mfrom mx -all then the "mx -all" part applies to the "From" header.

spf2.0/pra, such as spf2.0/pra mx -all then it applies to the MAIL FROM: protocol negotiation.

You may also use both, such as spf2.0/mfrom,pra mx -all.
Servers that support this should interpret it the same as "v=spf1 mx -all".

share|improve this answer

Your Answer


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.