Milter-greylist

Sometime, somewhere, Jeff Earickson scribbled:

> Anyway, the suggestions of Mr. Messerer on this webpage concerns me.
> The poprelayd fiddles with the contents of greylist.conf. Yuck.
>
> I would much rather have the greylist code use an existing
> Berkeley DB file that my sendmail.cf file looks at by way of the
> following entry in my sendmail.cf file:
>
> Kpopauth hash -a<OK> /etc/mail/db/pophash
>
> This is what I'm trying to get to with the entries:
>
> sm_macro "POP relay" "{popauth}" "OK"
> acl whitelist sm_macro "POP relay"
>
> in greylist.conf and the corresponding entries in sendmail.cf:
>
> O Milter.macros.envrcpt={popauth} (or something)
>
> This is what I was trying to get to with M. Dreyfus' help and 
(maybe)
> code debugging of rc5. I would like to continue on that path.
>
> Jeff Earickson

Fellow humans,

I'm no sendmail guru.  I've been trying to find a solution to this 
problem concurrently.  I think I've discovered the source of our 
difficulty.

If someone knows something that I don't (which wouldn't be hard), 
please slap me around.

After having conducted some research, I've come to the conclusion that 
popauth db, like access db, is a map.  I don't think we can pass a map 
to a milter, only a macro.  It seems to me (again, no sendmail expert) 
that a macro could be likened to a variable, whereas a map seems to be 
more of a function.

Regardless, I totally agree with you Jeff, that munging the conf file 
is a hazardous proposition at best.  I think that the quickest path to 
success will be us finding someone who can write a sendmail ruleset to 
populate a macro (that we can then pass to the milter) based upon a 
lookup from a map.