Re: AlwaysSignHeaders results in "fail"

From: <lutz.niederer_at_gmx.net>
Date: Fri, 15 Jun 2012 23:05:21 +0200

> > If send mail with this X-Scan-Info header present and I add
> > AlwaysSignHeaders X-Scan-Info to opendkim.conf verification always
> fails.
> > AlwaysSignHeaders CC to opendkim.conf verification succeeds.
> > AlwaysSignHeaders CC,X-Scan-Info to opendkim.conf verification always
> fails.
> >
> > If I send mail with this X-Scan-Info header NOT present and I add
> > AlwaysSignHeaders X-Scan-Info to opendkim.conf verification succeeds.
> > AlwaysSignHeaders CC to opendkim.conf verification succeeds.
> > AlwaysSignHeaders CC,X-Scan-Info to opendkim.conf verification succeeds.
> >
> > OpenDKIM is running on a mail relay. The header is added at the hop
> > before that relay. So, the relay does not do anything with this header
> > except passing it through like all the other headers. I can also
> > clearly see that the header is not modified (it is pretty simple
> > "X-Scan-Info: a").
> >
> > Strange! Any tips what I am missing here?
>
> The only thing AlwaysSignHeaders does is amend the "h=" value to ensure
> your named header field(s) are always there even if they were absent
> during signature generation. They don't actually cause the header field
> to be signed. Try adding this to your configuration:
>
> SignHeaders *,+x-scan-info


Thanks, I'll try this.
What does "*" exactly mean? Did I miss something in the documentation? Are there more such things like "*" and where can they be found in the docu?

Cheera!
-litzn



-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Received on Fri Jun 15 2012 - 21:05:36 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:20:40 PST