Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

How do you deal with the case of:

  • wanting to whitelist a domain so that emails from it won't get eaten, but
  • not having emails forged to appear to be from that domain get bogusly whitelisted

whitelist_from_recvd looks promising, but then you have to know at least the TLD of every host that could send you mail from that domain. Often will outsource email to one or more sending companies (like Constant Contact and the like) in addition to using servers that reverse-resolve to something in its own domain. But it looks like whitelist_from_recvd can only map to one sending server pattern so that would be problematic.

Is there a way to say something like "if email is from domain X, subtract N points from the spam score"?

The idea would be that if the mail is legit, that -N will all but guarantee it isn't considered spam. But if it is spam, hopefully all the other failed tests will render it spam even with the -N being included.

share|improve this question

This is the problem that Sender Policy Framework solves (if it's implemented correctly). The catch is, the sender has to set it up.

share|improve this answer
And DKIM and ... :) – QuantumMechanic Aug 30 '12 at 20:29
Yes, but DKIM doesn't really work for this. You can't presume a mail is not legitimate because a DKIM signature failed. – Michael Hampton Aug 30 '12 at 20:34
Oh, I know. Hence the smiley (referring to your "if it's implemented correctly" comment). – QuantumMechanic Aug 31 '12 at 15:32

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.