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

I have Opendkim working well for signing messages but verification fail, I guess that's because emails are injected from Dspam on so Opendkim try to sign the mail instead of verifying it

This is an exemple when receiving a mail from gmail :

Dec  3 13:10:58 mail postfix/smtpd[16282]: connect from[]
Dec  3 13:10:59 mail postfix/smtpd[16282]: NOQUEUE: filter: RCPT from[]: <>: Recipient address triggers FILTER smtp-dspam:[]:25000; from=<> to=<> proto=ESMTP helo=<>
Dec  3 13:10:59 mail postfix/smtpd[16282]: 997C03FF20:[]
Dec  3 13:10:59 mail postfix/cleanup[16290]: 997C03FF20: message-id=<>
Dec  3 13:10:59 mail opendkim[15867]: 997C03FF20: [] not internal
Dec  3 13:10:59 mail opendkim[15867]: 997C03FF20: not authenticated
Dec  3 13:10:59 mail opendkim[15867]: 997C03FF20: no signature data

I think having dkim before dspam would solve the problem but I don't see how ?

this is my Postfix conf : :

smtpd_recipient_restrictions =  check_recipient_access pcre:/etc/postfix/dspam_filter
                                check_recipient_access pcre:/etc/postfix/dspam_filter_rejectexternal
                                check_sender_access pcre:/etc/postfix/dspam_filter_rejectexternal

milter_default_action = accept
smtpd_milters = inet: :

localhost:25001 inet    n       -       -       -       -       smtpd
  -o content_filter=
  -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks,no_milters
  -o smtpd_helo_restrictions=
  -o smtpd_client_restrictions=
  -o smtpd_sender_restrictions=
  -o smtpd_recipient_restrictions=permit_mynetworks,reject
  -o mynetworks=
  -o smtpd_authorized_xforward_hosts=
share|improve this question

1 Answer 1

The no_milters option at the end of your receive_override_options is telling Postfix not to use milters after the mail is re-injected. That's usually used to stop OpenDKIM from signing a mail twice when using a content filter.

Your question says DSpam is injecting on 25000, but your is set up for 25501. Which one is accurate?

share|improve this answer
my mistake, DSPAM receives on 25000 and inject on 25001 –  user62555 Aug 9 '11 at 8:10

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.