Patrick Proniewski wrote: > In mean time I've changed my all setup to use only > milters (more readable config).
Seems reasonable to me. > Unfortunately I've discovered that Amavisd is unable to add headers > I want as it would do as an smtp proxy filter. > It will properly add: > > X-Virus-Scanned: my custom tag > X-Crm114-Status: UNSURE ( 6.79 ) Those two milters appear configured okay. Okay for CRM114 (which I like and use as well). Okay for the virus scanner. You are seeing the headers. That appears to be working okay. > but won't add: > > X-Spam-Score: -3.714 > X-Spam-Flag: NO > X-Spam-Level: > X-Spam-Status: No, score=-3.714 tagged_above=-6 required=3 > tests=[ALL_TRUSTED=-1, ... That milter configuration for SpamAssassin appears to have a problem then. If the headers are not being added. Because conceptually it is no different from the other two milters. But if that milter is not able to add those headers then something is not right about that configuration. If it were me I would keep working that part of the problem. > I'm still wondering how it can add the X-Crm114-Status header > (amavisd uses spamassassin and spamassassin uses crm114, quite far > fetched) but seems unable to add it's own personalized headers. If this were the spamassassin users list I would challenge that assertion because as far as I know SpamAssassin does not use CRM114. SA has its own Bayes engine. Instead CRM114 would be running from it's own configuration separately. I run CRM114 before SpamAssassin and then add in custom SA rules to score a final SA score using CRM114 as one of the weighted inputs, de-rating SA's internal Bayes to avoid double scoring. But since this isn't the SpamAssassin users list I will simply suggest gently that something is wrong with the milter configuration for it interfacing to Postfix. Bob
