On 17 Jun 2019, at 14:28, David B Funk wrote:
Taking a quick look at the source code for spamass-milter (I use a
different milter) I can see that it explicitly needs '{auth_type}' and
'{auth_ssf}'
so you can ignore {auth_authen} & {auth_author}.
That's an unfortunate design choice.
The {auth_ssf} macro is (almost?) always going to be 0 and I suspect
that it's impossible for it to be anything else, since that would
indicate a "security layer" handled via SASL, which nobody really does.
If one is not supporting GSSAPI via SASL, it is not even hypothetically
possible to negotiate a security layer in SASL because it appears that
no other registered SASL mechanism supports any security layer; they
mostly just say "do this inside TLS."
If I were a user of spamass-milter, I would report that requirement as a
bug.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
