MailScanner Digest, Vol 120, Issue 4
mailinglists at feedmebits.nl
Fri Dec 4 13:20:32 UTC 2015
Thanks for your reply. It's for outgoing mail, the messages gets signed
but it doesn't pass the dkim test. When I take out mailscanner and just
let it go through postfix I get a pass. So seems like Mailscanner
changes the body/hash of the dkim headers?
I have the same settings for adding multiple headers:
Multiple Headers = add
Place New Headers At Top Of Message = yes
I just send plain text mails nothing with links in them. I'll have
another look at my logs.
spf=pass (google.com: domain of mailinglists at feedmebits.nl designates 126.96.36.199 as permitted sender) smtp.mailfrom=mailinglists at feedmebits.nl;
dkim=neutral (body hash did not verify) email@example.com
KIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=feedmebits.nl;
Authentication-Results: hotmail.com; spf=temperror (sender IP is 188.8.131.52) smtp.mailfrom=mailinglists at feedmebits.nl; dkim=permerror header.d=feedmebits.nl; x-hmca=none header.id=mailinglists at feedmebits.nl
X-SID-PRA: mailinglists at feedmebits.nl
On 12/04/2015 01:00 PM, mailscanner-request at lists.mailscanner.info wrote:
> Send MailScanner mailing list submissions to
> mailscanner at lists.mailscanner.info
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> mailscanner-request at lists.mailscanner.info
> You can reach the person managing the list at
> mailscanner-owner at lists.mailscanner.info
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MailScanner digest..."
> Today's Topics:
> 1. dkim and Mailscanner (Maarten)
> 2. Re: dkim and Mailscanner (Mark Sapiro)
> Message: 1
> Date: Thu, 3 Dec 2015 22:24:49 +0100
> From: Maarten <mailinglists at feedmebits.nl>
> To: mailscanner at lists.mailscanner.info
> Subject: dkim and Mailscanner
> Message-ID: <5660B321.8040108 at feedmebits.nl>
> Content-Type: text/plain; charset=utf-8
> I'm having a problem getting dkim to work together with mailscanner. I
> noticed some comments about dkim in the comments so I took the advice of
> the comments.
> Multiple Headers = add
> # Some people prefer that message headers are added in strict order with
> # the newest headers at the top and the oldest headers at the bottom.
> # This is also required if you receive a message which is authenticated by
> # DKIM, and you are forwarding that message onto somewhere else, and want
> # not to break the DKIM signature.
> # **Note**: To avoid breaking DKIM signatures, you *must* also set
> # Multiple Headers = add
> # So if some of your users forward mail from PayPal, Ebay or Yahoo! to
> # accounts stored on Gmail or Googlemail, then you need to set this to "yes"
> # and "Multiple Headers = add" to avoid breaking the DKIM signature.
> # It may be worth using a ruleset to just apply this to messages sent by
> # the companies mentioned above.
> # This can also be the filename of a ruleset.
> Place New Headers At Top Of Message = yes
> Each time I got the following error:
> dkim=neutral (body hash did not verify) firstname.lastname@example.org
> I thought I'd try doing a test by taking out mailscanner, only using postfix, and now I'm getting:
> dkim=pass email@example.com
> So for some reason Mailscanner is changing the body hash of the dkim signature. Any know what what's causing this and how to fix it?
> I can't find any other config setting in Mailscanner that would fixes this.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the MailScanner