>> So in my understanding, Amavis must come in front of opendkim, does it?
>
> I thought amavis was anti-virus only. If it provides spam detection service as well, then yes, you want something like this to locate whatever amavis puts in the header to indicate the message is spam. It may not be the same as the example, however; the above is based on what Spamassassin does.
:) Amavis does spamassassin internally. So it also adds headers coming from SA.
Looks for example like this:
X-Spam-Status: No, score=-2.646 required=2.4 tests=[AWL=0.290, BAYES_00=-1.9,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VERIFIED=-0.1,
RP_MATCHES_RCVD=-0.735, SPF_PASS=-0.001] autolearn=ham
I have removed the flag option, but I will change the opendkim pattern like seen in this example above.
One last question:
Can you give some starting values for DKIMReputation* parameters? I guess 1001 will never be reached. But I have no experience with this. In Amavis I know the value is something around 6.23, which means a false-positive of less than 1:10.000. But I have no knowledge about upper and lower values that can be reached here in opendkim.
Thanks in advance
Kind regards
-Christian Rößner
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
Received on Mon Oct 29 2012 - 15:09:24 PST