Louis Guillaume <lo...@zabrico.com> writes: >> I think what is supposed to happen is >> >> spamass-milter gets milter macros >> >> spamass-milter makes a synthetic Received: line that is *not* in the >> message as received. This proxies for the Received: line that the >> MTAe would add. The synthetic line includes a notation that the >> message was authenticated. >> >> spamass-milter sends the synthetic Received: line plus message to spamd >> >> spamd parses the synthetic received line and because of the auth line >> treats the Received line as indicating a local submission instead of a >> from-network hop. Thus ALL_TRUSTED fires. (I do not understand where >> itn the code this happens, and I'm not sure if this is the plan.) >> > >> If you are using pkgsrc, then updating to spamass-milter-0.3.1nb3 will >> bring in the Received header patch, bringing spamass-milter to head of >> CVS via a patch (in Makefile, not a patches/ file). I committed nb3 on >> 2010-06-03. But, the Received header bug doesn't seem to bother SA. I >> get the following causes/symptoms: >> >> no macro i (or j??) ==> SA claims no received lines, big mess >> >> no received: patch ==> no observed troubles >> >> (spamass-milter doesn't tell SA about auth) ==> [ >> rbl checks run against authenticated user's IP address >> lack of ALL_TRUSTED for authenticated user's mail >> ] >> > > That last one seems to be my problem. Does the patch fix this? I'll > try updating and see what happens.
No, I am not aware of any fix for the last problem. It needs a few lines of code in milter-greylist, and maybe some MTA config to pass macros.
pgpkASvIF987v.pgp
Description: PGP signature
